Emulator Issues #1960
closed
Dolphin not properly saving config (Dolphin.ini)
Added by cacofff almost 15 years ago.
Relates to performance:
No
Relates to maintainability:
No
Description
Whatever setting I try at the Plugins page, even if I delete Dolphin.ini
and try a different config, this part of Dolphin.ini ends up saved like this:
GFXPlugin = Plugins/Plugin_VideoOGL.dll
DSPPlugin = Plugins/Plugin_nJoy_SDL_Test.dll < there should be a DSP
plugin here
Pad1Plugin = Plugins/Plugin_PadSimple.dll
Pad2Plugin = Plugins/Plugin_nJoy_SDL_Test.dll < there should be a GC
pad plugin here
Pad3Plugin = Plugins/Plugin_Wiimote.dll
Pad4Plugin =
WiiMote1Plugin = Plugins/Plugin_Wiimote.dll
OS: Windows XP x64
Haven't tried Dolphin since 500 revisions ago, so i don't know where this
started.
This affects the [Config...] buttons' behaviour since these check the
selected plugin from the ini file instead of the created (temporary)
fields. So I click DSP Config... and get NJoy properties.
*correction
Pad2Plugin = Plugins/Plugin_nJoy_SDL_Test.dll
Pad3Plugin = Plugins/Plugin_Wiimote.dll < there should be a GC
pad plugin here
you should delete that SDL_Test plugin you have there :)
I know it's not working. Just a way to showing that it happens even if I manually
modify the ini file to use multiple pad plugins and open/close Dolphin.
Now something interesting, if i write anything to DSPPlugin:
DSPPlugin = test
Pad1Plugin = Plugins/Plugin_PadSimple.dll
Pad2Plugin = Plugins/Plugin_PadSimple.dll
open/close dolphin
this happens
DSPPlugin = test
Pad1Plugin = Plugins/Plugin_PadSimple.dll
Pad2Plugin = test
Same goes for Pad3Plugin reflecting the Wiimote1Plugin
can you test with r4754, r4755?
AHA! Changing the MAXPADS define back to 4 did it.
While you're at it, check this patch. It lets you pick what pad plugin to choose for
each individual player without going to the ini files, Although the [Config...]
button still redirects to Pad1 config.
Patch includes the MAXPADS thing.
Besides, MAXPADS and MAXWIIMOTES are defined to be 1. No matter what you do, Dolphin
will (should) not use anything else than Pad1Plugin and WiiMote1Plugin.
With r4789, theres nothing in the code that obviously changes that. If anything does,
its a rather well-hidden bug, overwriting memory.
Hmm, didn't see that reply before. I'm not so sure if changing the MAXPADS define to
something else is that useful. Especially since there is not mapping between the
controllers connected in the GC tab and the Pad Plugins you just patched.
It did fix my issue, also, ConfigMain uses MAXPADS a couple of times there to
check out what plugins are assigned to individual pads.
Setting it to 1 (as of r4755) kills the Multi Pad Plugin feature.
with the changes in r4755, only the first pad plugin would be unloaded...
- Status changed from New to Fixed
Also available in: Atom
PDF