New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion: Using custom configs for each packaged game #53
Comments
I'll need to know more about how this is suppose to work and when it's officially supported. |
No worries. All that's needed is to add this to the mgl: I've been using this for each of my custom games: Still uses the folder structure of ao486, but dedicated config files for each game including keyboard to joypad mappings. Probably only needed for games that don't properly integrate joysticks properly. |
I thought same_dir wasn't in main yet |
"I've been using the 0mhz-collection for about two weeks in my Mister FPGA and I'm satisfied. Regarding the setup for each game, I've been doing the following: I exit the game and end up in the prompt, then I call the .bat or .exe of the setup or install and configure the sound and the game as I want. |
That hasn't been added to stable MiSTer main yet. I imagine when it is that it will get added. The thing I need to look at is what happens if you load a game that has a setname defined but you have no existing cfg file for it. I'm hoping it just uses ao486.cfg in that case, but I'm not sure at the moment. I guess 0MHz could just include a cfg in the package that is named the same as the setname if that were an issue. |
Using |
So same_dir is in main now. I guess it would be a pain to update all the existing games (at least, all the ones in 0mhz specifically) but maybe the ones that need/would benefit from it could be updated? Either for custom controls or custom machine configs like running a slower CPU or excluding L1 or L2 cache etc. |
As mentioned in #19 (comment), custom configs can be used to save things like keyboard>joypad button mappings, refresh rates and other game-specific requirements.
Not sure if that variable has been rolled into the stable MiSTer main yet, but might be worth considering if it's not too much of a hassle.
The text was updated successfully, but these errors were encountered: