Im getting further with the dolphin player 2 setup, but have a question, in your final steps you mention pushing a joystick button, nbut i have the two side buttons on my aimtrak configured for mouse middle and mouse right...are you not supposed to do that for player 2 with dolphin? in the other emulators in the read me you mention setting the buttons to mouse right and mouse middle, so i did that for both guns. If i change aimtrak config to make the buttons on the side joystick buttons and not mouse buttons, then the presses are seen in the dolphin config tool..
Yes, in fact Aimtrak buttons can be assign either to one of the mouse button (left/middle/right) or to one of Aimtrak's emulated joypad buttons.
Usually Trigger is set to left-click onscreen, and right-click outscreen
Then according to the gun housing, users have more or less physical buttons to assign (and so twice as virtual buttons with onscreen/outscreen)
Dolphin, when set to use a SDL joystick, will recognize in its settings windows
only emulated joypad buttons (not mouse click, that's normal for a jostick...). But, in fact, it does not matter as DemulShooter gets both guns mouse events and inject data directly into Dolphin's memory. Dolphin then thinks that a joypad button has been pressed even though it was a trigger/leftclick that DemulShooter transformed.
It's the same for P2 axis, with an aimtrak set a "mouse emulation" there is no Joypad Axis movement recognized in Dolphin's setting sceen. DemulShooter is making the word to feed it by getting mouse coordonates
That's why I have to give you a pre-made config, as the joypads buttons (in process memory) to redirect mouseclicks are fixed in the code
One issue with all of this is not to feed Dolphin but
WHERE, in memory, to feed.
Forget what I told you earlier : that's was too much unclear and - finally - not pertinent.
And yes yes of course let your trigger and buttons set to mouse click with the aimtrak software (other emulators won't work if not !). I was talking about other buttons (maybe you do not have more on your guns !) that could have been set to Joypad buttons.
1) If i run the demulshooter config to replace the controller config, then i open demul 4.0.2. I can see the P1 controller settings are set as expected. At this point, if i move my mouse, or either aimtrak gun, the little red dot on the wiimote config screen moves around the square as normal.
2) Next while leaving dolphin open, i run demulshooter -target=dolphin -rom=ghostsqu from command line. Now, the mouse and P2 aimtrak stop controlling the red dot on the wii mote config screen. The P1 aimtrak moves the dot, which to mean, means demulshooter is doing its job (great!)
3) I then start ghosesquad, get to the start screen, hit + on my keyboard, but the p1 aimtrak no longer controls the cross hair in game. I have a feeling that when i thought it was working for p1 previously, i had forgotten to start demulshooter maybe, and it was just the standard mouse control i was seeing.
Untill here, everything's normal, yes !
4) For P2, I have found that if demul shooter is not running, and i use the aimtrak config utility to set the side buttons to button 1 and button 2, then the dolphin config registers the button presses. If i have demulshooter running, it does not detect them, Changing the buttons in aimtrak utility back to mouse middle and mouse right also fail to have any impact
No more detection is normal, SDL inputs are blocked and only DemulShooter feeds the emulator with button pressed data.
what should happen though, is for you to see some buttons become red even if a mouse click is pushed as it should be transform into a (B) press (for left click for example)
To make it quick I can give you 2 "solutions" :
1) in the Wiimote settings, note all the SDL devices seen by Dolphin.
Than for each one, edit the WiimoterNew.ini and write it's ID, run DemulShooter, run Dolphin and see if P2 works. I cannot do more with this
I don't really understand how dolphin affects controllers, sometime it swaps them in it's process memory
2) Wait a little for me to release v4. I nearly finished Dolphin 5.0 support and there are a lot of changes in the way they handle Devices.
I don't say it will work better, but it's different
EDIT : Oh, and out of curiosity, try to run DemulShooter with the
-v option and copy here the debug file. It may contain some info regarding Dolphin address errors