When any block is altered at all in game (breaking/placing blocks, torches, grass, each time that flowing water or lava expands to new blocks or recedes etc.), the game will freeze for a very brief moment. This is not to be confused with the block lag that you sometimes get while on servers that are under heavy load (block will appear to break, pop back into existence and then break a second time). While idling or while walking around, my FPS is at least 200. I have tried allocating more RAM to the game via the JVM arguments, using Optifine and lowering my graphics settings. None have worked.
I'm running vanilla Minecraft v1.13 with the latest version of Java on Windows 10 x64
PC Specs:
MSI Gaming 970 Series Motherboard
AMD FX-6300 (6 core processor) @ 3.5 ghz
Zotac GeForce GTX 750ti (2GB DDR5 VRAM)
8GB DDR3 RAM @ 800 mhz
Toshiba HDD (like 4500rpm or something)
Insignia 520W PSU
If anyone needs more info to diagnose the problem, let me know
P.S. I'm not sure if this falls into the known issue of "Bad performance on 1.13" mentioned in the board rules, so yeah
Put those JVM arguments back to default, turn on VBOs and disable any ingame overlays.
The lag still happens when changing lots of blocks quickly e.g. breaking the bottom block of large stacks of gravel or sand, breaking lots of single-hit blocks like sugarcane or lily pads and placing water/lava and letting it flow, but it doesn't stutter quite as much and no longer happens on normal blocks. Not a full fix but the game is actually playable now, so thanks
When any block is altered at all in game (breaking/placing blocks, torches, grass, each time that flowing water or lava expands to new blocks or recedes etc.), the game will freeze for a very brief moment. This is not to be confused with the block lag that you sometimes get while on servers that are under heavy load (block will appear to break, pop back into existence and then break a second time). While idling or while walking around, my FPS is at least 200. I have tried allocating more RAM to the game via the JVM arguments, using Optifine and lowering my graphics settings. None have worked.
I'm running vanilla Minecraft v1.13 with the latest version of Java on Windows 10 x64
PC Specs:
MSI Gaming 970 Series Motherboard
AMD FX-6300 (6 core processor) @ 3.5 ghz
Zotac GeForce GTX 750ti (2GB DDR5 VRAM)
8GB DDR3 RAM @ 800 mhz
Toshiba HDD (like 4500rpm or something)
Insignia 520W PSU
If anyone needs more info to diagnose the problem, let me know
P.S. I'm not sure if this falls into the known issue of "Bad performance on 1.13" mentioned in the board rules, so yeah
Post a screenshot with F3 enabled and your JVM arguments.
JVM arguments: -Xmx8G -Xmn4G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=16M
Put those JVM arguments back to default, turn on VBOs and disable any ingame overlays.
The lag still happens when changing lots of blocks quickly e.g. breaking the bottom block of large stacks of gravel or sand, breaking lots of single-hit blocks like sugarcane or lily pads and placing water/lava and letting it flow, but it doesn't stutter quite as much and no longer happens on normal blocks. Not a full fix but the game is actually playable now, so thanks