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
I use Optifine mainly for connected textures, I know I shouldn't but life is life.
Just before main menu, my log is spammed (+50 000lines) for about 15sec with this error msg : [Client thread/INFO] [STDERR]: [mirror.normalasm.client.sprite.FramesTextureData:load:167]: at net.minecraft.client.renderer.texture.TextureAtlasSprite.func_110970_k(TextureAtlasSprite.java:349)
while spamming, client seems to freeze, it happens right before main menu.
It makes freeze my Launcher (PrismLauncher) too.
I tried disabling "B:releaseSpriteFramesCache". Error disappeared, loading is faster. (And the game seems rendering faster but i'm not sure)
G1ll0u
changed the title
[BUG] Extreme log spam caused by Optifine loading in conflict with releaseSpriteFramesCache
[BUG] releaseSpriteFramesCache causes log spam while Optifine loads things
Jul 16, 2024
Hello,
Here's a bug report! :
I use Optifine mainly for connected textures, I know I shouldn't but life is life.
Just before main menu, my log is spammed (+50 000lines) for about 15sec with this error msg :
[Client thread/INFO] [STDERR]: [mirror.normalasm.client.sprite.FramesTextureData:load:167]: at net.minecraft.client.renderer.texture.TextureAtlasSprite.func_110970_k(TextureAtlasSprite.java:349)
while spamming, client seems to freeze, it happens right before main menu.
It makes freeze my Launcher (PrismLauncher) too.
I tried disabling "B:releaseSpriteFramesCache". Error disappeared, loading is faster. (And the game seems rendering faster but i'm not sure)
Here is my debug log of 135'000 lines that didn't fit on mclo.gs :
https://kdrive.infomaniak.com/app/share/592874/5c08ee43-3ff9-4bca-ad5a-7d7bc8651d6c
I'm using resource pack "Conquest Reforged" that has a lot of Optifine specific things.
I'm using Complementary Shaders v4.7.2 (I know it doesn't help but I never know)
The text was updated successfully, but these errors were encountered: