Betweenlands 3.3.1

Forge 2611

Singleplayer

While creating a mod pack on curse launcher, I decided to add this mod to my pack, since I really loved the design and feel. I have quite a few mods installed so i selectively removed them temporarily so I could see how they interacted with this new mod. After hours of testing I found myself struggling to figure out why this mod's dimension was so hard to load when I had more than 50 mods installed (Often taking about a minute per chunk). When I jump into the portal tree and get into the Betweenlands, the chunks start to load and then stop for a minute. The world persisted to generate very slowly, often raising my ping beyond absurd levels even of singleplayer. With even more testing I found that it tends to lag a lot more with more mods installed, regardless of which ones. Obviously this behavior is expected since that's how modding works, but Twilight forest and other dimension mods do not react this way

Okay I've tested it again with ATM3 (233 mods) and it works just fine for me. The initial worldgen of the area around the portal is somewhat slow (still around the same as with the BL only though), but as soon as it's done it runs fine with almost exactly the same time per tick as in the overworld. Going through the portal is almost instant except when the dimensions are unloaded, in which case it sometimes takes around 4-6 seconds.
Like I mentioned before it could be that you ran into one of the lighting bugs which can slow the TPS to a crawl.

If you don't know how to use a profiler like VisualVM you can try using the vanilla ingame profiler which is started/stopped with the commands /debug start and /debug stop. You need to start the profiler and then let it run for a while so it can collect data. Once you stop it again it should generate a "profile-results-..." file in the debug folder which you can send to us

I play on the Hexxit modpack and absolutely adore Betweenlands. We have a similar problem though too. Chunks load slower in Betweenlands than the overworld or Erebus. Checking betweenlands out by itself without other mods seems to make chunks load normally but no faster in the overworld. But twilight forest seems to have a similar problem for me but with a different twist. Character moving and and chunks loading isn't slow at all, but trying to break a block, eat, use a potion, kill a mob or even use a portal is given a dramatic delay when betweenlands is installed. I hope this helps narrow anything down.

Isn't Hexxit for 1.7.10? A link to any modpack that has this problem would help.

But twilight forest seems to have a similar problem for me but with a different twist.

And what is that different twist? :P
TF has the same problems with the lighting system as our dimension sometimes does, which won't be fixed until the fixes are accepted into Forge.

Do you have any profiling results (preferably with something like VisualVM)?
Worldgen can can definitely be a bit slow at times (partly due to bug(s) in the lighting system), but what you've described doesn't sound normal.

I'll try it out later today with some big modpacks and see what happens. Last time I tested something in ATM3 it worked fine though, IIRC

That one runs fine for me too, I don't see any difference between the mod pack and the BL alone

https://minecraft.curseforge.com/projects/hexxit-updated

I just updated my modpack. The name is The Quantumverse. It is still under review so I'll let you know when its approved. The version that contains the Betweenlands is 2.5.0. Regarding the memory usage, I did see it above 90% most of the time I was in the dimension, but I have more than enough ram allocated (8 GB). I did not send the log with the memory error. If you want I could try reproducing it and sending you that log, although I didn't see anything there that could point to any issue. It was mainly entity/render lag that i saw in the debug.

maybe its a bug with certain drivers or computer specs? Seems weird since I have somewhat a decent rig. Im running a 6700k, 2 1080s in sli and nvidia drivers 388.59

Edit: as for the modpack, I have hesitated to release the new version because of this bug, but I could send you a link to the beta thru google drive or something. The entity lag is usually the worst part. Try hitting a mob while the dimension is loading. It doesnt respond for at least 2 minutes or crashes. The crash log that I get though is just a standard out of memory error, even tho I have 5 gigs assigned.

When I try to quit while its loading the dimension, it crashes and I get this log. it also said this a lot when I turned on debugging:

The Betweenlands loaded a new chunk (4, 41 Dimension: 20) during chunk population, causing cascading worldgen lag. Please report this to the mod's issue tracker. This log can be disabled in the Forge config.

The crash log that I get though is just a standard out of memory error, even tho I have 5 gigs assigned.

I don't see any out of memory error in the log you sent, or is that another one? You can check on the F3 screen how much memory is being used, if it gets close to 90% chances are you need to give it more RAM.

It also said this a lot when I turned on debugging:
The Betweenlands loaded a new chunk (4, 41 Dimension: 20) during chunk population, causing cascading worldgen lag. Please report this to the mod's issue tracker. This log can be disabled in the Forge config.

That's normal if it occasionally appears when generating new terrain, but if it happens constantly it could be other mods causing it.

I'll definitely need either a profiling result or the modpack, otherwise I can't help on this because I can't reproduce it even with big modpacks. You can PM the modpack link to me on Discord, Curse or MCF.

Oh that explains it. Thank you for pointing that out, I will definitely try that.

Yep, it fixed the lag once I added in the blacklisted mobs. Thanks.

Betweenlands is awesome btw.

Sent a fixed build of ESM (13.160) up to Curse Forge. Turns out it was caused by a tiny missing piece of code that used to be in 1.7.10 to scale down the pathing checks when increasing target distances. This missing check made mobs try and pathfind every half second regardless of distance.

Vadis pointed out there may potentially be chunk runaway trigger somewhere contributing to the slowdown but until we have more profiling tests to figure out where it could be coming from, there isn't a lot I can do to fix it. In the mean time that update should start to help mitigate most of the issues.

Thanks, I'll check it out.

I did not send the log with the memory error. If you want I could try reproducing it and sending you that log, although I didn't see anything there that could point to any issue.

Nah it's ok, there's not much to be gained from it. But since your memory usage is above 90% most of the time and you even got an out of memory error I really recommend at least trying it out with some more memory. If the garbage collector constantly needs to run it can cause a lot of lag (although it would also cause big FPS lag spikes).

Yes, now I can reproduce it. That is definitely not normal...
But since the BL works perfectly fine in ATM3 which has more mods I'm quite sure that it does not have anything to do with the number of installed mods and is more likely an incompatibility with some mod or some mod causes runaway/cascading chunk gen in the dimension.

Seems like it generated a huge number of chunks (5 * 16 * 32 = 2560 blocks in X dir!) just after entering the portal and not even moving. As soon as it stops generating those chunks it starts running normally at 20 TPS without any lag.

IIRC somebody reported a similar issue a while ago. I ran VisualVM to figure out what's going on and somehow entity AI/path finding keeps loading chunks, and it seems like Epic Siege Mod replaces all entities' AI with a custom AI and then causes the runaway chunk gen:

Found the old issue, is probably exactly the same problem: #353

I've found an AI Blacklist in the Epic Siege Mod config. You may want to start adding BL mobs there until it stops lagging the game out. The angler fish (thebetweenlands:angler) would be a first candidate to add because that's what caused the problem in the picture above

@Funwayguy

Stahp it!

Thanks! That didn't fix it unfortunately, but since the config allows blacklisting AI's it's not really a problem