Jump to content

All my products and services are free. All my costs are met by donations I receive from my users. If you enjoy using any of my products, please donate to support me. My bare hosting costs are currently not met so please consider becoming a contibuting member by either clicking this text or the Patreon link on the right.

Patreon

Recommended Posts

Posted

I'm relatively new to xpadder so I might be missing something obvious, but I can't figure out what it is. I have xpadder set up by itself with a profile for 3do saved, and that works fine. I have freedo working in gameex with closemul v3 using advice found on these forums (was originally going to use freedowrapper, but then links I found didn't work so I discovered closemul in another post here), and it works great. However, I'd like to use xpadder in addition due to freedo not supporting gamepad input. When I edit gameex settings to run xpadder before or along with closemul for freedo, something strange happens. The screen freezes and only allows me to hit escape to exit back to gameex. When I exit gameex xpadder is running fine in the system tray minimized, with my gamepad profile loaded just like I wanted. When I exit xpadder, closemul takes over instantly and runs freedo and the game I had selected.

I've deleted the run before/run during setting in gameex to test what is going on. I deleted those settings, then opened my 3do setting in xpadder. Then I ran gamex, ran a 3do game, and closemul took over right away and ran it fine like I want it to. The controls on my gamepad worked as well this way. However all of this eliminates what I want to do, which is only open xpadder WITH freedo using closemul, load my 3do profile, play the game, and then kill xpadder on exit of the game (all within gameex).

If anybody has any idea why closemul hates xpadder so much please reply. I'm open to any ideas or suggestions.

Posted

Of course a bit later and I figured it out myself. It turns out it had nothing to do with closemul. I had to have xpadder running already from windows startup (before/during gameex loads), and then in the emulator configuration I put the "launch before" command in for the emulator profile. I then added a dreamcast xpadder profile and tested the switching between the two and it worked perfect! I kept xpadder running the whole time, never telling gameex to kill the process. By loading the profile in each different gameex emulator config (launch before), it switches smoothly.

Guest
This topic is now closed to further replies.
×
×
  • Create New...