@kylen12 said in Connecting Playstation 2 Controller via GPIO Pins:

Do you think it is feasible to have a Python script that would do so?

Probably yes, but I'm not famiiar with the SPI ecosystem on the PI. There's https://github.com/mholgatem/GPIOnext which is a simpler input simulation library (i.e. 1 GPIO line = 1 input/button) and can provide a starting point for the 'virtual' input device creation, but for the SPI part I'm afraid I have no idea.

@retropieuser555 said in MKDD Tint Issue RPI5:

@gvx64 said in MKDD Tint Issue RPI5:

Instructions for Building from Source

cd /home/pi sudo mkdir ./dolphin-rpi/ sudo git clone https://github.com/gvx64/dolphin-rpi cd ./dolphin-rpi sudo git submodule update --init --recursive

I wouldn't use sudo to make the dolphin-rpi directory, you can just git clone straight away. Otherwise it'll mess up all the permissions. Or later in your code the user probably won't be allowed to make the build directory

cd ~ git clone https://github.com/gvx64/dolphin-rpi cd ./dolphin-rpi git submodule update --init --recursive

Thanks, I agree with this. I will modify Post 42 to remove the unnecessary directory creation from the instruction set when I have some time.

@mitu yeah i think, because i configured it normally, but dosen't work after some reset,

@mitu Actually I've been trying to get that working. I also have a RPI 2 (?) or something, which I've installed Raspberry Pi OS on. If I put that card into my RPI 2 I can ssh in and I still couldn't get the screen working.

If I put the same SD card (AFAIK the image you install is the same? I use Raspberry Pi Imager) in my RPI 4B I can't SSH in because the standard password somehow isn't 'raspberry'? I even reinstalled. Either way I can't get anything to show up on the screen with either of the pi's. I think it's DOA, but the company I got it from is not responding to me anymore.

