Before some 12-year old opens his mouth and tells me to buy a better computer, let me preface by putting my system specs right here:
- 12 thread i7 5820k overclocked to 4.4GHz
- 2-way SLI 980tis overclocked to 1203MHz
- 32GB DDR4 overclocked to 2400MHz
- OS and game running on a Samsung SSD950 connected to 4x gen3 PCI-E lanes (Non-Volatile Memory Express, not SATA!)
- 144Hz G-sync display running at 1440p
Let me also state for the record that X99 CPUs have no integrated graphics coprocessor. Now that that's over with, I apologize for my bluntness.
I've been having issues with all versions of Java minecraft over the last two years (Since I built this machine in 2016). My symptoms include periodic microstutters of varying duration at frequencies ranging from 0.5~4 per second. I experience these stutters on both vanilla and modded Minecraft, on all versions tested between 1.4.7 and 1.12.2. Turning my render settings up to 32 chunks increases the length of the stutters slightly, while turning it down to 2 chunks only decreases the duration of the stutters slightly. They are always present, no matter what I do. I've tried Optifine, Fastcraft, you name it.
One interesting thing to note is that I experience the same sort of microstutter on the Windows 10 edition... but it's only noticeable if I turn my render distance up to something ridiculous like 72. This leads me to believe that the problem is not related to the Java emulator, but rather something to do with the core programming of the game itself and the way it utilizes system hardware. My GPU drivers are not out of date... I'm running 390.77 - January 2018.
One commonality that I have noticed is that the Alt+F3 pie chart shows a recurring tick spike that coincides perfectly with my stutters. This leads into my second symptom: Internal server lag. In both vanilla and modded MC, I've noticed internal server lag on occasion when I try to break blocks. I'll mine out three pieces of Stone... and nothing will happen for a good three to four seconds [modded 1.10.2]. Then I'll get a slight rollback like you would on a slow multiplayer server. Or, I'll dig up a block of sand... and the two blocks of water surrounding it will just sit there for a couple of seconds before they decide to flow [vanilla 1.4.7].
Since version 1.5 or 1.6, I've even noticed stuttering in UI elements - like the main menu screen.
Can anyone help me make sense of this insanity? No other game does this to me. I can upload a 60fps video of the microstutter on request.
You assigned 16 gigs to MC, show how you did it, post your JVM arguments.
Technic launcher. Like I said. No Java arguments.
And here's a vanilla screenshot on a clean vanilla launcher install that I just did to show I'm not BSing you. Oddly enough, that graph was mostly flat and green for the first 90 seconds or so. Then it turned into what you see there.
Edit: added a second screenshot right after startup to show the difference. Still stutters though.
Not sure if it's related or not, but I always have to disable mipmapping... otherwise I get transparent pixels on block edges.
I just tested the Windows 10 edition again with 72 render distance. The performance and resource utilization is much better (Actually getting some SLI - at around 16% on each card), but the exact same stutter is still there - if to a lesser degree. There is no debug screen in the W10 version, otherwise I would post it.
In vanilla: turn down your render distance to 16 and turn on VBOs. And turn off GeForce experience overlay.
Done. Shown in versions 1.4.7, 1.7.10, 1.10.2, 1.12.2.
I couldn't get the bar chart to display in the older versions, but the stutter was tangibly much worse. I had to hold down shift and alt for a few seconds *before* pressing F3 in order to get the chart to display on .10 and .12. That might have been the issue with the earlier ones too, come to think of it. I can try again with that technique in mind if you'd like.
Also shown in the later three versions is the mipmapping bug.
It picked up pretty clearly, so watch in full screen 720p60. Don't blink or you'll miss them! Look closely at the foreground in the first 10-15 seconds and you'll be able to pick up the smaller microstutters. Keep going towards the end and you'll see some of the more obvious spikes by focusing near the crosshair.
Where Quake is to glass, Minecraft is to sandpaper. Why is this happening?
(Sorry about the music. Forgot to turn off audio in FRAPS. )
you say you have sli cards, is sli enabled or disabled? if enabled have you tried disabling it?
This issue has presented itself from day one on this machine. I didn't add my second card until about a year after the initial build, so it's definitely not SLI related.
I'm curious about the little orange MB/S reading that I get on some of the technic pack screenshots... what is that? Read/write rate to disc or something? Sometimes it jumps up to around 3.3GB/S.
If that number *does* represent the rate at which the game is trying to write to disc, is it possible that my problems are arising from the simple fact that those operations are taking up too many CPU cycles? I.E. the game is probably developed using slow HDDs and 'normal' SATA SSDs. If I have effectively removed the bottleneck that they would normally provide by letting the game write to a stupidly fast PCI-E drive, and there is no internal throughput limiter in place within the game code... could my NVMe drive actually be hurting my performace? Is there any way to install Minecraft onto a separate hard drive to test this?
Before some 12-year old opens his mouth and tells me to buy a better computer, let me preface by putting my system specs right here:
- 12 thread i7 5820k overclocked to 4.4GHz
- 2-way SLI 980tis overclocked to 1203MHz
- 32GB DDR4 overclocked to 2400MHz
- OS and game running on a Samsung SSD950 connected to 4x gen3 PCI-E lanes (Non-Volatile Memory Express, not SATA!)
- 144Hz G-sync display running at 1440p
Let me also state for the record that X99 CPUs have no integrated graphics coprocessor. Now that that's over with, I apologize for my bluntness.
I've been having issues with all versions of Java minecraft over the last two years (Since I built this machine in 2016). My symptoms include periodic microstutters of varying duration at frequencies ranging from 0.5~4 per second. I experience these stutters on both vanilla and modded Minecraft, on all versions tested between 1.4.7 and 1.12.2. Turning my render settings up to 32 chunks increases the length of the stutters slightly, while turning it down to 2 chunks only decreases the duration of the stutters slightly. They are always present, no matter what I do. I've tried Optifine, Fastcraft, you name it.
One interesting thing to note is that I experience the same sort of microstutter on the Windows 10 edition... but it's only noticeable if I turn my render distance up to something ridiculous like 72. This leads me to believe that the problem is not related to the Java emulator, but rather something to do with the core programming of the game itself and the way it utilizes system hardware. My GPU drivers are not out of date... I'm running 390.77 - January 2018.
One commonality that I have noticed is that the Alt+F3 pie chart shows a recurring tick spike that coincides perfectly with my stutters. This leads into my second symptom: Internal server lag. In both vanilla and modded MC, I've noticed internal server lag on occasion when I try to break blocks. I'll mine out three pieces of Stone... and nothing will happen for a good three to four seconds [modded 1.10.2]. Then I'll get a slight rollback like you would on a slow multiplayer server. Or, I'll dig up a block of sand... and the two blocks of water surrounding it will just sit there for a couple of seconds before they decide to flow [vanilla 1.4.7].
Since version 1.5 or 1.6, I've even noticed stuttering in UI elements - like the main menu screen.
Can anyone help me make sense of this insanity? No other game does this to me. I can upload a 60fps video of the microstutter on request.
-
View User Profile
-
View Posts
-
Send Message
Moderatorpost an F3 screen and your java arguments
-Attached
No java arguments.
GPU1,2 and CPU load shown in upper left... 0, 16, and 27% respectively.
Here's another screenshot after sitting still for a few minutes.
I'm not sure what's going on with that bar chart in the bottom left. It looks like there are two of them overlapping.
You assigned 16 gigs to MC, show how you did it, post your JVM arguments.
Technic launcher. Like I said. No Java arguments.
And here's a vanilla screenshot on a clean vanilla launcher install that I just did to show I'm not BSing you. Oddly enough, that graph was mostly flat and green for the first 90 seconds or so. Then it turned into what you see there.
Edit: added a second screenshot right after startup to show the difference. Still stutters though.
Not sure if it's related or not, but I always have to disable mipmapping... otherwise I get transparent pixels on block edges.
I just tested the Windows 10 edition again with 72 render distance. The performance and resource utilization is much better (Actually getting some SLI - at around 16% on each card), but the exact same stutter is still there - if to a lesser degree. There is no debug screen in the W10 version, otherwise I would post it.
In vanilla: turn down your render distance to 16 and turn on VBOs. And turn off GeForce experience overlay.
Done. Shown in versions 1.4.7, 1.7.10, 1.10.2, 1.12.2.
I couldn't get the bar chart to display in the older versions, but the stutter was tangibly much worse. I had to hold down shift and alt for a few seconds *before* pressing F3 in order to get the chart to display on .10 and .12. That might have been the issue with the earlier ones too, come to think of it. I can try again with that technique in mind if you'd like.
Also shown in the later three versions is the mipmapping bug.
I tested the game with G-sync disabled just to humor myself. Still stutters, except with a whole lot of screen tearing.
Here, have a video.
It picked up pretty clearly, so watch in full screen 720p60. Don't blink or you'll miss them! Look closely at the foreground in the first 10-15 seconds and you'll be able to pick up the smaller microstutters. Keep going towards the end and you'll see some of the more obvious spikes by focusing near the crosshair.
Where Quake is to glass, Minecraft is to sandpaper. Why is this happening?
(Sorry about the music. Forgot to turn off audio in FRAPS.
)
-
View User Profile
-
View Posts
-
Send Message
Moderatoryou say you have sli cards, is sli enabled or disabled? if enabled have you tried disabling it?
This issue has presented itself from day one on this machine. I didn't add my second card until about a year after the initial build, so it's definitely not SLI related.
I'm curious about the little orange MB/S reading that I get on some of the technic pack screenshots... what is that? Read/write rate to disc or something? Sometimes it jumps up to around 3.3GB/S.
If that number *does* represent the rate at which the game is trying to write to disc, is it possible that my problems are arising from the simple fact that those operations are taking up too many CPU cycles? I.E. the game is probably developed using slow HDDs and 'normal' SATA SSDs. If I have effectively removed the bottleneck that they would normally provide by letting the game write to a stupidly fast PCI-E drive, and there is no internal throughput limiter in place within the game code... could my NVMe drive actually be hurting my performace? Is there any way to install Minecraft onto a separate hard drive to test this?
Just trying to come up with ideas.
What are these huge blue spikes?
Bump.
@MachineMedic
I got some help from someone on the minecraftirc.net #minecrafthelp channel.
Someone recommended to disable integrated graphics via BIOS. Once I did this my single player frame lag issues disappeared.
However, I'm still having issues when I run a local server.
I thought about setting up a virtual machine and running my server in there, but I'm honestly just too lazy to do so right now. Hope this helps!!
See here:
https://www.intel.com/content/www/us/en/products/chipsets/desktop-chipsets/x99.html