@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?

A couple of my favorites:

Logitech F710
https://retropie.org.uk/docs/Logitech-Controller/

Nintendo Switch Pro Controller
https://store.nintendo.com/pro-controller.html

The Logitech is pretty affordable, works right out of the box, and uses 2.4GHz wireless adapter so you don't have to mess with bluetooth pairing. Supports rumble.

The switch pro is more expensive, but the stick would be in a better position for N64 games. It does use bluetooth so it needs to be paired, but I had no trouble with getting it to work.

@erickwilson thank you for the advice. I am currently playing with a temporary keypad. Waiting for some of the retro keypads to come back in stock. Seems like there's a shortage on them right now.

@retropieuser555

Yeah.

I see how you're right on this.

Using the default, built in WiFi, it took 45 minutes to transfer a 500 MB folder.

With the WiFi dongle and the same folder, about 6 minutes.

And with a direct connect with an ethernet cable, less than 30 seconds.

I'm not sure how to test for ping though, but I think I'll stick with the dongle. :)

We don't support 3rd party images, especially the ones loaded with ROMs and sold - RetroPie's image license is specifically non-commercial.
Ask the seller for support.

@mitu I can confirm that works. Thank you!

@dankcushions Thanks for that, clears it up a little bit.

Nobody knows hot to help? Ah the above mentioned combo works with the italian layout which i sat in retroarch otions menu

@gordonfreemanjr said in 8bitdo FC30 not pairing via Bluetooth:

@jplank Was that it?

Someone suggested I SSH into the retropie and go to bluetoothctl and then scan now. I did so and neither of the controllers showed up. I rebooted and tried again, same result. Then I tried one last time to load emulation station and pair the controllers - and it worked right away.

The thing is that I had about 15 tabs open with any youtube tutorial and help thread that I could find and I was trying anything I could find. For me, it wasn't that I changed setting X and then it suddenly started working. I "think" the last setting I changed was when mitu suggested changing the pairing mode. I changed it back to default and had to try a few more times to connect before it finally did. There might have been some resetting in there. All in all, I spent hours trying to get it to pair. I hope you manage to get yours fixed in less time. I hope that helps a bit. Good luck!

@mortalwombat I keep an SSD plugged into my case and it just sits under the TV so you can't see anything for the most part.

If you really want an all-in-one solution, Argon just released a new case that holds an M.2 SSD inside.

https://www.argon40.com/argon-one-m-2-case-for-raspberry-pi-4.html

@redmarsbluemoon Yes, stock Raspbian. No need for userland ds4drv :) Imperceptible latency atlhough I've never measured it, I can easily play even games like Street Fighter II.

Try updating your packages/kernel? apt dist-upgrade and rpi-update.

Also be careful about interference from other wireless sources (Wi-Fi, other 2.4 GHz devices)... Maybe try moving things around and seeing if that helps. Best of luck.

I had issues with Pi4 wifi too. In my case I was noticing it when sending files over Samba from W10 or using FTP, and also scraping problems. I'd get constant disconnects and transfer speeds of around 200kb/s even when it would stay working.

I found mentions online of known issues where noise from the HDMI output can disrupt the wifi signal. Every instance I saw talked about said it was only over a certain resolution (1440 I think), but I decided to try disconnecting my 5" screen anyway, which runs 800x480, and as soon as I did that the speeds went up to around 3-5MB/s and the connection stays stable.

@gordonfreemanjr do you have any other controllers plugged in? Did you map your keyboard as a controller? It may be worth going into RetroPie-setup and resetting your mappings and then remapping just to see if that fixes the light issue.

@quicksilver
It had passed 4 months before I actually tried your fix proposal.
It worked. The X-box controller is now fully compatible. Thank you!

@rodolfoaguilar @Firebird_WS6
I'm summing up what quicksilver proposed.
This solution worked for me.

Plug in a Keyboard While in Emulation Station press F4 to open the Terminal Type sudo nano /etc/modprobe.d/xpad.conf Change
xpad triggers_to_buttons=1 to xpad triggers_to_buttons=0 Press cntrl-x Accept the changes. Return back to Emulation Station by typing emulationstation Restart Retropie.
(In my case, I noticed that the X-box controller had started acting strangely while in Emulation Station.
The D-pad buttons swapped positions in Emulation Station as they were previously in PPSSPP.) Remap the controller in Emulation Station. Remap the controller in PPSSPP if necessary.
(In my case, this was not needed.)

I'm not sure why this issue is affecting some people and not others.
Apparently, the problem is caused by the Trigger buttons somehow.