@mitu thats sad, wish I knew how to code for it, as Elan Performer software takes midi-in. Great for triggering animations. Not to mention Octamed audio tracker for making music :(

Any idea what would it take to do, is it scripting or C+ coding. etc?

Some refs I have found:
https://github.com/midwan/amiberry/wiki/Serial-Port-support
and for a PC/Ami emulator:
https://www.amigaforever.com/kb/13-107
and this for Linux/Amiga:
https://mathr.co.uk/blog/2019-12-10_midi_network_between_linux_and_amiga.html

@StoqnS14 We don't support this configuration and OS. Use either RaspiOS or the RetroPie image from https://retropie.org.uk/download and you'll not have issues.

@mitu Hey, that did the trick, thank you very much, sir !!!!

bear in mind that even audiodriver=alsa causes a noticeable performance loss vs audio_driver=alsathread on a pi4. if jack is more demanding that either, it would be a non-starter.

@theatomicfire said in Trying to make my own motion control with retropie:

However, I have been running into problems getting the gamepad "configured" within retropi. I created cfg file for my "input device" which retopi recognizes, but none of the commands i input through the script actually go through

Do you mean EmulationStation will not recognize and configure your input ? Is your device working with jstest or sdl2-jstest ?

Do you have any ideas as to how I could implement this?

Difficult to say without any more details or a look at the code you used.

@mitu
Yes it turns out that the custom Retropie xpad driver was the culprit. I was pointed to this issue thread here, https://github.com/RetroPie/RetroPie-Setup/issues/3379

I tried uninstalling and once again my XBox One controller worked fine with the program im working on (Chiaki)!

I'm still waiting to hear if that solves my user's similar issue as well.

Thanks!

@baconbandage Run the following command - with the gamepad plugged in - and post the output

cat /proc/bus/input/devices

Try testing the gamepad with the jstest utility. Exit EmulationStation and run

jstest /dev/input/js0

You should get a listing with the gamepad's input types (buttons/joysticks/etc.) and you can press the buttons/D-Pad/move joysticks to see if they are registering. You can exit the test by pressing Ctrl+C.

@mitu said in Razer Atrox Arcade Stick Help:

@Sircoynie said in Razer Atrox Arcade Stick Help:

I have seen a thread about this on here gut it gives no explanation on how it was solved and is very old.

I think the solution was to mod the stick with an IPAC usb encoder.

So i bought some electronic switches and a custom usb keyboard encoder (ipac2), installed it in my atrox and ended up with a fully working xbox one and raspberry pi machine.

Can you try to test the controller with jstest, from the command line and see if the inputs are registered ? Exit EmulationStation and run from the terminal

jstest /dev/input/js0

You can exit the test by pressing Ctrl+C.

I will give that a try and get back to you thanks.

@spacebiscuit there is no 'main rom' for MAME/arcade. 'outrun.zip' will have many variants with different contents with exactly the same name. outrun.zip from MAME 0.37b5 will not be the same as outrun.zip from MAME 0.220, for example. there will be a version of outrun.zip that runs in FBNeo - it is the one with the romset version listed here: https://retropie.org.uk/docs/FinalBurn-Neo/

there's no need to do trial and error and trying different MAME/FBA emulators, you simply download the romset collection for the emulator you are trying to use.

@ironsocks

retropie 4b 8gb
sd image made from retropie.org
retropie 4.7

***I am using an oem nintendo wii sensor bar that was modded to work in a standard usb A ports and NOT a Dolphin bar. This was done by cutting off the wii proprietary connector and soldering the wires into a usb A connector as well as removing 4 LEDs out of ten to bring the voltage down to under 5v. It works perfectly fine for wiimote tracking.

Almost all the guide I see for using wiimotes in lightgun games such as duck hunt use a dolphin bar and not a standard wii sensor bar. why am i using an oem sensor bar? because the dolphin bar went way up in price after the tariff war with china, and I have quite a few oem wii sensor bars so why not.

Have you figured this out yet? Using wminput method I was able to get the wiimote to work as a mouse tilt wiimote up and down side to side left mouse button mapped to wiimote button b and right mouse button mapped to wiimote button a. the other buttons and d pad on the wiimote are mapped to keyboard keys. No thanx to the guide I followed which you referenced here with the 3 different methods on it.

You have to read up on the wminput github page as to how to get the wiimote to map as a mouse/keybpard vs a joystick. You need to use Plugin.acc.X = REL_X
Plugin.acc.Y = REL_Y and map at least a left mouse button to a wiimote button. This turns the wiimote into a mouse/keyboard configuration and this works in lxde in the Retropie menu and in the retroarch menu in game but wont work as a controller or mouse to use in games such as duck hunt.

I could also use the motion/tilt as a joystick input using Plugin.ir_ptr.X = ~ABS_X and Plugin.ir_ptr.Y = ~ABS_Y in the wii button mapping config file. This works in retropie menu and in the retorarch menu as well as being able to somewhat control a game in an emulator BUT still doesnt work as a pointer or mouse in duck hunt. So you still can't use it as a shooting device.

I have tried a couple different new emulators along with different configurations in retroarch to try to get this wiimote to work as a mouse in the duck hunt game. It works fine everywhere else as mentioned but not in the game. This is so frustrating.

hey guys,

jumping in here as well. just bought a Madcatz FightStick Tournament edition PS3 which is running fine on my mac. It's recognized as gamepad in ES but does not give the option to be configured, pressing any button does not do anything.

Is it still required to install mentioned additional libs or are they included in the default image?

btw. I am using rp4, 4 GB RetroPi Version 4.7.1.

Thanks!

Did anything change in the dmesg and/or tail output?

@petrockblog Thanks so much!

@swimdad84 it looks like it. You can also plug your phone into that dongle too to test it I suppose or just plug the pi into it.

Edit: So as to what mitu and the others spoke of, I feel so dumb. Like I said earlier, I was able to boot into noobs just fine, and I had raspbian full installed at the same time as my retropie. I tried accessing the files for retropie that way earlier to see if I could recover my retropie or change configs or remove powerblock drivers, etc... But the issue I had was nothing showed up under the Raspbian desktop file manager earlier. I reinstalled everything after having lost it all earlier, and when I reset up my raspbian desktop just now, I got a link for retropie on the desktop. GO FIGURE, it only showed up after updating and rebooting raspbian desktop....
Since i rarely ever use the desktop os and mainly only ever use retropie, it didnt cross my mind to try updating and rebooting raspbian and see if I could access those files again. So to reiterate, as the others have mentioned if anyone ever stumbles across this and is in the boat I was in, if you're lucky enough to have raspbian installed as well as your retropi, you CAN access your retropie files and fix the mess as mitu said. Hopefully this saves someone else 6hrs+ of recovering lol.