# Use the _fastcall calling convention when interfacing with A68K/Musashi/Doze # Force recompilation of files that need it (i.e. # Include rom set verifying features (comment this for release builds) # Include symbols and other debug information in the executable # Include Toaplan sound sample hacks for games without MCU dumps # Build for Windows XP target (for use with Visual Studio 2012) # Build for 圆4 targets (MinGW64 and MSVC only, this will undefine BUILD_A68K and BUILD_X86_ASM) # Specify the name of the executable file, without ".exe" Uncomment any of these declarations to enable their function. (Intermediary) targets which have their own unique rules # The first pass makes sure all intermediary targets are present. Not the simplest solution but it was fun and the end result is ten times betterĬode: Select all # Makefile for FBA, for use with GNU make Solved: Wiring my own stick and using an IPAC fixed everything. Question is, how do I get the arcade stick to work in piFBA without messing it up for Mame4allpi? :/ The stick directions show on/off readings at 0,1,2,3 and I think piFBA want the analog 32767/-32767 raw axis figures for the joystick input, right? Sudo xboxdrv -detach-kernel-driver -id 0 -led 2 -dpad-as-button -silent & sleep 1īut jstest /dev/input/js0 shows some weird readings and I guess that's where my problem lies. The stick works fine in Mame4allpi with this line in /etc/rc.local Yet I see people using arcade sticks with piFBA so I'm now hoping someone over here could help me out. What am I doing wrong here? I simply can't get my 360 Hori arcade stick working with piFBA on RPi2, I've changed the fba2x.cfg in so many ways that I don't know what to do anymore, and I've downloaded cfg-files that people say fix their sticks, but it still doesn't work.
0 kommentar(er)
