@Rinusch thanks again for rephrasing despite my clear lack of understanding. You did right by raising a ticket directly. Somehow I'm still convinced your issue is related to the one I've mentioned earlier about the custom controls. Anyhow thanks for your patience.

@Coldcoat please add some more details about your system as requested in https://retropie.org.uk/forum/topic/3/read-this-first

What hardware are you on and how did you install RetroPie? Please attach the relevant log from ~RetroPie-Setup/logs from when you tried to install Drastic.

@sleve_mcdichael This is exactly what I was looking for. I installed Retropie and about 100 NES, SNES ROMS, themes etc. on a 256 card but looking to do USB rom service on NESPI 4 case on a 256 SSD. Thought I would be able to make an image and then install it on a 128 card but no, Win32diskimager says the card is too small. I thought there is no freaking way this card was too small but now I know it copied the unused sectors too.
Thanks for tip about PiShrink! You hopefully saved me $40 on another SD card! Thanks again!

Ok figured it out.

First step, is to open your router and add your raspberry pi to the port forwarding. This is easy enough, you will want to use the internal IP of you pi, and open port 22 to tcp. you can usually access your router settings via http://192.168.0.1/ in your browser, providing you are wired directly into the router and not using wifi to connect.

Once this is done you will need the external ip. I found it by going on to my retropie under "retroarch netplay".

You will need this external ip to login from the internet.

this site has the steps on creating a new user:

https://humanwhocodes.com/snippets/2021/03/create-user-linux-ssh-key/

Once done you can open putty from any pc connected to the internet and ssh into your pi by using the external ip.

Expose your pi to the internet at your own risk.

@PARALAX yeah, we can't really support you if you're using your own configuration - eg the "correct" BIOS folder for retropie is so because retropie's config heirarchy sets it - if you make your own config it will be whatever you set/retroarch defaults to.

@Ashpool Note that if you were looking into more recent MAME vintages to fix emulation issues present in older ones, FBNeo would be a solid alternative and doesn't have the rotation bug.

@Ashpool said in Fixed IP and disable wi-fi.... how ?:

@DjDiabolik said in Fixed IP and disable wi-fi.... how ?:

My question it's...... it's the wireless connection need for some devices ? Like some joystick or joypad used wireless instead bluethoot?

Not that I am aware of any, but all my controllers are wire based (I am not a Fan of wireless HIDs) - but as long as you are not owing such a device, why not disabling the wifi, as it could always be reenabled again ? ;)

For the moment i have thinks it's best idea to maintain active :)
An Example:
Some time i goes in trasfert to my houses of friends or my brother house and pass whit us some hours on retropie in double :)
In most of cases in this houses i can't connect my Pi4 to a LAN Network if for example we need to add some roms to my collection or something like that and if i disable the wi-fi now how i can re-enable it whiout the possibility to re-edit the config.txt ?

Problably i can do it using a keyboard attach to a usb port......press F4 and do it from console using "nano" but i'm not sure.

Could it be a suggestion ..... why not add a function to activate or deactivate the adapter directly from the retropie-setup?

@niyoki said in joystick has only axis 4 and axis 5 how to configure for linapple?:

... and has 1 hat switch (using axis4 and axis5)

So it looks like axis4/5 are not considered as an analog control, but as a Hat - probably that's why linapple doesn't use them.

Sorry i didn't know that i need a bios file, they are working fine now.

Reading the replies from @doug and @b3n, I've managed to implement the fix by giving a change to the report when the controller is connected.

