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 can reproduce this on Meteor 26.3-14, including with only Meteor and its bundled dependencies. ESP Shader mode fails, while Box and Glow work. Enabling Glow in a second ESP module immediately makes Shader rendering work.
Local bytecode analysis points to LevelRenderer.executeOutline(): it returns early when currentFrameRendersEntityOutline is false. Meteor’s Shader ESP uses a separate framebuffer, which does not satisfy this vanilla outline condition. Glow activates the vanilla outline path, allowing Shader rendering to proceed.
In 26.2-35, Meteor called PreparedFrame.executeOutline() directly. This appears to be a regression in the updated rendering path.
Activity
Ziv-Barber commentedon Oct 24, 2026
Same problem in both Meteor Client 26.3 build 13 and build 14 only if you selecting "shadow" type.
Work around solution: Use "Glow" instead
NameGTHuB commentedon Oct 27, 2026
I can reproduce this on Meteor 26.3-14, including with only Meteor and its bundled dependencies. ESP Shader mode fails, while Box and Glow work. Enabling Glow in a second ESP module immediately makes Shader rendering work.
Local bytecode analysis points to
LevelRenderer.executeOutline(): it returns early whencurrentFrameRendersEntityOutlineis false. Meteor’s Shader ESP uses a separate framebuffer, which does not satisfy this vanilla outline condition. Glow activates the vanilla outline path, allowing Shader rendering to proceed.In 26.2-35, Meteor called
PreparedFrame.executeOutline()directly. This appears to be a regression in the updated rendering path.