I wish people would realize that FPS has NOTHING to do with lag.
In a new world I made specifically for this purpose both 1.7 and 1.8 showed the same FPS (82 / 83) but the 1.8 world was lagging so bad I could see the edge of the ocean and the hidden stuff underneath (whereas in 1.7 every chunk that I had not visited was rendering in a perfect circular area in front of me).
As I flew around in creative it got worse in 1.8 while 1.7 was fine - but the frame rates were overall the same.
FPS does have a lot to do with lag, so does chunk loading lag, but FPS is lag as well.
Rollback Post to RevisionRollBack
XP Guide Regardless of what change you do, no matter how small, someone will complain. - Jens Bergensten If you want me to see your reply, make sure to quote my post in your reply.
frame rate is not slow for me, its the in game ... when starting a new map takes forever... then everything in game moves soooooooooooo slow ug ...
What do you mean by forever? (in secounds)
Generating a map takes 9 secounds for me (actually the loading screen takes only 8 secounds, but it takes a secound for everything to become visible), then there's an additional secound untill the fps gets up to a playable amount (>50 fps), and then there's an additional 3 secs in which the fps increase to the maximum of 60.
This was tested on a laptop with a 2.6GHz i5.
Really the only FPS problem for me is on Single Player worlds. I only get slight lag when on Multiplayer. In pre 1.8 official release versions my worlds on SP would run okay except for my survival world. Now sadly it isn't so great. And that survival world? Sadly it's so bad it's unplayable. Luckily there's somethings called patches and fixes!
The 1.8 Update has rendered Minecraft un-playable for me. I was struggling along with around 15 FPS in online servers now I can count them on 1 hand. Even If I downgrade to 1.7.10 It's still un-playable. I seriously hope Mojang come out with a fix for this soon.
P.S. I run all settings at minimum.
so you say you had more frames before 1.8 but even if you downgrade you have now low frames so that means your frames are now lower even if you play on 1.7 again.
Plane old vanilla gives me 10 fps while running now. I was getting a minimum of 60 (capped, so don't know the actual cap) with 1.7. With or without optifine. Can't really blame it on my PC, sure my PC is slightly outdated but I get better FPS in recent games with demanding graphics. Even ****ty console ports run smoother.
it ight be because the 1.8 update is new and your pc cant exactly handle it or you might be dealing with a virus on your pc check to make sure your pc is clean and if that dosent work tell me immediently coz u might be hacked
Plane old vanilla gives me 10 fps while running now. I was getting a minimum of 60 (capped, so don't know the actual cap) with 1.7. With or without optifine. Can't really blame it on my PC, sure my PC is slightly outdated but I get better FPS in recent games with demanding graphics. Even ****ty console ports run smoother.
Actually, Minecraft is a pretty demanding game. It's blockyness and low-res textures may make it look like a PS1 game, but it has to calculate milions of vertices and render millions of polygons. It doesn't do much fancy effects like shadows and such, but still, the GPU load shouldn't be underestimated. And then there's still all the things Minecraft has to update, which puts a rather big load on the CPU and the RAM as well.
Having said that, if I turn render distance down to 4 it stays above 60 most of the time (still has the same relative drop, simply hidden by a higher FPS) and since I spend most of my time underground I wouldn't notice the difference most of the time, but the mob spawning issue is still a problem; one clue as to what causes it can be found in MCEdit; here are the results from analyzing a rather small world (1120 chunks):
There are 250 hostile mobs in that small area - triple the number there are supposed to be (creepers and zombies each already reached the cap by themselves), which tells me the mob spawning bug is due to mobs not despawning before chunks are unloaded and it somehow still counts those mobs into the mob cap, possibly because the game still loads/generates a larger area of chunks as you move, as seen by setting render distance to 2 and moving into new chunks then using MCEdit or a mapping utility to look at the world, presumably only actively spawning/despawning mobs within the render distance but still counting mobs in "inactive" chunks. This also explains observations of mob spawn rates decreasing over time and as you move around. The buildup of mobs doesn't happen on older versions since mobs despawn before they get outside the active chunk area.
Description
Seems like the fps has been fixed,the only thing that lags me now is the chunk loading,If i stop i go over 100fps,but if i start moving the chunks start to load up and the fps drops to 7
Description
When chunks load properly, they load really fast, but a lot of the time they seem to not load for a couple of minutes (i've seen similar things on the xbox version in videos, where they're trying to get somewhere but have to stand and wait for the next chunk to load). I went in /gamemode 1 so i could fly past the edge, but the chunks took a long time to load behind me.
FPS does have a lot to do with lag, so does chunk loading lag, but FPS is lag as well.
Regardless of what change you do, no matter how small, someone will complain. - Jens Bergensten
If you want me to see your reply, make sure to quote my post in your reply.
Same and I have better FPS
Gaming PC: AMD A8-7600 3.3GHz Quad-Core Processor | Gigabyte GA-F2A68HM-DS2H Micro ATX Motherboard | Kingston HyperX Fury Blue 4GB DDR3-1866 Memory | Western Digital BLACK SERIES 500GB 2.5" 7200 RPM Internal Hard Drive | Thermaltake VL80001W2Z ATX Mid Tower Case | Corsair Builder 430W 80 + Bronze Certified ATX Power Supply | Windows 10 Insider Preview 64-Bit |
Laptop: Intel Core 2 Duo P8600 2.4GHz Dual-Core Processor | Dell Inc. 0F328M Motherboard | 4GB DDR2-667MHz Memory | 74GB Seagate ST980313AS ATA Hard Drive | Dell Latitude E6500 Chassis | Dell 90W AC Adapter | Windows 10 Insider Preview 32-Bit |
Contact me for support or just to chat about PCs, gaming, anime, etc.
What do you mean by forever? (in secounds)
Generating a map takes 9 secounds for me (actually the loading screen takes only 8 secounds, but it takes a secound for everything to become visible), then there's an additional secound untill the fps gets up to a playable amount (>50 fps), and then there's an additional 3 secs in which the fps increase to the maximum of 60.
This was tested on a laptop with a 2.6GHz i5.
Figured it was time for a change.
so you say you had more frames before 1.8 but even if you downgrade you have now low frames so that means your frames are now lower even if you play on 1.7 again.
sounds like a problem with your computer.
jep same here fps invreased from 24 to about 60 with almost no lagspikes
it ight be because the 1.8 update is new and your pc cant exactly handle it or you might be dealing with a virus on your pc check to make sure your pc is clean and if that dosent work tell me immediently coz u might be hacked
Actually, Minecraft is a pretty demanding game. It's blockyness and low-res textures may make it look like a PS1 game, but it has to calculate milions of vertices and render millions of polygons. It doesn't do much fancy effects like shadows and such, but still, the GPU load shouldn't be underestimated. And then there's still all the things Minecraft has to update, which puts a rather big load on the CPU and the RAM as well.
I might play around with the framerate, but my CPU for minecraft is spiking to 90%, a good 40% more than 1.7.whatever the last one was.
Having said that, if I turn render distance down to 4 it stays above 60 most of the time (still has the same relative drop, simply hidden by a higher FPS) and since I spend most of my time underground I wouldn't notice the difference most of the time, but the mob spawning issue is still a problem; one clue as to what causes it can be found in MCEdit; here are the results from analyzing a rather small world (1120 chunks):
There are 250 hostile mobs in that small area - triple the number there are supposed to be (creepers and zombies each already reached the cap by themselves), which tells me the mob spawning bug is due to mobs not despawning before chunks are unloaded and it somehow still counts those mobs into the mob cap, possibly because the game still loads/generates a larger area of chunks as you move, as seen by setting render distance to 2 and moving into new chunks then using MCEdit or a mapping utility to look at the world, presumably only actively spawning/despawning mobs within the render distance but still counting mobs in "inactive" chunks. This also explains observations of mob spawn rates decreasing over time and as you move around. The buildup of mobs doesn't happen on older versions since mobs despawn before they get outside the active chunk area.
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
I think the main cause of this is the new way the game loads chunks in 1.8. That may have something to do with the huge FPS drop when moving around.
Other than that, i don't have any proper advice on how to solve or mitigate the problem.
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?