Storage ESP break game render
Describe the bug
I checked without Meteor Client and there are no problems.
Also on older versions of Minecraft with Meteor Client this problem did not exist.
Steps to reproduce
- Join in world when the game is minimized in the background
Meteor Version
meteor-client-1.21.5-16
Minecraft Version
1.21.5
Operating System
Linux
Before submitting a bug report
-
[x] This bug wasn't already reported (I have searched bug reports on GitHub).
-
[x] This is a valid bug (I am able to reproduce this on the latest dev build).
So I found out that this problem is caused by Storage ESP in shader mode.
Very interesting, definitely a driver bug of some sort. If you really want it looked at then we would need a RenderDoc capture of the bug. Without it we can't really do anything.
EDIT: Or you can try updating your drivers if they aren't already or downgrading them if the issue just started happening and you did a driver update.
Very interesting, definitely a driver bug of some sort. If you really want it looked at then we would need a RenderDoc capture of the bug. Without it we can't really do anything.
EDIT: Or you can try updating your drivers if they aren't already or downgrading them if the issue just started happening and you did a driver update.
I have the latest drivers for my vidio card and installing newer versions will break everything else on my system Also this problem was not observed on previous versions of Minecraft with meteor client
Well, as I said, without a capture we can't really do anything. I don't think RendeDoc captures have some sensitive info but if you want, you can send me it in a DM on Discord.
Even then, it is next to impossible to fix without a bunch of trial and error which I don't have the time and motivation to do, sorry.
I don't understand how to run RenderDoc I tried its version compiled on my system but the debugmarker command didn't appear I use renderdoc-git When checking through gdb, the problem did not appear Strangely, I have now been unable to reproduce this problem with a normal launch
Can you test if this still happens as of 64a4bc52d6c00aa9bae032805f2ff344a3eee03c?