Console errors thrown whenever players travel.
Multiplayer server, vanilla with performance and QOL
1.21.5
Fabric
Modlist:
- BadOptimizations
- c2me-fabric
- cloth-config
- DistantHorizons
- entity-culling
- fabric-api
- ferritecore
- ImmediatleyFast-Fabric
- iris
- lithium
- moreculling
- NoChatReports
- sodium
- threadtweak
- vmp
The console throws errors that look like the following:
12/06 16:26:30 [Error] Trying to schedule tick in not loaded position class_2338{x=159, y=58, z=8188}
12/06 16:26:30 [Error] [16:26:30] [DH-PriorityTaskPicker Thread[2]/ERROR]: Trying to schedule tick in not loaded position class_2338{x=159, y=58, z=8189}
The co-ordinates are not located at the player at the time of the error log.
Server RAM usage has gone from 60% ish to 95%-100%
Many thanks 🙂23 Replies
So it doesn’t happen without DH?
Does it happen when DH is the only mod?
Prior to adding DH to the modlist, it hadn't happened before no
I am yet to try on its own as it is for a live community server I run
occurred again today:
having removed all mods except DH i get the following:
the issue still persists with all other mods removed
!logs
You should send your
latest.log file to provide additional useful information.
Logs are usually located in the .minecraft/logs directory.
On Windows: %appdata%\.minecraft\logs
On Linux: ~/.minecraft/logs
On Mac: ~/Library/Application Support/minecraft/logs
Please upload the file to mclo.gs instead of sending the raw file. This makes reading the contents of the file a lot easier and improves the chances of you getting the help needed.
After uploading the file, click on Save and send the link.oh sure - i can do that
https://mclo.gs/WmjnlgV
this is with mods
https://mclo.gs/InKGIP1
this is without mods
Before the errors there are 2 warnings suggesting optimising your world and deleting the DH DBs
IDK how to optimise a server world though.
Other then that I guess you can try updating to DH nightly that contains some additional bug fixes
There are no method to optimize the world on the server. You need to load up the world on a client then use the world optimizer option there.
In any case, what kind of world is this? Is it generated as the server first run, or is it a world that has been upgraded from a prior version? Or perhaps this is a world downloaded from the internet or edited with external tools?
I did do a couple of full resets of the DH sql file. The error always pops up regardless.
I think you can't optimise a world on a server? not 100% sure though as I've only messed with DH for a month or so now.
Its a long running survival world. The earliest backup I have access to is dated Jan 2019, before 1.15.
The server started early 2017 if I remember correctly - so 1.12.
The only external tool I use for editing is MCA selector for chunk trimming (as the world file is approaching 25GB uncompressed) but otherwise no tinkering.
Definitely need the world to be optimized before loading up Distant Horizons on it.
With that said, this has been 2 instances where older world upgraded without optimizing has cause this error to pop up.
what does optimising actually do?
Updates the world format to a later version, remove any deprecated entries, update all entities, tile entities and others to a new format (most important), make sure world is in a consistent state for when generation occurs.
Consistent state is probably the most important in the context of Distant Horizons. Without optimization, you will have the world containing data for 2 or more versions of Minecraft.
i see, and is it possible this could impact the worldfile in the future- with updates and such?
Last time I checked, it causes LOD generation to stall.
Little testing was done on that regard, so there's little information around this.
Well, ill make a backup and them optimise - I'll get back to you on if it fixes it or not when i do
Thanks for your help 🙂
righty - got some interesting results.
first thing:
I did a world optimisation, took a backup, and switched the server over to the optimised world file.
this is the logfile for the optimised world: https://mclo.gs/TdgvYHS
second thing:
removed the sql file hoping it would solve itself, but the old issue returned.
this is the logfile for the optimised world after I reset the DH sql file: https://mclo.gs/B8CUHtq
this is all quite confusing xD
I do think it is something to do with the worldfile, but at least some others seem to be having the same issue so I'm not alone.
I did do a new map test - and no errors popped up. so its something to do with the map.
as a little aside, the DH chunks look like they match the terrain, but when you get closer the actual loaded terrain ends up looking different (example below).
For the second paragraph, if the difference is minor, that is expected behavior for the default generation mode which is Features.
Difference is only visible in the LOD. Actual chunk data remains accurate to the world generator.
I figured as much
what do you recon about the errors then?
is it something that is fixable? (not complaining at all - the mod is amazing)
and if so - i'd be happy to provide any help needed/wanted