Pingouin7 said:nl255 said:If the ini file is saved in the same directory as nesDS then you wouldn't be able to use it as a DSTwo plugin as the configuration .ini file would overwrite the ini file used by the DSTwo to store the plugin information.
Easy...
Change it so that it becomes nesDS.cfg
Besides, you aren't forced to keep the nesDS.nds file name, you can have the DSTwo plugin be nes.nds and nes.ini while the .ini for the emulator would be named nesDS.ini.
Shouldn't cause problems then.
I think having the configuration file kept in root is better.
ALL of these solutions work — I'm using a DSTwo right now.
What's the point of having a .ini file if it doesn't let you save the screen scaling?
It does let me disable every shortcut though. DIS I LIKE.
I still think my idea of supporting both /DATA/nesDS.cfg and /nesDS.cfg (check in /DATA/ first) is better. Also, it doesn't let you set the sprite rendering method either and quite a few games need it to be per scanline rather than per frame. Not to mention many games have staticy sound (it is very noticable on Batman).