infernalstudios / Infernal-Expansion

Expanding the Nether beyond the Nether Update!
https://www.curseforge.com/minecraft/mc-mods/infernal-expansion
Apache License 2.0
58 stars 30 forks source link

[1.19.2] Extreme Rendering lag with incendium+Terrablender #391

Open RedBeast1959 opened 1 year ago

RedBeast1959 commented 1 year ago

Describe the Bug

With combination of Incendium datapack and Terrablender, Infernal Expansion's glowstone valley biome cause extreme rendering lag( a.k.a. "Waiting for Chunk" ). Without Terrablender, Incendium does not generate any glowstone valley, and with only Terrablender and not Incendium, there's no rendering lag for glowstone valley.

P.S. I deleted data/minecraft/dimension/the_nether.json of Incendium just in case there's biomesource override problem. But It still cause same rendering lag for IE's biome.

Reproduction Steps

  1. Put current version of Incendium + Terrablender and Infernal Expansion
  2. Open nether portal and enter
  3. Find Glowstone Valley(IE's biome) ...

Expected Result

Extreme rendering lag in Glowstone Valley followed by specific F3 debug("Waiting for Chunk")

Screenshots and Videos

2022-10-02_04 31 41 2022-10-02_04 33 17

Operating System

Windows 10

Mod Version

2.5.1

Minecraft Version

1.19

Forge Version

43.1.32

Other Mods

infernal-expansion-1.19.2-2.5.3.jar TerraBlender-forge-1.19.2-2.0.1.127.jar Oh_The_Biomes_You'll_Go-forge-1.19.2-2.0.0.11.jar incendium-5-1-3(Datapack) rubidium-0.6.2

Additional Context

No response

UfaiX04 commented 1 year ago

Encountering same problem

SwanX1 commented 1 year ago

This is not rendering lag, it's slow world generation. Given you're using terrablender and incendium, it's most likely their issue, not ours, because by default our mod generates the biome with decent speed. We can't really provide support. A profiler report (like spark) would be essential in determining and fixing the problem if it is on our side.

MarioSMB commented 1 year ago

Spark reports unfortunately probably don't help pinpoint much as Incendium is a datapack - any laggy parts will just return Java internal functions, as shown here https://spark.lucko.me/UtPw4VKjfu which I suppose further shows it's an Incendium issue.
Sadly Incendium due to its nature tends to be incredibly resource heavy.