Emulator Issues #8975
closedLock Essential Settings through INIs
0%
Description
Users can't be trusted, therefore we need to help them out sometimes. I propose that we make immutable game settings for games where they are unplayable without X settings. Yes, it will be a judgment call, yes, it'll probably piss off some people. But, at this point, I've been watching my cousins play Dolphin, and it's very, very apparent that we suffer badly with usability issues. They don't know what any of the stuff in the UI means, they don't know what settings do what, we need to make things as easy as possible.
So, we need a second class of "forced" settings in the INI files that basically "lock" a setting in the UI. Opening the graphics menu WON'T override it, rather, the user won't get the option to break it. This is useful because my cousins would have the correct setting, and then change it to the wrong setting because "it's faster" and not realize what broke the game until later.
Here's an example of one I'd force on: Super Mario Sunshine - EFB2RAM + Safe Texture Cache. The game just isn't playable without these settings.
Example of a game where I WOULDN'T force it on: The Legend of Zelda: The Wind Waker - EFB2RAM. It's only needed for a subquest where turning it on for that point is plausible.
What does everyone think? I know it'd be a lot of work to setup at first, but, I think in the long run having immutable settings could be useful.