[1.7.10] Chunk generation lag?

[Quesenek]

In my 1.7.10 beta build of basically the same mods as the unstable pack give or take some mods that I cannot find the chunk loading is not noticeably bad, FPS is amazing. In single player its horrible however it is the same as 1.6.4 so I cannot say anything about it.
Overall I love the 1.7.10 mods.

 

[reddvilzz]

The spamming is real though for me. Using solitarycraft, unstable and the third party modpack forgelabs they all are the same. I have no idea why and it lags a lot for me. In monster 1.6.4 i can play just fine with 230 mods. But now in 1.7.10 even with 140 or 90 mods it lags a lot. The lags either come from when new chunk loads and i get that chunk ticking spam and lots of lag spikes after 15 minutes playing. Tried JVM arguments but that didn't really fix the problem though.

I have no clue on how to be able to play with 1.7.10 modpacks

Sent from my Nexus 5 using Tapatalk

 

[unknown zombie]

Yeah, it's definitely going to be frustrating.

I am really hoping it gets fixed, because who knows how long we'll be waiting for 1.8.

I'm going to try pre-generating a world, but I've never looked into that before. Anybody have any tools to suggest for that?

Sent from my SAMSUNG-SGH-I337 using Tapatalk

 

[KurShedir]

You can use command blocks to teleport you around in creative in order to generate large portions of the world. Better than nothing.
Worst case scenario, I'll stick with skyblocks.

 

[SatanicSanta]

I'm not getting any of the console spam, but when generating chunks it'll occasionally freeze for minutes.

 

[Densely]

i am getting this console spam too. if only mojang would fix it. (ex, 1.7.11)

 

[Qazplm601]

i am getting this console spam too. if only mojang would fix it. (ex, 1.7.11)

mmh, i dunno. i'm not sure if i wan't them to work on fixing this or 1.8. actually, i think you're right. it would help modded players a lot(with lag) and make the game more enjoyable.

 

[van Krass]

Just use this guys
http://www.minecraftforum.net/forum...ecraft-tools/1261072-minecraft-land-generator

 

[Qazplm601]

Just use this guys
http://www.minecraftforum.net/forum...ecraft-tools/1261072-minecraft-land-generator

funny thing is, i already knew about that. i want a actual fix.

 

[budge]

I'm going to pray to the Gods of Modding for a bandaid fix.

 

[It_IS_Lupus]

I get it too. normally its fine, but when i go exploring for more than a few minutes i get massive lag it alleviates itself once all the chunks load. but its irritating.

 

[Zenthon_127]

I'm playing with 40 mods atm and I get this. It sucks.

I hope somebody out there figures out a bandaid, because servers are going to hate their lives.

 

[unknown zombie]

This just keeps getting worse the more mods I add. I've only got 99 mods running:

[13:13:00] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2656ms behind, skipping 53 tick(s)
[13:13:21] [Client thread/INFO]: Warning: Clientside chunk ticking took 156 ms
[13:13:22] [Client thread/INFO]: Warning: Clientside chunk ticking took 218 ms
[13:13:22] [Client thread/INFO]: Warning: Clientside chunk ticking took 212 ms
[13:13:22] [Client thread/INFO]: Warning: Clientside chunk ticking took 448 ms
[13:13:23] [Client thread/INFO]: Warning: Clientside chunk ticking took 191 ms
[13:13:24] [Client thread/INFO]: Warning: Clientside chunk ticking took 221 ms
[13:13:24] [Client thread/INFO]: Warning: Clientside chunk ticking took 350 ms
[13:13:27] [Client thread/INFO]: Warning: Clientside chunk ticking took 142 ms
[13:13:28] [Client thread/INFO]: Warning: Clientside chunk ticking took 227 ms
[13:13:28] [Client thread/INFO]: Warning: Clientside chunk ticking took 198 ms
[13:13:29] [Client thread/INFO]: Warning: Clientside chunk ticking took 261 ms
[13:13:29] [Client thread/INFO]: Warning: Clientside chunk ticking took 148 ms
[13:13:30] [Client thread/INFO]: Warning: Clientside chunk ticking took 183 ms
[13:13:31] [Client thread/INFO]: Warning: Clientside chunk ticking took 182 ms
[13:13:33] [Client thread/INFO]: Warning: Clientside chunk ticking took 111 ms
[13:13:33] [Client thread/INFO]: Warning: Clientside chunk ticking took 139 ms
[13:13:34] [Client thread/INFO]: Warning: Clientside chunk ticking took 139 ms
[13:13:34] [Client thread/INFO]: Warning: Clientside chunk ticking took 140 ms
[13:13:34] [Client thread/INFO]: Warning: Clientside chunk ticking took 141 ms
[13:13:34] [Client thread/INFO]: Warning: Clientside chunk ticking took 138 ms
[13:13:34] [Client thread/INFO]: Warning: Clientside chunk ticking took 135 ms
[13:13:34] [Client thread/INFO]: Warning: Clientside chunk ticking took 110 ms
[13:13:35] [Client thread/INFO]: Warning: Clientside chunk ticking took 110 ms
[13:13:41] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 17883ms behind, skipping 357 tick(s)
[13:13:43] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2730ms behind, skipping 54 tick(s)
[13:14:07] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 5273ms behind, skipping 105 tick(s)
[13:19:24] [Client thread/INFO] [inventorytweaks]: net.minecraft.client.gui.GuiChat
[13:19:30] [Client thread/INFO]: Warning: Clientside chunk ticking took 124 ms
[13:19:34] [Client thread/INFO]: Warning: Clientside chunk ticking took 2952 ms
[13:19:37] [Client thread/INFO]: Warning: Clientside chunk ticking took 2989 ms
[13:19:40] [Client thread/INFO]: Warning: Clientside chunk ticking took 3128 ms
[13:19:44] [Client thread/INFO]: Warning: Clientside chunk ticking took 3308 ms
[13:19:47] [Client thread/INFO]: Warning: Clientside chunk ticking took 3376 ms
[13:19:50] [Client thread/INFO]: Warning: Clientside chunk ticking took 3309 ms
[13:19:54] [Client thread/INFO]: Warning: Clientside chunk ticking took 3074 ms
[13:19:57] [Client thread/INFO]: Warning: Clientside chunk ticking took 3074 ms
[13:20:00] [Client thread/INFO]: Warning: Clientside chunk ticking took 3024 ms
[13:20:03] [Client thread/INFO]: Warning: Clientside chunk ticking took 3190 ms
[13:20:06] [Client thread/INFO]: Warning: Clientside chunk ticking took 3196 ms
[13:28:25] [Client thread/INFO]: Warning: Clientside chunk ticking took 112 ms
[13:28:25] [Client thread/INFO]: Warning: Clientside chunk ticking took 152 ms
[13:28:34] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2011ms behind, skipping 40 tick(s)
[13:28:51] [Client thread/INFO]: Warning: Clientside chunk ticking took 127 ms
[13:28:51] [Client thread/INFO]: Warning: Clientside chunk ticking took 128 ms
[13:28:51] [Client thread/INFO]: Warning: Clientside chunk ticking took 130 ms
[13:28:51] [Client thread/INFO]: Warning: Clientside chunk ticking took 131 ms
[13:28:51] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2566ms behind, skipping 51 tick(s)
[13:29:06] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2383ms behind, skipping 47 tick(s)

