@mitu Hey there - so just a quick update, I've managed to get the stick working - but it took some effort!

Firstly, you have to the stick into PS3 mode before the emulation station interface will recognise it, even then - it won't appear on-screen as a controller (the UI remains blank as if no controller is plugged in)- but if you hold down a button on the stick - it is suddenly recognised as a Brook PS3 controller and then configuration / calibration can start.

Emulation station refuses to recognise the L2 or R2 buttons, but you can configure the rest.

However I have noticed that it is then possible to get these buttons recognised after if you manually configure inputs in RetroArch(?) interace (the one with the green pixellated text that you access from in-game) - then with lots of fiddling around you can finally get the Wireless Brook Board working as a retro pie controller (as a wired PS3 controller)

I will try jstest next

Sorry for not posting details on setup - it's a RP4, with offiical usb-c power supply, (but was testing on RP2 with usb power last night) but will get the rest of the details when I can

@sleve_mcdichael @mitu thanks for the help. I reversed all the changes I made except for the location of the cache, just like in @sleve_mcdichael's example. Everything seems to be working now.

thedudester80 I am trying to create almost the same thing. Did you ever get this working?

@shavecat Delete the AUTOBOOT.DBP file ...

@alphabetapie Overclocking takes hardly any time though, in the scheme of things it isn't anything to worry about so far as having to do it twice goes. It's a few lines of text in a config file.

Yeah, I'd say the vendor probably "locked" their version of EmulationStation and it can't be altered without their action. The free official image as mitu directed is the best option if you want control over your system.

@mitu
I had a pretty bad go of it with this controller. I moved to the ps3controller driver and I did not get that to work per the docs. I tried to sort out which clone I may have, using lsusb, evtest, and dmesg but none gave me any indication other than Sony. So, I tried them all-- Official Sony, shanwan, and gasia. Although I appreciate the info to get additional bluetooth debugging, that project is "crossing the line" with regard to the time I am willing to invest.

Perhaps to make you laugh a bit-- I used retropie for several years with a Logitech F710 controller and an Intellivision Flashback controller. The F710 was getting worn out so I bought another one. It worked terrible! While the new F710 connected no problem, it was very clunky in terms of usability--buttons didn't work quite right, sometimes the control is sticky. Odd! Years ago I had a PS3 and I remember the controller fondly so I thought, I'll try one of those. Needless to say, instead of playing games I'm troubleshooting why this apparently poorly made clone isn't connecting. While the "thrill of the hunt" for the solution to the problem was fun, I'm done.

So, I'm not quite sure which controller I will try next, but the PS3 dualshock clone just found its way to my electronics-recycling box while I sort out my next step.

@rott42 said in Cant get 2 games running, killer instinct and wind jammers:

@adambegood KI 1&2 run for me on lr-mame2003, but graphically compromised, slow and lag. I use pi4.

Fair enough - I thought there was certainly some issue with them.

@mitu I use the rpi3 official image updated to 4.7.11. I haven't added anything extra that wasn't included in that image audio wise.

Please add more details about your setup, as asked in https://retropie.org.uk/forum/topic/3/read-this-first.

@lostless

Thats it! I do know know why I kept getting redirected to the other page. Thank you very much!

@mitu I downloaded the emulationstation for translate and compile it, what line i must change in what file? Thanks.

@sleve_mcdichael

Default will skip roms that have any piece of data from this source, and “only missing” will skip roms that have any piece of data from any source?

Yes, I had actually forgotten that point, it's quite an important distinction.

And you're welcome. Have fun with it!

@ts-x Great idea on dropping in on him. I might just do that. I have a wired number pad that I tried to use plugged into the USB port on my Mayflash (which would also avoid two long wires), but that didn't work. It's not a real USB port apparently. However, it would also be seen as another input device.

This issue is NUTS and across the whole retro industry. Someone needs to do something. Every joystick should come with the ability to ID itself as unique. If say, 8bitdo suddenly started offering controllers that all could send out unique IDs it would be a SHORT wait for someone in Retroarch and others to jump in and support that. That manufacturer would sell a ton of product and force everyone else to adopt that option as it would be SO brain-dead obvious. How has this NOT happened yet???

@hexxur i know there is away to get retroarch installed on it. and i know that it have a doom port built in.
how it works with WADS i dont know

Well, actually after some more research, as of the current version, the 0.11, there si no way to do this, but only when restarting a game already launched, instructions are in the official github project page here.

Please add more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

For the input part - can you get a verbose log from the emulator and see what it reports ?

@jamrom2 What's the name of this script? I thought I found it, but Mobile Gamepad isn't it. heheh

And given that my jzintv looks like crap, what do you recommend to get it right?

@mitu said in runcommand launch art and Skyscraper images:

Are you sure you're modifying the right file ? The file in the $HOME/Retropie-Setup is not used at runtime, it's just the source, when installed it's copied in /opt/retropie/supplementary/runcommand - which is used to for launching.

Aha, yes I was modifying the one in $HOME. I’ll try the one in /opt tomorrow and see if that does the trick.

Edit: I snuck a peek while closing up for the night and that was it, thanks for the tip! Now I wonder if there’s a way to get the transparent background to display as black instead of that light grey...

@ioortropie

Based on your previous answers it sounds like PulseAudio is not starting on its own.

Try systemctl --user enable pulseaudio in the terminal, and reboot.

If you still have no audio please post the output of pacmd list-sinks.