@csl

No problem but I think we see things from a much different angle.

I don't know the exact answer, you should ask a "global moderator".
But, I think, it basically comes down to how much time the developers can or want to spend and what they think what should be added or not.

And when something isn't there, some people become developers themselves.
Perhaps you can contribute to the open source community too.

I think you can just add gameandwatch in line 50 of /home/pi/RetroPie-Setup/scriptmodules/libretrocores/lr-mess.sh
I haven't tested though !
Let me know if it works for you, perhaps we can learn from this.

https://github.com/digarok/gsplus/issues/52

bringing this thread back from the dead, as i encountered the same issue on my pi zero. any updates?

Now that I am back to playing with Wayland/Sway, I found the best solution is what @etheling was doing...using imv as the image viewer. The difference is that I am using runcommand-onstart.sh to display the loading screens so I don't have to mess with editingruncommand.sh. The key is to NOT name you launch images *-launching.png (I use *-launch.png) as this will invoke feh via runcomand.sh.

#!/bin/bash ROMPATH="$3" ROM_BN_EXT="${ROMPATH##*/}" ROM_BN="${ROM_BN_EXT%.*}" LAUNCHIMAGE="/home/pi/RetroPie/roms/$1/images/$ROM_BN-launch.png" imv-wayland -f -s full -x "$LAUNCHIMAGE" & &>/dev/null IMG_PID=$! sleep 4 imv-msg "$IMG_PID" "q"

@oleguer try again in another year or two when the emulator has been completed/optimised/ported
EKA2L1
It's still early days but at least there is some hope

So in creating PBP files are they compatible with real PSP hardware running CFW?

@jimmyfromthebay

They say that rats are intelligent.
So you have to train them, not to bite the cables.;-)

@crush Hah, I have the same one for more than 10 years now. Its a great wheel and still works perfectly. 👍

@dmmarti

I found that some games require touch or mouse.
I have experimented, but I didn't find a solution.
Can you have a look ?

@muldjord

I understand that i can load it along side it. But it would be nice to have inside of steamos and just click on it from the library. It seems that RetroArch is jumping on it. That's why I asked, but they seem to be doing it from the windows point of view. like i said it would be nice to have it support in steam not a side load. that's all.

@langest I think I just used the guide above. It's been a while so I don't really remember too much.

@buzz yes please do let me know when you do so. I'll keep on the lookout as well. I understand wanting to keep things central (don't want malicious code uploaded in binary form run on peoples devices).

Glad to hear that its on your mind though (binaries for additional systems/architectures would be much appreciated).

I guess another alternative would be changing the scripts so more that one binary repo could exist (user could supply one through some config)... though that is a niche use case especially if you plan on expanding the number of devices you build for yourself in the future.

A IPS panel may be the best match for your setup (but with a higher price tag), or you go with a good (read: with a high viewing angle) TN panel.
(NB: Both techniques are of the TFT-LCD family. An LCD can be backlit by LED or by flourescent lamps. The latter are the bulkier and heavier flat-screens.)

Despite the fact that they want to sell their monitors, this article gives a not too technical overview about the panel types: https://www.viewsonic.com/library/photography/what-is-an-ips-monitor-panel/

Regarding the slower reaction time of the IPS in contrast to TN: I guess this can be neglected for retro games, which were developed when TVs with 50/60Hz were to be found in a household.

Maybe you can lend a TFT with IPS panel or know someone with an Apple device (Retina display) to evaluate the IPS capabilities, or can view the different panels in a consumer electronics store before making a buying decision.

One more thing: Depending how "noisy" your place is in terms of other bluetooth / wireless signals it may be advisable to use a dedicated USB-Bluetooth and/or USB-Wireless dongle, but this can be changed even once your arcade is built.

@samco friend, I’m looking at your videos about your samco project since 2016 videos.
This concept almost same with wiimote and dolphin bar right?
I has a big problem with wiimote and dolphin bar.
If I use 1 wiimote as a lightgun, it works properly.
But after I connected the 2nd wiimote the crosshair always merge beetwen player 1 and player 2.
I’m already change the dolphin bar mode (1-4)
What I want to ask is, is the wiimote not supported for 2nd players at retropie ? I’m affraid if I build the samco project I will experience the same things.

@clyde said in Any Ideas for a name for my arcade cabinet.:

@retroeddie Impressive. I couldn't do that. 👍

Yep agreed, cracking job.

@mitu

Ok I see.
So, EmulationStation and its emulator cores use ALSA and not PulseAudio so I shouldn't be doing anything with PulseAudio to get the switching to Bluetooth output.

I should just focus on getting ALSA to work with my Bluetooth headphones.

I just found out about this while installing retroarch on my tablet, super impressed with it, i really hope this will be included into retropie sometime soon.
Thanks for the instructions of adding it ourselves.

@dmmarti said in Music, Video, Photo & Comic Support (Submission):

@Rydo

Can I ask how you determined the following values?

/dev/input/jsX 0x3C 0x3E 0x2B 0x2D 0x70 0x71 0x69 0x6F

On a fresh RetroPie image using a wired Nintendo Switch controller, my button assignments do not match up to yours.

My device name is:

deviceName="BDA NSW wired controller"

So I'm curious how you determined those hex values.

Thanks,

David

The joy2key program is hard programed.
/dev/input/jsX means it is applied to all Linux joystick.
The hex escape codes are ansi keyboard codes for keypresses that overlay buttons in the order of 'left', 'right', 'up', 'down', 'a', 'b', 'x', 'y'

0x3C 0x3E 0x2B 0x2D 0x70 0x71 0x69 0x6F

I would suspect your buttons are backwards (Japanese style) so I would move the value around like this.

0x3C 0x3E 0x2B 0x2D 0x71 0x70 0x6F 0x69

@carlos0371 I left the recalbox-script in original state. So there it reboots the whole Pi