17883 ms! My computer isn't a slouch; I'm not trying to play on a laptop; there's no reason for Minecraft to run this poorly.

My computer could run 1.6.4 Monster perfectly fine with 184 mods. I hope this can get fixed, or 1.7.10 is going to be DOA for me.

I did a Google search to see if I could find any info on the problem and the only thing that really turned up was this Forge forum thread where some people complained about this problem and LexManos shut them down pretty quick.

 

[Zenthon_127]

I'm going to do a quick test in Vanilla. If the test turns out how I think it well, it's a Forge bug.

EDIT: Actually, this is a vanilla bug. Mods just make it 100x worse. That number is literal.

 

[RedBoss]

Meh, I'm playing vanilla.

 

[Quesenek]

Doing a little more world exploration the highest my server got was a 500ms hit, usually it is just 50-150ms hits when loading the chunks which does make me mad sometimes when I'm not expecting it.
The largest hit was from me accidentally loading a 50x50 area of chucks using the dimensional anchor but that was only a 5000ms hit.
Unless you are a super explorer the chunk loading lag hits are not bad at all on a server, normal base play is just fine.

 

[MegaRaja54321]

So i am running 200+ mods on 1.7.10 and yeah when i use my hang glider at full speed I get a lot of chunk lag. I found this problem when I was looking for those metorites from ae2. I even crashed a few times. I have 4gb alocated and and i5 bla bla bla 2.7ghz

 

[Skyqula]

This is defenitly a vanilla minecraft 1.7 problem. It gets worse with mods, especially mods with alot of world generation.

I did a Google search to see if I could find any info on the problem and the only thing that really turned up was this Forge forum thread where some people complained about this problem and LexManos shut them down pretty quick.

He is right in the sense that this isnt a bug with forge. However, its a pretty nasty bug as far as modded minecraft on 1.7 is concerned. I hope they can reach out to Mojang and get what ever fix they have for the issue "backported" into forge.

I also woudnt be suprised if it takes an initial FTB modpack release to get this issue to a hot topic state.

Edit: This looks interesting... https://twitter.com/LexManos/status/497887682484518913

*runs scripts to setup start of a s14w30a workspace*internet goes down* dammet. Guess its game day....

Edit2: Ok, not related, ignore that.

 

[Quesenek]

This is defenitly a vanilla minecraft 1.7 problem. It gets worse with mods, especially mods with alot of world generation.



He is right in the sense that this isnt a bug with forge. However, its a pretty nasty bug as far as modded minecraft on 1.7 is concerned. I hope they can reach out to Mojang and get what ever fix they have for the issue "backported" into forge.

I also woudnt be suprised if it takes an initial FTB modpack release to get this issue to a hot topic state.

Either that or they release 1.8 and all the modders move their mods to 1.8. I see that as a more likely outcome.

 

[budge]

1.8 is going to be a long time from now. 1.7 could turn out to be a long, painful experience...

I've done some testing in single player. These are the mods which I've focused on, specifically for their world generation components:

Battle Towers, Biomes O' Plenty, Farlanders, Hardcore Ender Expansion, Natura, Roguelike Dungeons, Ruins, and Twilight Forest.

Removing all of them leaves me with almost no non-vanilla worldgen. Exceptions include ores from Thermal Foundation, abyssal stone from Railcraft, meteors from AE, some trees from HarvestCraft, and bees from Forestry, as removing them pretty much guts the pack. In this slimmed down pack, chunk lag is noticeably better. It is still there, but pauses are no more than half a second, compared to 10-20 full seconds before. Adding Natura by itself brings back 5-10 second pauses, and adding Biomes O' Plenty by itself brings pauses of 3-5 seconds. Still testing the others.

I should note that this problem is exponentially worse in single player, so if you can tune your pack's performance acceptably in single player, then it'll be much better on a dedicated server.