Open boomercore opened 6 years ago
hizzlekizzle
commented
6 years ago It's looking to my general RA settings for the difference, and ignoring the core's override when it writes the game override, I believe.
That's correct. We don't have any good solution for this problem at the moment, unfortunately.
boomercore
commented
6 years ago Thanks for the quick response. I suppose I'll make these changes manually or in the UI after I load a game then til it's fixed.
hizzlekizzle
commented
6 years ago Yeah, the only other option is to manually add the line to your per-game overrides, though they'll get wiped out if you save another per-game override over the top of it.
boomercore
commented
6 years ago I engineered a solution of sorts, in case anyone's curious: I saved run-head as true with 0 frames to RA's default settings. Then made a core save with run-ahead +1, and the game with run-ahead false. This made it work as it should.
andres-asm
commented
6 years ago This is why I wanted to remove "nesting" But @Tatsuya79 said he used nested overrides so I left it as is.
I have RA set up to not run ahead by default. I have various cores set to run ahead 1 frame. When I try to save a per-game configuration with a run-ahead off (because it might be more demanding or not work right), it won't write a config file with run-ahead marked off. It will save my frames of run ahead count if I make that change, but will not make a flag for run-ahead off. It's looking to my general RA settings for the difference, and ignoring the core's override when it writes the game override, I believe. However, it will still take the core's run-ahead setting.
Was wondering if this issue could be resolved so I could have the core run-ahead by default, but per game disabled if I specify that. Thanks for your time.