ppsspp
ppsspp copied to clipboard
hrydgard
Add extra configuration files when starting from the command line
What should happen
ppsspp should have an extra configuration file that, when launched from the command line, can load the game's custom diff configuration.
for example:
PPSSPPWindows64 "Silent Hill Origins (USA).iso" --appendconfig=FILE1 PPSSPPWindows64 "God Of War - Chains Of Olympus.iso (USA).iso" --appendconfig=FILE2
This extra configuration file usually only contains the difference from the main configuration file(ppsspp.ini), and has a small size.
Who would this benefit
All users who use a fancy frontend to manage game startup and loading will benefit
Platform (if relevant)
No response
Games this would be useful in
All games
Other emulators or software with a similar feature
No response
Checklist
- [X] Check the latest git build in case it's already implemented.
- [X] Search for other requests of the same feature.
I guess this is for libretro core, since you can create a game-specific's config on the standalone version already
Not only that, the existing stand-alone game-specific's configuration file contains all the configuration, not the reduced size of the diff file,so writing and configuration is not very convenient And only in a specific folder.
It's not all, per game settings contain only settings which are set as a per-game settings, those loads when custom config exists and doesn't need any additional commandline, nor "any work to make it work since it should work" already.
There's a different thing, which works from a very long time, I think even before per-game settings were a thing with the option:
--config="yourcustominifilename.ini"
which does include all since it's basically a path to whole config, but again, this should be unnecessary to use.
When you think about it, appending options instead of including them is kind of counter productive in actual use. I get it, it might "look" neater, however it's part of the software where looks doesn't matter especially in a space of launchers where you set it once and most of the time never look back and it's not practical at all since end user not knowing how options are named in the config files would instead of editing one file which has pretty easy to search and understand english names, have to edit two files or worse read some additional help/guides to get the settings names from and have to repeat that every time he wants to try different options, on platforms which doesn't handle multitasking well this is even worse.
Practical usage of per-game settings makes editing ini files very unlikely in the first place, you're kind of creating issues to invent new ways to get around them when there was no issue to begin with, you can just run PPSSPP, set up your per-game settings(which basicaly works like append as you only change what you want changed from base config in them) then use those per-game config files which should be automatic and not dependant whenever a proper PPSSPP is used or it's buggy-retro core.
Cant be for libretro, retroarch can handle per game options independantly. Also a diff for a file thats a few kb in size when the content is hundreds of thousands of times larger? A saving is a saving but it's not the avocado toast that is keeping you from owning that house.
Retroarch also does that kind of partial overrides and it's a nightmare because you can never know where a user has a conflicting option and the user with an issue most certainly doesnt know.
The reason I mention this requirement is because individual games may only need one that is different from the general settings. For example, God of War, on some low-end devices, it is necessary to reduce the internal resolution to ensure the running speed. In this case, only one configuration needs to be changed, “InternalResolution = x” instead of copying the entire configuration file. This command line startup itself is prepared for enthusiasts who like tossing, and ordinary beginners no need it at all.
Again why even bother editing ini file for changing "only one configuration" when you can just run the actual UI and do the same in a much more comfortable way without copying anything.
We don't really need a third way for storing per-game configs especially since one is really kept only historically(or for some obscure cases) and per-game settings are always the way to go which even if you use a custom launcher that lacks support for editing them can still be used using PPSSPP UI just fine. I think it's an issue about "the way I'm used to from different software is the only way I will accept" even if it's not better in any way, have it's own downsides and can be skipped alltogether by just using UI... .
On a side note, GOW can run even on a potato these days with a built-in improved(vs cwc version) 30 fps compat hack which to some people might be a better alternative to reducing resolution.
Again why even bother editing ini file for changing "only one configuration" when you can just run the actual UI and do the same in a much more comfortable way without copying anything.
We don't really need a third way for storing per-game configs especially since one is really kept only historically(or for some obscure cases) and per-game settings are always the way to go which even if you use a custom launcher that lacks support for editing them can still be used using PPSSPP UI just fine. I think it's an issue about "the way I'm used to from different software is the only way I will accept" even if it's not better in any way, have it's own downsides and can be skipped alltogether by just using UI... .
On a side note, GOW can run even on a potato these days with a built-in improved(vs cwc version) 30 fps compat hack which to some people might be a better alternative to reducing resolution.
Maybe you are just used to ppsspp ui and haven't tried third-party front-end ui. I just kindly remind you that there are many novel things in this world. When God closes a door, he opens a window. Keep an open mind, young man,you will open a new window while the old door is still open.
