You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can confirm. Lag spikes start happening on breaking or placing blocks after /filling a large amount of blocks. Just to be sure, loading new chunks (via /tp) and then breaking or placing blocks doesn't produce lag spikes.
Condition resolves after quitting/reloading world without quitting Minecraft. Condition doesn't resolve after reloading chunks (F3+A)
Log produces similar output to OP. Lag spike detector doesn't trigger before using the /fill command.
[15:11:37] [Render thread/INFO]: Lag spike at terrain_setup - 23,828,000ns, threshold is 16,666,666ns
[15:11:38] [Render thread/INFO]: Lag spike at terrain_setup - 30,804,300ns, threshold is 16,666,666ns
[15:11:38] [Render thread/INFO]: Lag spike at terrain_setup - 18,346,700ns, threshold is 16,666,666ns
[15:11:38] [Render thread/INFO]: Lag spike at terrain_setup - 20,944,200ns, threshold is 16,666,666ns
[15:11:38] [Render thread/INFO]: Lag spike at terrain_setup - 18,419,600ns, threshold is 16,666,666ns
[15:11:38] [Render thread/INFO]: Lag spike at terrain_setup - 22,317,200ns, threshold is 16,666,666ns
...
System Informatinon
Other mods and versions installed
How you triggered the behavior
What you expected would happen
What actually happened
Logs and screenshots
latest.log
The text was updated successfully, but these errors were encountered: