After applying/restoring one of MangoTune's saved profiles, the actual HUD order from that profile is reflected correctly in the running preview, but Tools -> HUD Order does not show the same order.
Observed behavior:
Apply/restore a saved profile whose config file has a known non-default HUD order.
The preview updates and shows the expected restored order.
Open Tools -> HUD Order.
The list shown there does not reflect the restored order from the active config.
This looks like a UI state/derived-order mismatch rather than MangoHud ignoring the order, because the preview itself is correct.
Likely investigation points:
HUD Order page may be rebuilding from stale state after profile apply/restore.
The page's visible-group order derivation may not be re-run after config replacement.
Profile restore/apply may update preview/runtime state without fully refreshing the page model.
Acceptance criteria:
After profile apply/restore, HUD Order immediately shows the same order that the preview and current config now use.
No manual page switching or extra apply step should be required.
After applying/restoring one of MangoTune's saved profiles, the actual HUD order from that profile is reflected correctly in the running preview, but `Tools -> HUD Order` does not show the same order.
Observed behavior:
- Apply/restore a saved profile whose config file has a known non-default HUD order.
- The preview updates and shows the expected restored order.
- Open `Tools -> HUD Order`.
- The list shown there does not reflect the restored order from the active config.
This looks like a UI state/derived-order mismatch rather than MangoHud ignoring the order, because the preview itself is correct.
Likely investigation points:
- `HUD Order` page may be rebuilding from stale state after profile apply/restore.
- The page's visible-group order derivation may not be re-run after config replacement.
- Profile restore/apply may update preview/runtime state without fully refreshing the page model.
Acceptance criteria:
- After profile apply/restore, `HUD Order` immediately shows the same order that the preview and current config now use.
- No manual page switching or extra apply step should be required.
Resolved. HUD Order now reflects the restored/applied profile order correctly again, and the related HUD Order navigation/live-update regressions addressed in the same pass are stable with cargo fmt --all, cargo test -q, and cargo clippy --all-targets -- -D warnings passing.
Resolved. `HUD Order` now reflects the restored/applied profile order correctly again, and the related HUD Order navigation/live-update regressions addressed in the same pass are stable with `cargo fmt --all`, `cargo test -q`, and `cargo clippy --all-targets -- -D warnings` passing.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
After applying/restoring one of MangoTune's saved profiles, the actual HUD order from that profile is reflected correctly in the running preview, but
Tools -> HUD Orderdoes not show the same order.Observed behavior:
Tools -> HUD Order.This looks like a UI state/derived-order mismatch rather than MangoHud ignoring the order, because the preview itself is correct.
Likely investigation points:
HUD Orderpage may be rebuilding from stale state after profile apply/restore.Acceptance criteria:
HUD Orderimmediately shows the same order that the preview and current config now use.Resolved.
HUD Ordernow reflects the restored/applied profile order correctly again, and the related HUD Order navigation/live-update regressions addressed in the same pass are stable withcargo fmt --all,cargo test -q, andcargo clippy --all-targets -- -D warningspassing.