Little Daphne emulator help

roslof

@DingoAce10 Regarding controls, for what it's worth, I'm having the same problem now.

I updated to latest code about a week ago, and since then, the Action button does not appear to be mappable. My dapinput file has not changed in a year, and controls were working perfectly with a Playstation 4 controller prior to the update.

Like you, everything else works except for the Action button.

Anecdotally, it seems to be a new(er) bug, but I wouldn't cry wolf just yet. I did devote a few hours to solving this without finding a solution.

roslof

@DingoAce10 Regar

Okay, regarding controls --
I'm using a PS4 controller, and updated to latest Daphne Source (after a Retropie Script update). I know you're using a different controller, but here is what I have in dapinput.ini for my PS4 controller. These settings now work perfectly for me. Remember, the first two sets of numbers are keyboard codes and the 3rd number maps to a controller button "+1" -- so button "0" would read as "1"... A "0" means, inactive button (more explanation below the output):

[KEYBOARD]
KEY_UP = 273 114 0
KEY_DOWN = 274 102 0
KEY_LEFT = 276 100 0
KEY_RIGHT = 275 103 0
KEY_BUTTON1 = 306 97 1
KEY_BUTTON2 = 308 115 4
KEY_BUTTON3 = 32 113 2
KEY_START1 = 49 0 9
KEY_START2 = 50 0 0
KEY_COIN1 = 53 0 10
KEY_COIN2 = 54 0 0
KEY_SKILL1 = 304 119 3
KEY_SKILL2 = 122 105 5
KEY_SKILL3 = 120 107 6
KEY_SERVICE = 57 0 0
KEY_TEST = 283 0 0
KEY_RESET = 284 0 0
KEY_SCREENSHOT = 293 0 0
KEY_QUIT = 27 113 11
END

So anything with a "0" at the end deliberately does not map to a button.

KEY_BUTTON1 maps to the Dragon's Lair Sword. The number "1" in my configuration maps to the PS4 "X" button (button code 0 + 1 = 1). Games that require more buttons (KEY_BUTTON2 and KEY_BUTTON3) map to PS4 "Square" (code 4) and "Circle" (code 2) buttons respectively.

KEY_SKILL1, 2 and 3 map to the difficulty settings for games like Space Ace (where you could choose "Cadet", "Captain" or "Space Ace"). These map to Triangle, Left Bumper and Right Bumper respectively.

I use the PS4 logo button to exit (code 11)

Hope this is helpful for your controller issues.
-Roslof

grant2258

this subject keep on reapearing i put a pull request in for this on retropies github and it was ignored for months so i just closed it. if you want to fix it compile it from my repo like this. it will also fix analog joystick controls up for directions to be used.

cd /home/pi/RetroPie-Setup/
git clone https://github.com/grant2258/daphne-emu.git tmp/build/daphne
sudo ./retropie_packages.sh daphne depends
sudo ./retropie_packages.sh daphne build
sudo ./retropie_packages.sh daphne install
sudo ./retropie_packages.sh daphne configure
sudo ./retropie_packages.sh daphne clean

DingoAce10

For those still having the problem. I updated the Daphne emulator from the binary and everything is now working correctly.

Clyde

@grant2258 You wouldn't want to add the much-needed joystick selection (i.e. other than /dev/event0) to Daphne by any chance? 😌

grant2258

@Clyde said in Little Daphne emulator help:

@grant2258 You wouldn't want to add the much-needed joystick selection (i.e. other than /dev/event0) to Daphne by any chance? 😌

Well its using sdl I know it isint quite what you asked for but you can changed this one line here to change the joystick for your setup.

https://github.com/grant2258/daphne-emu/blob/fd017595886a6cf55b412c8afd2ca29bb4e4d7e6/src/io/input.cpp#L303

SDL_JoystickOpen(0) is default change t to which one you want for your setup SDL_JoystickOpen(1) ect and just compile the source.

I dont have any plans to change daphne much but its easy enough to set here. I would need to look at the source and add another command line option to do that as the cfg file is read after the joystick init ill leave it in a todo bucket but this should let you change it for now.

Clyde

@grant2258 Thanks! I'll try that. 😊

Clyde

@grant2258 Er … sorry, how do I compile from your repo? sh ./buildme.sh fails, see here for the output. I tried on Kubuntu 18.04.

grant2258

the retropie instructions are above your using retropie use the retropie build scripts. Are you using retropie on x84/64 bit ?

Clyde

@grant2258 Yes, at least for the test above for speed reasons. But I finally plan to compile your daphne fork on my Pi 3b. Sorry, I missed the instructions above. As I understand them, they clone your repo directly to the temp dir Retropie is using for its "installation from source", and then invoke the Retropie installation script for all necessary steps, right?

Do I have to modify your instructions for my 64 bit system? (I can't test it before tomorrow.)

grant2258

never tried compiling this code in 64 bit to be honest i would need to compile it locally to test

Clyde

@grant2258 I did compile your version with SDL_JoystickOpen() set to 1 on my Pi by now. But alas, I can't control the game with my joysticks connected via two DragonRise encoders. For some months now (and maybe since I experimented with lr-daphne), in Dragon's Lair 1+2 and DLE 2.1, any movement from one of the sticks will freeze the video in the games' attract mode as well as in a running game. I can control the games via keyboard, however. Since this happens with your fork as well as the source and binary versions from Retropie, I'll have to fix that before trying to change the joystick detection in your version.

I don't want to hijack this thread with this problem, so I will open another thread about it (not now, since I have to leave soon). If you've any quick idea what may be wrong with my Daphne setup that worked flawlessly before, you may still answer here until I've opened a new thread.

grant2258

Well it could be something in your setup daphne by default uses the first joystick found. I could be any joystick number if you have more setup or custom settings for joysticks. You would need to add extra info to see what joystick sdl is using in daphne. Your problem sounds more liek a config problem or the first joystick isint you dragonrise

Clyde

@grant2258 Thanks for the tips. I'll cobble something together when I have time to collect the necessary information.