I hope I am not the only one, but I played this snapshot and I never got above 25 fps. That is very strange because I usually have 60 fps. I had 60 in the snapshot before this. I cannot play when my fps is this low. This tells me that it is the snapshot rather than my computer. Anyone else having this issue? BTW I am running windows 7 64 bit. This is after messing with the settings as well.
I have noticed similar behavior as well, however, it is a snapshot and will probably be addressed in either future snapshots or with general version release.
I dont know why but most of snapshots kinda kill me, from time to time the computer starts working slower. Mostly, going into the nether on snapshots its kinda a pain because i start to lag 100% sure, sometimes more, sometimes less.
Snapshots are not made for optimization; they are made for testing reasons when new features are added. Don't expect optimization until they start getting ready for the actual release.
Snapshots are not made for optimization; they are made for testing reasons when new features are added. Don't expect optimization until they start getting ready for the actual release.
I understand what you say man, but how can some players actually TEST the snapshot features if they can barely play with the memory leaks? If thats the purpose of a snapshote, this problem kinda goes against such purpose.
I understand what you say man, but how can some players actually TEST the snapshot features if they can barely play with the memory leaks? If thats the purpose of a snapshote, this problem kinda goes against such purpose.
Then they should be reporting the memory leaks so they don't appear in the official release. That's still testing.
I understand what you say man, but how can some players actually TEST the snapshot features if they can barely play with the memory leaks? If thats the purpose of a snapshote, this problem kinda goes against such purpose.
Question .... how on earth would someone find out if memory leaks are happening with out testing it? You tested .. you find it's going slow .. now report it. Not much else you can do till they release the next snapshot to fix these issues. Which they tend to do anyway .. so exactly what is the problem?
I also saw a sharp decrease in framerate in this snapshot. It seems like this is the fault of the chunk updates, if I stand still for a few moments my framerate will jump to the high 40s / 50s once chunk updates stop. With render distance of 10 instead of my usual 12 I get solid 60 FPS once chunk updates stop but framerate is still in the 20s while they are going on. Which basically means a mean framerate in the 20s since, well, who wants to play the game while standing still in-game?
There is nothing in this snapshot that warrants such a framerate penalty as far as I can tell so it is probably a bug that needs to be discovered and squashed.
Well when my frame rate is on the border of playable and not playable, it is kinda hard to test stuffs.
Well, then let the people with better computers test the poorly optimized snapshots, and you can wait for the released versions.
Seriously, this constant complaining about snapshots not being up to par with released versions is getting really old. They are snapshots. They have bugs. That's why they let us test them.
I used to not lag from enchant shine, but it started somewhere around 1.6 and I still lag horribly from enchants, optimization be damned!
I modded out the glint myself for this reason, although in my case it started when I installed the Improved First Person View mod, and was highly inconsistent; that is, about once every 2-3 times I played it would cause severe lag when I held an enchanted item, but otherwise there was no impact (also, it only affected held items, not my armor, which is visible when looking down, and still has the glint as I only removed it from held items, not armor or items in my inventory).
As for the snapshots, I've noticed a big decrease in framerate during chunk updates, to a much greater extent than other versions/snapshots. On the other hand, the game has less lag spikes while loading chunks, particularly during new chunk generation, presumably because it is spread out over multiple frames (Optifine has a similar function, in addition to using multiple CPU cores, eliminating almost all chunk loading lag).
I modded out the glint myself for this reason, although in my case it started when I installed the Improved First Person View mod, and was highly inconsistent; that is, about once every 2-3 times I played it would cause severe lag when I held an enchanted item, but otherwise there was no impact (also, it only affected held items, not my armor, which is visible when looking down, and still has the glint as I only removed it from held items, not armor or items in my inventory).
I don't really want to get rid of it though, cause I like the shiny. lol
I should probably test if the lag goes away from replacing the texture with a blank one, that would be pretty cool.
Well, then let the people with better computers test the poorly optimized snapshots, and you can wait for the released versions.
Seriously, this constant complaining about snapshots not being up to par with released versions is getting really old. They are snapshots. They have bugs. That's why they let us test them.
Now why do I have to be limited because I don't have a gaming computer? That does not seem right. Just because you have a gaming computer and can handle the game on ultra even with these snapshots doesn't mean that you can have no regard for those that don't. You are saying it as if you and the people with gaming computers are a higher rank than those that don't. You are also saying it as if it is poorly optimized because they only want people with good computers testing them. No, they want everyone testing them. This is an excusable mistake on Mojang's part, and it is just some constructive criticism. If all topics that had constructive criticism were locked, then they would have a very crappy game that would very well still be in beta.
Now why do I have to be limited because I don't have a gaming computer?
Uh, that's kinda like saying, "Why can't I make my car go 180mph just because I don't have a Lamborghini? My 1967 Volkswagen Beetle should be able to do it too!"
You are saying it as if you and the people with gaming computers are a higher rank than those that don't. You are also saying it as if it is poorly optimized because they only want people with good computers testing them.
No, I'm not saying either of those things. I'm saying that if your computer is a toaster, you can't expect to be able to play games with poorly optimized code.
I'm also saying that you can't expect game developers to fully optimize their code and still release snapshots every week.
There is a certain toaster that burns the day's forecast into your toast. It doesn't burn a map of your country with warm and cold fronts, but it burns a rain drop, a sun, a cloud or a snowflake into your toast.
I understand what you say man, but how can some players actually TEST the snapshot features if they can barely play with the memory leaks? If thats the purpose of a snapshote, this problem kinda goes against such purpose.
Then they should be reporting the memory leaks so they don't appear in the official release. That's still testing.
Question .... how on earth would someone find out if memory leaks are happening with out testing it? You tested .. you find it's going slow .. now report it. Not much else you can do till they release the next snapshot to fix these issues. Which they tend to do anyway .. so exactly what is the problem?
There is nothing in this snapshot that warrants such a framerate penalty as far as I can tell so it is probably a bug that needs to be discovered and squashed.
Seriously, this constant complaining about snapshots not being up to par with released versions is getting really old. They are snapshots. They have bugs. That's why they let us test them.
Although I normally play 1.6.4. I got down to 1 fps with a jungle forest fire in 1.7.4. But yeah, it's only a snapshot. Optimizing required, expected.
I modded out the glint myself for this reason, although in my case it started when I installed the Improved First Person View mod, and was highly inconsistent; that is, about once every 2-3 times I played it would cause severe lag when I held an enchanted item, but otherwise there was no impact (also, it only affected held items, not my armor, which is visible when looking down, and still has the glint as I only removed it from held items, not armor or items in my inventory).
As for the snapshots, I've noticed a big decrease in framerate during chunk updates, to a much greater extent than other versions/snapshots. On the other hand, the game has less lag spikes while loading chunks, particularly during new chunk generation, presumably because it is spread out over multiple frames (Optifine has a similar function, in addition to using multiple CPU cores, eliminating almost all chunk loading lag).
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 should probably test if the lag goes away from replacing the texture with a blank one, that would be pretty cool.
Uh, that's kinda like saying, "Why can't I make my car go 180mph just because I don't have a Lamborghini? My 1967 Volkswagen Beetle should be able to do it too!"
No, I'm not saying either of those things. I'm saying that if your computer is a toaster, you can't expect to be able to play games with poorly optimized code.
I'm also saying that you can't expect game developers to fully optimize their code and still release snapshots every week.
Don't put words in my mouth.
It garbage collects breadcrumbs and uses a processor to toast the bread?