[48361.273580] usb 1-2.4: USB disconnect, device number 25 [48366.681972] usb 1-2.4: new full-speed USB device number 26 using xhci_hcd [48366.883070] usb 1-2.4: New USB device found, idVendor=054c, idProduct=0268, bcdDevice= 0.01 [48366.883092] usb 1-2.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [48366.883102] usb 1-2.4: Product: PS3 Controller [48366.890323] usbhid 1-2.4:1.0: can't add hid device: -32 [48366.890366] usbhid: probe of 1-2.4:1.0 failed with error -32 [48366.905149] usb 1-2.4: USB disconnect, device number 26 [48367.449946] usb 1-2.4: new full-speed USB device number 27 using xhci_hcd [48367.643118] usb 1-2.4: New USB device found, idVendor=054c, idProduct=0268, bcdDevice= 5.72 [48367.643141] usb 1-2.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [48367.643150] usb 1-2.4: Product: PS3 Controller [48367.654388] input: PS3 Controller Motion Sensors as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4/1-2.4:1.0/0003:054C:0268.0014/input/input47 [48367.706730] input: PS3 Controller as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4/1-2.4:1.0/0003:054C:0268.0014/input/input46 [48367.707515] sony 0003:054C:0268.0014: input,hiddev98,hidraw6: USB HID v81.11 Joystick [PS3 Controller] on usb-0000:00:14.0-2.4/input0

Good: The driver works even with the latest driver available. It just change the report of the given controller, so, other controllers will remain functional.

Bad: The controller only works with the cable and the player's count LEDs turn on in a weird way.

TODO: I still want to make this driver actually doable. Any help will be very welcome.

GitHub: https://github.com/KanuX-14/GeneriKit

Edit: The original driver will be kept. It can be enabled again by deleting the line 'blacklist hid-sony' in /etc/modprobe.d/generikit.conf.

@AlphaBetaPie said in Lethal Enforcers Always Sideways When Loaded in Mame:

I'm wondering why Retropie doesn't come with these other, more compatible cores as their default (instead of Mame). Seems based on what you folks are saying, it's a better option.

it does? lr-fbneo is in the default image and is recommended in the docs

lr-mame2003-plus is an optional install, which makes sense to me as it has an ever-changing romset, so you'd need to manually build it (the ones in circulation appear years out of date). i don't think that's a reasonable expectation for users to do by default.

the same could be said of lr-fbneo, but it appears pretty trivial to acquire near-current sets.

@10vorne you got me on that one.

Yes, the sound issue is a known thing on vice64. I found it when I tried to run Dino Eggs and Beachhead II. It was missing certain effects and voice sounds. Like you, I kept screwing with settings until I found it.

I don't know what's causing the other issue. If F7 works in Bruce Lee, it's not lr-vice. Perhaps it's just how lr-vice is interacting with 7cities?

Try Beachhead II. That's another one that you need function key input to start the game. If it works, you don't need to remap anything.

@10vorne By switching from FastSid to ReSid 6581, the high-frequency beeping in vice x64 is gone.

@Manukan said in Splashscreen Video not playing every time:

@mitu It is still only playing every time, can I start this service earlier in the boot-process to make it more consistent?

Not sure what you mean, the splashscreen service is already started pretty early during the boot sequence.

@10vorne

Hi. Yes they both us the same emulator, but have to be setup specifically otherwise you keep over riding the settings of each. It's tricky at first, but once you get it setup, it works great.

Did you have a look at this to thread? It's the go-to for how to properly setup Atari 800/5200 in RetroPie.

Follow this...

https://retropie.org.uk/forum/topic/22392/lr-atari800-5200-artifacting-basic-and-other-guidance?_=1653829718633

@Chadmon10 said in Retropie won't boot into a rom, tries, then goes to command line.:

/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ megadrive "/RetroPie/roms/megadrive/Sonic The Hedgehog 2 (World).md"

You forgot the ~ in ~/RetroPie/roms/megadrive/Sonic The Hedgehog 2 (World).md.

Solution: Posting this in case someone else runs into this problem.
Apparently the simple explanation is that Moonlight can only read one configuration file. So the solution was

copy the controller config strings of both controllers into one single .map file. in the global.conf set both controllers to use the same .map file (where all controller mappings are stored)

So my global.conf now looks like this:

# global config file for moonlight input = /dev/input/event0 mapping = /home/pi/msigc302.map input = /dev/input/event1 mapping = /home/pi/msigc302.map quitappafter = true

Ok, so the stutter goes away if I set baud rate of Bluetooth to 460800:
Run sudo nano /boot/config.txt and then append the following

# Enable autoprobing of Bluetooth driver dtparam=krnbt=on # Increase Bluetooth baud rate dtparam=krnbt_baudrate=460800

The idea was taken from here: https://github.com/Arkq/bluez-alsa/issues/205

Now only the playback delay left.