Many people are experiencing a significant decrease in FPS when playing Minecraft with the new update. But the odd thing about this bug is that it came with a significant amount of people who try to place the blame on the player or actually deny the bug exists, which I thought rather odd. So I thought I'd address all of the arguments against the factual existence of a known issue. Let me first begin by explaining what the issue is.
The problem is simply a drop in FPS. Many people don't have it, but then many of us do. I was using the same settings that I had in 1.2.5, and yet when I made a new world in 1.3.1, my FPS slowed to literally a crawl and made the game unplayable. Dropping all the settings to their lowest possible, restarting the computer, closing all programs, and waiting patiently for the world to load some more, did make it playable at the very least, but still with lots of noticeable FPS drops. I imagine other players have it worse. Some theorize that this issue is caused by the way "Single-player now runs a server internally".
Now to address the denial arguments:
Argument 1: "There's probably a virus on your computer."
The game works fine before an update, drops in performance immediately after, and you think a virus is causing it? Sure, a virus just happened to jump on my computer right when I updated the game. Well a scan shows I'm all clean, so...
Argument 2: "Download this mod that helps you optimize performance."
If you didn't need the mod to make the game perform properly before the update, you shouldn't need the mod after the update.
Argument 3: "I don't experience the problem, therefore the problem doesn't exist."
Terrible logic.
Argument 4: "My performance has actually increased since the update."
Ok. Good for you. What about us?
Argument 5: "You're probably doing something wrong on your end."
No we're not. If we're using the exact same settings we had before the game was updated, then why is it behaving differently now? Our settings have remained constant, and our computers have remained constant. The only thing that's changed is the update. Therefore, the problem has to do with the update. Even if we turn the settings even lower than we had them, that doesn't solve the problem for most of us.
Argument 6: "Get a better computer/Your computer is crappy/What are your specs?"
If the game worked on the computer we bought it for, it should continue to work on that same computer. You can't release an update that effectively kills the game for hundreds, possibly thousands of your paying customers and then tell them to get a better computer. No, we don't have to get a better computer. We fulfilled our end of the bargain by having a good enough computer when we first bought the game. It's unreasonable to expect us to go out and buy a new rig later down the line just because the game updated. And one does not simply "buy" a new computer. Many, if not most of us can't afford to do that. Don't get me wrong. I'm not accusing the devs of thinking like that. I'm just explaining why this logic doesn't work.
The FPS drop is indeed a real issue, and not a matter of opinion. I'm concerned about people denying it exists because I don't want the devs to be discouraged from looking into it. So please don't dismiss people when they claim the problem is happening to them. They have no reason to be making it up. We just want to play the game, same as you.
I have the same problem since the new version 1.3.1. I play like 5 mins fine sometimes just 1 min and at once the fps drops to 0 and i can't make almost no move more of course. Then i have to quit the game and relog in again and it works again fine for some minutes. When it goes to 0 it doesn't go more up i have to quit it through alt-f4.
I have the same problem. Plays with 100 fps then drops to 2 - 5 fps for a couple of minutes then gores back to 100 fps. Tried allocating more memory, adjusting video settings, updating drivers, updating Java, praying to various Gods....
I was hoping it was vendor related to route out the problem, but after 3psy's specs it is obvious it is in the patch.
Specs:
AMD 8120
16 gb ddr3
AMD 7970
Windows 7 64 bit
I have the same issues! Me and my brother were making a great base in 12w27a just fine. No FPS drops or anything. August 1st came out so we updated to 1.3.1. Well I heard there was something about "Chunk errors dont exsist anymore" So I thought "AWESOME SAUCE" So I log on to 1.3 I start my world and I start building a floating island. Everything is lagging. I hit Shift+F3 to see my FPS. It was at 100 , I was like ok.... So I placed another block. I imeditly dropped at 0 fps then hit 30 fps. Then started playing at 12-14 fps. Now this is kinda strange. I had 50 - 150 fps in minecraft playing, Now I dont need to clean my computer. I have 4 saves, I clean out my temporary files every week , Clear out my Windows Log Files and Windows error reporting. And my firefox cache. It still didnt work. Now before you say "wow your computer is crappy" Its not. Its a 3GB computer , Great graphics card , A great processer and 2-3 cores I believe. I really have no idea what happend when I updated it. Maybe since there arent anymore chunk errors that is processes stuff to much. BRING BACK CHUNK ERRORS!
Rollback Post to RevisionRollBack
I play Minecraft! I upload maps and love making redstone contraptions.
Nothing else has changed except the version. Talking to some of my friends who say it increased their performance.
Example 1:
Friend 1 FPS in 1.2.5: 20-30
Friend 1 FPS in 1.3.1: 30-50
Example 2:
Friend 2 FPS in 1.2.5: 10-30
Friend 2 FPS in 1.3.1: 30-40
Now, both their computers are much older and much worse than mine. This is not a hardware problem on my end. It is simply something about the update that has reduced my FPS. I'm not saying it happens to everyone, as it clearly does not, but just because it happens to the minority doesn't mean it should be ignored.
Argument? Did I miss something? Mojang said that 1.3 will decrease fps and that you probably need a new computer to play the game. There is nothing really you can do about it.
@Rocky55119
Actually 1.3 was for me the first version where I saw major chunk errors because they removed "unnecessary chunk reloading" Optifine fixed all of them for me except the chunkhole at spawn after death
This is unacceptable business practices. What on earth could you do to have some people decrease from rate by over 80% and THEN on the release notes claim "performance increases" That my friends is the worst business practice ever. Things like this actually cause lawsuits in the US when a business claims one thing and the end result is another. How I wish Mojang was in the U.S. they would have so many different business ethics laws they would HAVE to follow which sweden doesn't have.
Let me get this staright also: why is a update that adds just a handful of new features so detrimental to performance anyways? Why does their release software (they're NOT in Beta anymore folks) have soooo many bugs? The answer - Mojang has probably the worst suit of coders for java ever. I've never come in contact with an idie game or any game for that fact made in any language with soooo many bugs. There quality control is terrible. Mojang needs to get their **** together people. The honest truth is they are a terrible company with a good idea. What we need is a good company with a good idea.
The problem is that 1.3.1 merged Single and Multiplayer. So, when you play Single Player, your client starts a server and logs into itself basically. This is more resource intensive. OTOH, when playing multiplayer on another server, resource usage is significantly reduced because you are not running a server as well and optimizations have been made since 1.2.5.
As to dealing with the problem, I dont really feel like going through all the recommended steps to increase FPS again, but if you want you can look in one of the other threads I've posted in.
This is unacceptable business practices. What on earth could you do to have some people decrease from rate by over 80% and THEN on the release notes claim "performance increases" That my friends is the worst business practice ever. Things like this actually cause lawsuits in the US when a business claims one thing and the end result is another. How I wish Mojang was in the U.S. they would have so many different business ethics laws they would HAVE to follow which sweden doesn't have.
Let me get this staright also: why is a update that adds just a handful of new features so detrimental to performance anyways? Why does their release software (they're NOT in Beta anymore folks) have soooo many bugs? The answer - Mojang has probably the worst suit of coders for java ever. I've never come in contact with an idie game or any game for that fact made in any language with soooo many bugs. There quality control is terrible. Mojang needs to get their **** together people. The honest truth is they are a terrible company with a good idea. What we need is a good company with a good idea.
And this is where the conflict of sanity came into play. The Dev team wanted to hold off until everything, including the mod API, was finished and stable. But with the length of the update being the longest in MC history, the player base started getting impatient and clamoring for a content release to keep them busy. So they pushed back several features they had planned, focused on phase 1 with the code base merger and added some content to help satisfy the masses.
Everyone who was involved with testing the snapshot knew it was buggy, and the release would had benefited from being delayed another 2 months or more to work out the odd bugs. But apparently that wasn't enough to stop a lot of players from getting the snapshot, despite the risk, just to mess around with the new content.... and then come here in a panic when something breaks.
I've been in a lot betas in my days, but this is one of the few instance where the community demands got everyone in over their heads. Then came the delicious tears of butthurt once people realized they were getting what they asked for, but not what they expected.... followed by the "the merger is the worst thing ever" threads, a couple months of rampant misinformation, and now an outcry for a roll back to a divergent code base because it worked better.
It seems to me that the people with good pcs happen to have the fps drops. I used to run at about 10 fps max with game booster. Now without it im running at about 20 - 30 and with game booster about 45.
Personally I've seen some weirdness. I've had a slight overall increase in FPS, but with occasionally 1 to 2 second freezeups, especially in the first 5 minutes of play.
I'd like to see the stats as to what percentage of people with problems have AMD processors vs Intel. Could the new 1.3.1/.2 code be running afowl of manufacturer specific "optimiziations" in the instruction sets?
My specs:
AMD Phemon II X4 965 Black Edition (about the same as an i7 920)
8 gigs of ram
24 gigs of virtual ram
(I manually doubled the ram that Java can use too, because the default is too low for large minecraft worlds on my computer)
ATI 5770
Intel i7 (3.07ghz)
8gb Kingston HyperX (1600mhz)
Nvidia GTX590's (Two of them in SLI configuration)
Operating System Windows 7 (64x) (Fresh Install of the entire OS)
5 Kingston V+ Series SSD (Raid 0 configuration)
I have major issues to the point where I cannot even play the game.
I have noticed that the game is easily brought under load which cause's this issue.
As you can see the game is under %100 load all the time and is causing the amazing FPS drop and by amazing I mean I get 0-1 FPS after the first 3 mins of the game running this is most undoubtably a bug in the game at the moment.
I cannot play Minecraft with this bug.
It's Java 32x
Java 64x doesn't have the issue so make sure you got the right Java installed.
I have Java 32x (and Win7 64-bit) and I have experienced an FPS increase. Mind you, I also went in and doubled the ram Java could use, so...? Does Java 64-bit have a higher default allowable max ram useage than Java 32-bit? Could the FPS issues be a result of Java constantly trying to free up ram? If so, why do some people barely have playable games even on min view distance, when before they were fine at "far"?
Oh, and I have a fresh install of Windows too, which is why I currently have 32-bit Java. For some reason that's what autoinstalled, and I haven't bothered to go fix it yet.
That I knew;). Sorry, I was unclear. I was wondering about the default settings in 32-bit vs 64-bit. Maybe 32-bit comes out of the box with a setting of 512 megs, and 64-bit sets itself to 2-gigs? Just guessing as to what the difference could have been in your case.
This should really be pinned so that you can get more people to vote...I am almost positive that the numbers would shift from 2/3 people to more like 4/5...
Lucky you. I have a decent computer, but with the new update my FPS more than halved. Such a pain.
Here are my specs anyway:
CPU: Intel i7-2630QM @ 2.00GHz
GPU: AMD Radeon HD 6770m 1GB
RAM: 8GB
OS: Windows 7 Home Premium x64
Significant FPS drops even when using Max FPS setting in Video Settings. Like I said, getting about half as many FPS as I did in 1.2.5.
My PC is from 2006 and I got a FPS increase lol.
CPU: Intel Core 2 2.4GHz
GPU: NVIDIA GeForce 7950 GT
RAM: 2 GB
OS: Windows XP Media Center Edition 32bit
Edit:
I could run max settings but it will speed up a Minecraft memory leak. (Fix your game Jeb)
The problem is simply a drop in FPS. Many people don't have it, but then many of us do. I was using the same settings that I had in 1.2.5, and yet when I made a new world in 1.3.1, my FPS slowed to literally a crawl and made the game unplayable. Dropping all the settings to their lowest possible, restarting the computer, closing all programs, and waiting patiently for the world to load some more, did make it playable at the very least, but still with lots of noticeable FPS drops. I imagine other players have it worse. Some theorize that this issue is caused by the way "Single-player now runs a server internally".
Now to address the denial arguments:
Argument 1:
"There's probably a virus on your computer."
The game works fine before an update, drops in performance immediately after, and you think a virus is causing it? Sure, a virus just happened to jump on my computer right when I updated the game. Well a scan shows I'm all clean, so...
Argument 2:
"Download this mod that helps you optimize performance."
If you didn't need the mod to make the game perform properly before the update, you shouldn't need the mod after the update.
Argument 3:
"I don't experience the problem, therefore the problem doesn't exist."
Terrible logic.
Argument 4:
"My performance has actually increased since the update."
Ok. Good for you. What about us?
Argument 5:
"You're probably doing something wrong on your end."
No we're not. If we're using the exact same settings we had before the game was updated, then why is it behaving differently now? Our settings have remained constant, and our computers have remained constant. The only thing that's changed is the update. Therefore, the problem has to do with the update. Even if we turn the settings even lower than we had them, that doesn't solve the problem for most of us.
Argument 6:
"Get a better computer/Your computer is crappy/What are your specs?"
If the game worked on the computer we bought it for, it should continue to work on that same computer. You can't release an update that effectively kills the game for hundreds, possibly thousands of your paying customers and then tell them to get a better computer. No, we don't have to get a better computer. We fulfilled our end of the bargain by having a good enough computer when we first bought the game. It's unreasonable to expect us to go out and buy a new rig later down the line just because the game updated. And one does not simply "buy" a new computer. Many, if not most of us can't afford to do that. Don't get me wrong. I'm not accusing the devs of thinking like that. I'm just explaining why this logic doesn't work.
The FPS drop is indeed a real issue, and not a matter of opinion. I'm concerned about people denying it exists because I don't want the devs to be discouraged from looking into it. So please don't dismiss people when they claim the problem is happening to them. They have no reason to be making it up. We just want to play the game, same as you.
I have the same problem since the new version 1.3.1. I play like 5 mins fine sometimes just 1 min and at once the fps drops to 0 and i can't make almost no move more of course. Then i have to quit the game and relog in again and it works again fine for some minutes. When it goes to 0 it doesn't go more up i have to quit it through alt-f4.
Greetings 3psy
Specs:
i7 2600k
16gb ddr3
gtx 590
win-7, 64-bit
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI was hoping it was vendor related to route out the problem, but after 3psy's specs it is obvious it is in the patch.
Specs:
AMD 8120
16 gb ddr3
AMD 7970
Windows 7 64 bit
-
View User Profile
-
View Posts
-
Send Message
Retired StaffMy FPS in 1.3.1: 20-50
Nothing else has changed except the version. Talking to some of my friends who say it increased their performance.
Example 1:
Friend 1 FPS in 1.2.5: 20-30
Friend 1 FPS in 1.3.1: 30-50
Example 2:
Friend 2 FPS in 1.2.5: 10-30
Friend 2 FPS in 1.3.1: 30-40
Now, both their computers are much older and much worse than mine. This is not a hardware problem on my end. It is simply something about the update that has reduced my FPS. I'm not saying it happens to everyone, as it clearly does not, but just because it happens to the minority doesn't mean it should be ignored.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThis is unacceptable business practices. What on earth could you do to have some people decrease from rate by over 80% and THEN on the release notes claim "performance increases" That my friends is the worst business practice ever. Things like this actually cause lawsuits in the US when a business claims one thing and the end result is another. How I wish Mojang was in the U.S. they would have so many different business ethics laws they would HAVE to follow which sweden doesn't have.
Let me get this staright also: why is a update that adds just a handful of new features so detrimental to performance anyways? Why does their release software (they're NOT in Beta anymore folks) have soooo many bugs? The answer - Mojang has probably the worst suit of coders for java ever. I've never come in contact with an idie game or any game for that fact made in any language with soooo many bugs. There quality control is terrible. Mojang needs to get their **** together people. The honest truth is they are a terrible company with a good idea. What we need is a good company with a good idea.
As to dealing with the problem, I dont really feel like going through all the recommended steps to increase FPS again, but if you want you can look in one of the other threads I've posted in.
And this is where the conflict of sanity came into play. The Dev team wanted to hold off until everything, including the mod API, was finished and stable. But with the length of the update being the longest in MC history, the player base started getting impatient and clamoring for a content release to keep them busy. So they pushed back several features they had planned, focused on phase 1 with the code base merger and added some content to help satisfy the masses.
Everyone who was involved with testing the snapshot knew it was buggy, and the release would had benefited from being delayed another 2 months or more to work out the odd bugs. But apparently that wasn't enough to stop a lot of players from getting the snapshot, despite the risk, just to mess around with the new content.... and then come here in a panic when something breaks.
I've been in a lot betas in my days, but this is one of the few instance where the community demands got everyone in over their heads. Then came the delicious tears of butthurt once people realized they were getting what they asked for, but not what they expected.... followed by the "the merger is the worst thing ever" threads, a couple months of rampant misinformation, and now an outcry for a roll back to a divergent code base because it worked better.
-
View User Profile
-
View Posts
-
Send Message
Retired StaffLucky you. I have a decent computer, but with the new update my FPS more than halved. Such a pain.
Here are my specs anyway:
CPU: Intel i7-2630QM @ 2.00GHz
GPU: AMD Radeon HD 6770m 1GB
RAM: 8GB
OS: Windows 7 Home Premium x64
Significant FPS drops even when using Max FPS setting in Video Settings. Like I said, getting about half as many FPS as I did in 1.2.5.
I'd like to see the stats as to what percentage of people with problems have AMD processors vs Intel. Could the new 1.3.1/.2 code be running afowl of manufacturer specific "optimiziations" in the instruction sets?
My specs:
AMD Phemon II X4 965 Black Edition (about the same as an i7 920)
8 gigs of ram
24 gigs of virtual ram
(I manually doubled the ram that Java can use too, because the default is too low for large minecraft worlds on my computer)
ATI 5770
8gb Kingston HyperX (1600mhz)
Nvidia GTX590's (Two of them in SLI configuration)
Operating System Windows 7 (64x) (Fresh Install of the entire OS)
5 Kingston V+ Series SSD (Raid 0 configuration)
I have major issues to the point where I cannot even play the game.
I have noticed that the game is easily brought under load which cause's this issue.
As you can see the game is under %100 load all the time and is causing the amazing FPS drop and by amazing I mean I get 0-1 FPS after the first 3 mins of the game running this is most undoubtably a bug in the game at the moment.
I cannot play Minecraft with this bug.
www.gamers-haven.org
www.facebook.com/elitegamershaven
It's Java 32x
Java 64x doesn't have the issue so make sure you got the right Java installed.
www.gamers-haven.org
www.facebook.com/elitegamershaven
I have Java 32x (and Win7 64-bit) and I have experienced an FPS increase. Mind you, I also went in and doubled the ram Java could use, so...? Does Java 64-bit have a higher default allowable max ram useage than Java 32-bit? Could the FPS issues be a result of Java constantly trying to free up ram? If so, why do some people barely have playable games even on min view distance, when before they were fine at "far"?
Oh, and I have a fresh install of Windows too, which is why I currently have 32-bit Java. For some reason that's what autoinstalled, and I haven't bothered to go fix it yet.
64x can use up to 128gb of ram.
www.gamers-haven.org
www.facebook.com/elitegamershaven
My PC is from 2006 and I got a FPS increase lol.
CPU: Intel Core 2 2.4GHz
GPU: NVIDIA GeForce 7950 GT
RAM: 2 GB
OS: Windows XP Media Center Edition 32bit
Edit:
I could run max settings but it will speed up a Minecraft memory leak. (Fix your game Jeb)