Page 1 of 1

Can’t keep setting modifications

Posted: Thu Feb 14, 2013 1:05 pm
by Racotte
Hi everyone,

Thanks for this nice app and for the good job your doing updating it.

For now on I only try FFVII but I experienced some problems with the settings that doesn’t stick when I load the game.

Here is what happens:
- I change the settings
- I restart FPse, check the settings, everything is ok
- I load FFVII, I have a message “!!! Please restart FPse !!! to apply all option for this game”
- If check the settings, all of them are back to default
- If I quit FPse and restart, all settings are back to default even if no game are loaded

I tried to change the setting in-game, save them to default configuration and restore them, and plenty of change/restart but nothing work and I can’t keep the settings I want.

Did someone had already experience this problem? Anyone get a solution?

Thank for your help

Re: Can’t keep setting modifications

Posted: Thu Feb 14, 2013 7:47 pm
by zerostriker
Hello,

I can tell i have the same problem. When i try to change something in the video settings it goes back to default settings, even after restarting or after a reinstall...

I can remember some versions earlier i didnt have this problems..

I am using S3 with 4.1.2, latest FPSE, with the rom Metal Gear Solid, if it helps...

Hope someone can respond please.

Re: Can’t keep setting modifications

Posted: Fri Feb 15, 2013 9:00 am
by akutasame94
My phone is currently being fixed in shop, so I can't tell you for sure, but when you start game go set up your settings and then go to MISC - Save default config... Then your config will be default for all games ;)

Re: Can’t keep setting modifications

Posted: Fri Feb 15, 2013 9:20 am
by Racotte
Hi,

Thanks for your answers.

I have already tried to save the config as default after changing the setting in-game, but if I quit and restart, all the changes are vanished. If I try to restore default config, it didn’t apply the change I’ve made previously…

I have also a Samsung S3 with android 4.0.4. May this problem be specific to S3 ?