Decide whether to expose MangoHud-native preset semantics in the UI #3

Open
opened 2026-03-31 03:05:04 +00:00 by 44r0n7 · 0 comments
Owner

MangoTune profiles now behave as a library of real MangoHud .conf files stored under MangoTune's own profile directory and applied into the active config target.

Still unresolved:

  • whether MangoHud's own preset feature should be exposed directly in the UI
  • how to explain MangoHud launch-time config/profile precedence without confusing it with MangoTune profiles

Goal:

  • keep the UX clear and avoid overlapping profile/preset concepts unless there is a strong product reason to expose them
MangoTune profiles now behave as a library of real MangoHud `.conf` files stored under MangoTune's own profile directory and applied into the active config target. Still unresolved: - whether MangoHud's own `preset` feature should be exposed directly in the UI - how to explain MangoHud launch-time config/profile precedence without confusing it with MangoTune profiles Goal: - keep the UX clear and avoid overlapping profile/preset concepts unless there is a strong product reason to expose them
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: 44r0n7/mangotune#3