@herb_fargus said in USB Controller player order:

we really need to add it as an option to the configuration editor tbh

Yes please :)

Although the ps2 shares the commonality of having a 64-bit processor like the Rpi3, there is quite a bit more to emulation than surface similarities. For instance, one general rule that has seen few exceptions is that a machine intending to emulate another machine should be in the neighborhood of four times faster than the original. Even then, there are still circumstances that would prohibit proper emulation. At this point in time, the Rpi is just not fast enough and is unlikely to be fast enough for quite a few updates yet to come.

Of course, I can set the Zero to Player 2 mode with Start + B + R. That's sorted it.

I have fixed it just uninstalling and installing again sixad (PS3 controller) in RetroPie-Setup script and adding a systemd service:

sudo nano /etc/systemd/system/sixad-start.service

##########
[Unit]
Description=Sixad start service
After=network.target

[Service]
Type=oneshot
ExecStart=/usr/bin/sixad -s 2>&1 > /dev/null
ExecStop=killall sixad
RemainAfterExit=yes
User=root
Group=root

[Install]
WantedBy=multi-user.target
##########

Then:
sudo systemctl daemon-reload
sudo systemctl enable sixad-start.service
sudo reboot

It also works plugin the bluetooth device.

I'll have to try this as it really annoys me too :)

I had this, the interfaces were set to manual.

edit the /etc/network/interfaces file.

Later,
dabone

thank you kind sir

@dasfreak go to your config.txt and change "hdmi_group=2" to "hdmi_group=1"
Group 1 is CEA
Group 2 is DMT (no sound)
Check http://elinux.org/RPiconfig

@Rion said in [SOLVED] map: vt02 => fb0 [or how do I kill this message?]:

Sorry to resurrect and old thread but could you please @senkun post you're finding to the wiki? The more I can hide when I boot up the better.

Don't think it would be relevant in the retropie wiki as;

... I'm actually running attractmode instead of ES as the retropie frontend.

and what I did in addition to what the wiki has already covered very well was to pipe fsck messages away, not recommended. besides that, mostly to suppress the output from x/attractmode once it's running or when I exit and restart AM; which involved messing around with getty to hide the autologin/last login msgs, clearing MOTD, doing a .hushlogin, changing .bashrc, etc. I didn't really take notes and one shouldn't really be messing with those for retropie I believe.

as long as you have a splashscreen pic/video setup in retropie it boots very cleanly to ES doesn't it? you just need to follow the wiki to edit /boot/config.txt /boot/cmdline.txt and it will be clean all the way in except for the fsck msg.

Yes onboard. That you for the reference I will take a look.

You could move the downloaded_images folder to usb and create a symlink on the sd card...

@shift838

https://retropie.org.uk/forum/topic/140/how-to-use-overclock-and-mupen-core-options-to-significantly-increase-64-game-playability-quality-and-stability

Thank you!!!

Mine got recognized automatically by the default driver xpad(and xboxdrv), so I was just able to get it going using the emulationstation configure input option.

I'm not quite sure how you could get it working, easiest option I think is to make sure you've tried all possible ports so it's not a faulty port or something. Also, you could try it out on a pc to see if it's working or a faulty controller. I'm not sure this is the best advice, but it's probably something I'd check for myself if I had that problem.

As for the software and drivers, RetroPie should be fully equipped to handle most controllers plug and play, including the F310. So if you did anything really custom besides just flashing the stock image to sd card, it may be worth trying it out again with a stock install. I doubt this would be the reason, unless your install isn't recognizing any controllers at all.