Leaves will turn black in LODS with polytone and then spams the logs to an ungodly amount.
Im a resource pack creator and im working on switching from optifine to polytone and so far it works pretty well and actually wasn't expecting the color changes to apply in the LODS as well. However I've have had this really annoying problem where sometimes, when I reload the datapack or resource pack, the leaves in the LODS turn pitch black for some reason. Except that's the least of my concerns. The actual problem is that my logs will spam this message to a ludicrous amount.
16:17:24.030
Polytone
DH-PriorityTaskPicker Thread[1]
Error getting block tint at class_2338{x=-54, y=129, z=126} with colormap Colormap{ID=null, triangular=false, rounds=false, hasBiomeBlend=true, inlined=true}. Was it during a reload?
java.lang.IllegalStateException: Failed to get biome key for biome: net.minecraft.class_1959@13985e7f This means that biome registry returned an empty key for it. How is this possible? Was it not registered? Seriously HOW? Must be due to some mod doing unsafe stuff!! This is NOT a Polytone issue!
at knot//net.mehvahdjukaar.polytone.utils.BiomeKeysCache.lambda$get$0(BiomeKeysCache.java:40)
at knot//it.unimi.dsi.fastutil.objects.Object2ObjectOpenHashMap.computeIfAbsent(Object2ObjectOpenHashMap.java:439)
at knot//net.mehvahdjukaar.polytone.utils.BiomeKeysCache.get(BiomeKeysCache.java:27)
at knot//net.mehvahdjukaar.polytone.utils.LegacyHelper.getBiomeId(LegacyHelper.java:339)
at knot//net.mehvahdjukaar.polytone.biome.BiomeIdMapper.lambda$static$0(BiomeIdMapper.java:22)
at knot//net.mehvahdjukaar.polytone.colormap.IColormapNumberProvider$4.getValue(IColormapNumberProvider.java:121)
at knot//net.mehvahdjukaar.polytone.colormap.Colormap.sampleColor(Colormap.java:176)
at knot//net.mehvahdjukaar.polytone.colormap.Colormap.getColor(Colormap.java:193)
This is what I could copy and paste before the debug window crashes. It will spam this message so fast that my lastest.tx document will reach sizes half of my entire hard drive within hours (The Biggest one I got was around 200 Gigs.) Granted, if I go into the data folder and delete the sqlite file, it will stop but will probably come back if I reload any texture packs or make changes to the datapack. I'll probably post this on the Polytone discord as well since they are a part of this despite the logs saying "This is NOT a Polytone issue!" trillions of times in my logs.
I am using DistantHorizons-neoforge-fabric-2.3.2-b-1.21.1
10 Replies
/logstore
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.These log files are too big to even open let alone send in discord
Don't send latest.log to discord, upload it to mclo.gs
site cant handle it
got the log file to 70 MB and the site just crashes
Hmm, that doesn't seem a normal size for a latest.log file. There must be some rather large errors taking up all your log space.
Probably the errors mentioned in the first message
Yes. It spams that error message to an unworldly degree.
Hmm, I have a suspicion. Try changing the generator mode from Features to Internal Server, see how it goes.
didnt work :/
it mostly does this when I return to the world after I made changes to either the resource pack or the data pack's terrain generation
I know its leaf related because when its happening all leaves in the LODS turn black
I cant be the only one expierencing this am i?