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
Is your enhancement related to a problem?
Speed Indicator added in 3.14 is a sub-control of the Stance Indicator, which means its visibility is subject to the mission's difficulty settings having the stance indicator enabled. This also results in the Speed Indicator not being shown unless there's been a recent stance change if the stance indicator is set to fade-out.
Solution you'd like:
Tie the Speed Indicator to another class of RscInGameUI (RscUnitInfoSoldier seems most appropriate), or make it its own class entirely, like Advanced Fatigue's Stamina Bar.
Alternatives you've considered:
It's possible to disable the Stance Indicator via Selective UI while having it enabled in difficulty settings. This doesn't account for the fade-out possibility.
Additional context:
The medical feedback indicators (fractures, blood volume, splints, tourniquets) suffer from the same issue.
The text was updated successfully, but these errors were encountered:
Is your enhancement related to a problem?
Speed Indicator added in 3.14 is a sub-control of the Stance Indicator, which means its visibility is subject to the mission's difficulty settings having the stance indicator enabled. This also results in the Speed Indicator not being shown unless there's been a recent stance change if the stance indicator is set to fade-out.
Solution you'd like:
Tie the Speed Indicator to another class of RscInGameUI (RscUnitInfoSoldier seems most appropriate), or make it its own class entirely, like Advanced Fatigue's Stamina Bar.
Alternatives you've considered:
It's possible to disable the Stance Indicator via Selective UI while having it enabled in difficulty settings. This doesn't account for the fade-out possibility.
Additional context:
The medical feedback indicators (fractures, blood volume, splints, tourniquets) suffer from the same issue.
The text was updated successfully, but these errors were encountered: