From the mod's description, BadOptimizations will not calculate data if the debug hud is not open/rendering in order to cut down on lag. So, I'm guessing that the {gizmo} variable is trying to retrieve data that isn't currently being calculated, as a result of the debug hud being closed.
Using this profile I found in documentation, this is what I see.
I can see part of the gizmo in the top left, however it is static and does not update when I look around. When I press F3 to view the debug hud, the debug gizmo works as intended. After I close the debug hud and the custom hud unhides, the gizmo did not update nor assume its last data (when in F3).
Did you try this without the mod, I believe the bug is still there. This is fixed in the v4 betas which can be found in my discord server. Hoping to have it ready for a published release soon-ish though
From the mod's description, BadOptimizations will not calculate data if the debug hud is not open/rendering in order to cut down on lag. So, I'm guessing that the
{gizmo}
variable is trying to retrieve data that isn't currently being calculated, as a result of the debug hud being closed.Using this profile I found in documentation, this is what I see. I can see part of the gizmo in the top left, however it is static and does not update when I look around. When I press F3 to view the debug hud, the debug gizmo works as intended. After I close the debug hud and the custom hud unhides, the gizmo did not update nor assume its last data (when in F3).
With BadOptimizations (mod):