1
FPS Drops
Since 1.10 version I have problem with massive fps drops every few seconds. MC normally runs at 150-300 fps, but when this massive lag appears it just goes down to 0-4 fps. I was searching for a problem and it looks like a problem with a memory.
I've tried changing JVM arguments for Java, but it hasn't helped.
This seems to be the problem:
Every time it reaches 409, lag spike appears.
I've tried changing JVM arguments for Java, but it hasn't helped.
This seems to be the problem:
Every time it reaches 409, lag spike appears.
Create an account or sign in to comment.
10
1
Nevermind, the image wasn't working.
1
When you use a 32-bit Java version you can only allocate about 1.4-1.6 GB, depending on your system. If your system is 64-bit, I advice you to use the 64-bit Java version instead of the 32-bit version.
1
How is this relevant? OP is using a 64-bit edition of Java.
1
Bdogs15 - I've allocated 2G to it, but in-game it stays the same
1
Yeah, I found out that allocated RAM was the problem. Now my problem is, that I just cannot allocate more RAM to Java. I tried changing arguments in Minecraft Launcher but also in Java settings. It just stays on 486 MB, no mather what I try
1
It'll only allocate as much as it needs - maybe it only needed that extra 22MB to run properly.
Under Mem is another value called "Allocated," which should be at around 25%. Correct?
Under Mem is another value called "Allocated," which should be at around 25%. Correct?
1
oh nevermind the image wasnt working for me..yeah dedicate more ram
1
The game doesn't have enough memory allocated to it. You can give it more via the launcher profile's Java arguments config option.
1
That also might be the problem, what is your -Xmx on the java args?
1
put VSYNC on, sets your fps to your monitors refresh rate(you might be getting 600 fps but your screen might be only showing you 60fps because thats the monitors refresh rate)
You could be running stuff in the background that causes the spikes or too high of a render distance...Cannot be exactly sure w/o a log
You could be running stuff in the background that causes the spikes or too high of a render distance...Cannot be exactly sure w/o a log