-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Render Errors with Older World #521
Comments
Hi, first of all thanks a lot for taking the time to make such a detailed error-report! The heightmap NPE has already been fixed with 5bb7a77 and the Self-Supression error has been fixed with d1aba56. You can download the latest build from here: https://github.com/BlueMap-Minecraft/BlueMap/actions/runs/8139906875 Closing this as already fixed :) |
Ah also a note, as i see you are using the "latest" docker container: |
FYI, the newest Snapshot 4.1 is working well. Thanks a bunch! |
What i did / Steps to reproduce
This is my first time attempting to run BlueMap with my Minecraft world originating from 2012. This world has seen a lot of version updates over the years, running constantly. I suspect the
heightmaps
errors below are related to old chunk data, as the errors come up immediately after rendering has started in the oldest parts of this Minecraft world.From here, the logs become more noisy, and it appears that rendering stops. CPU load seems to correlate to this. The web interface appears to remain responsive.
Expected result
More chunk rendering, less log errors.
Actual result
Application encounters multiple errors. Chunk rendering doesn't appear to run for long.
Note: For some reason, the container downloads minecraft-client-1.20.3.jar, when my server is running 1.20.4.
Context
BlueMap Version: 3.20; docker tag 0b73d93fc7c17f6b0e5acbcb5e5c90c1f577c201c7bce3d48fdc3f2045e3f881
Minecraft: Vanilla Minecraft v1.20.4
OS: Rocky Linux 8
I'm working on a Kubernetes PoC. Here's the deployment file.
There's no change in behavior whether SELinux is in enforcing or in permissive mode.
Bluemap Configuration
Comments removed.
core.conf
storages/mariadb.conf
Logs
bluemap.log
The text was updated successfully, but these errors were encountered: