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
vkBasalt supports toggling its effects on and off with a keypress, but MangoHud always shows "vkBasalt: on", regardless of effect state. One could argue that vkBasalt is "on" as soon as its lib is loaded - which is how the current indicator logic queries vkBasalt state - but it'd be nice if it accurately reflected wether vkBasalt's effects are on or off.
I'm surprised this hasn't been raised as an issue yet, because I just spent about half an hour trying to figure out why the vkBasalt toggle doesn't work, when infact it was working (FXAA turning on and off once I actually took a good look at the output) and I've just been staring at "vkBasalt: on" like an idiot the whole time. Maybe I need glasses, dunno.
The text was updated successfully, but these errors were encountered:
vkBasalt supports toggling its effects on and off with a keypress, but MangoHud always shows "vkBasalt: on", regardless of effect state. One could argue that vkBasalt is "on" as soon as its lib is loaded - which is how the current indicator logic queries vkBasalt state - but it'd be nice if it accurately reflected wether vkBasalt's effects are on or off.
I'm surprised this hasn't been raised as an issue yet, because I just spent about half an hour trying to figure out why the vkBasalt toggle doesn't work, when infact it was working (FXAA turning on and off once I actually took a good look at the output) and I've just been staring at "vkBasalt: on" like an idiot the whole time. Maybe I need glasses, dunno.
The text was updated successfully, but these errors were encountered: