Lag
Render
Resolved
(RESOLVED) L.S.O.D? My Minecraft drops to 0fps periodically in +1.8 versions for no apparent reason!
Poll: Should I add more info like more screenshots of the lagometer?
Ended Aug 12, 2017
Poll: Should I test other +1.8.8 versions to approach the problem?
Ended Aug 12, 2017
Poll: Versions between 1.8 and 1.8.8?
Ended Aug 12, 2017
This happens whether I use Optifine or not. It happens BOTH ON SINGLEPLAYER AND MULTIPLAYER. I have already reduced the settings and quality to the minimum, but nothing happened. I also tried out changing the autosave, VBO, VSync, non-fullscreen, etc. Still nothing. The game runs at decently FPS, but drops to 0 FPS for about half a second. This happens more or less every 4 seconds, which makes the game unplayable. This happens on every single +1.8 version, not all the time but something like %90 of the time I play. The Optifine Lagometer shows the reasons for these 'lag spikes'
On singleplayer, half of these lag spikes are produced by 'render terrain' (green colour). The toher half is produced by reasons unspecified (White colour)
On multiplayer, some of these lag spikes are produced by 'render terrain' and 'memory garbage collection' (orange colour), but most of them are by reasons unspecified (White colour).
Is this a L.S.O.D case? I know L.S.O.D is from the beta, but it seems to be that.
This is unmodified client support, please post a screenshot from vanilla game with F3 enabled and your JVM arguments.
Fine, I'll do, but I can't take a screenshot that shows '0 FPS' because the spike lag lasts so short that instead the F3 shows 15 FPS or so.
Done
-
View User Profile
-
View Posts
-
Send Message
ModeratorThe JVM arguments used like asked for too?
What do you mean? I forgot which the default JVM arguments were, but I don't think it may make a difference as I already tested out loads
I mean, I just changed the RAM usage
-
View User Profile
-
View Posts
-
Send Message
Moderatorpost the argument used to change the allocation of ram, it could make a difference as you may've change a value that shouldn't be changed, one of those is known to cause lag spikes like to say you have
Thanks! It worked