[quote=122276]Sorry, don’t know the answer. What screen is that? Thanks

[/quote]

Very nice screen good bang for the buck, it’s a waveshare 3.2″ v4, 320×240 so it’s pretty snappy when configured right, minimal tearing.

[quote=122328]with help from Buzz, we’ve actually fixed this in the code now

https://github.com/libretro/mame2003-libretro/pull/25#event-612809045

so if you don’t mind waiting for about 30 minutes for mame to compile, you could avoid the above instructions by doing a build from source:

1) retropie-setup
2) install individual emulators
3) lr-mame2003
4) from source

[/quote]

whoa! Thank you!

with help from Buzz, we’ve actually fixed this in the code now :)

https://github.com/libretro/mame2003-libretro/pull/25#event-612809045

so if you don’t mind waiting for about 30 minutes for mame to compile, you could avoid the above instructions by doing a build from source:

1) retropie-setup
2) install individual emulators
3) lr-mame2003
4) from source

[quote=122280]Hello again
I have now used this dualboot and tweaked it into my prefered settning regarding background pictures etc.
I just have one last (?) question;
How do I edit the config.txt?
I wanna overclock it a little and mostly, add my codes for the
decode_MPG2=0x00000000
decode_WVC1=0x00000000
I keep gettin errors both from SSH and WinSCP that I am not allowed to edit the file.
[/quote]

I think OpenELEC should allow you to edit the files with the default root/openelec combination of username/password.

As for other types of OSes like Raspbian and RetroPie, you’d need root permissions to edit the file.
In order to login through WinSCP as ‘root’, you’d first need to set a root password. You can google how to do that.
Or you could login as pi/raspberry with SSH or your preferred method and then edit the file with nano:
$ sudo nano /boot/config.txt

This is a great tutorial. I did it yesterday and everything is working, except one thing : I can’t configure the emulator exit button and the hotkey for mame4all (start + select).
I tried several configurations, including configuring the “retroarch.cfg” and “Xin-Mo Xin-Mo Dual Arcade.cfg” manually with:

input_start_btn = "8"
input_exit_emulator_btn = "8"

and

input_select_btn = "9"
input_enable_hotkey_btn = "9"

The emulator exit button (start+select) works well if a use a 8BitdoNES30Pro8BitdoNES30Pro controller. The 8BitdoNES30Pro8BitdoNES30Pro.cfg is exactly the same above, only the button numbers are diferente, of course.

– Yes, the buttons are working
– Yes, the buttons are mapped

Is there any other place that may be misconfigured ?
On the mame4all <TAB> menu, there is not mapping to a exit button. Should be one available there ?

Any help is appreciate.

You probably need to make the configuration for the mama4all. The easy way is to connect a USB keyboard, enter in a game and hit the <TAB> key.
You will see a menu, select the 1st option and configure your controller. To setup a button, hit <ENTER> on the keyboard then the controller button. To remove/del a setup, hit <ENTER> on the option you want to remove then <TAB><TAB>.
If this does not work, may be you need to config your Xin-Mo : https://www.petrockblock.com/forums/topic/how-to-get-xin-mo-dual-arcade-working-with-retropie-easy-guide/

I tested the ResidualVM installation in RetroPie a little further today with disappointing results. I copied over several save game files to test at different points throughout the game. ResidualVM will compile just fine and Grim Fandango will load. The intro is very choppy, and the beginning of the game is playable, but there are many more graphically demanding portions of the game later on, and it is definitely unplayable at those points and even crashed my pi a couple times. I tried forcing a lower resolution and tested out different memory splits to no avail.

At this point, I would consider ResidualVM games unplayable on the Raspberry Pi until better optimizations are made upstream.

Hi everyone,

Just got started with the Pi (using a RPi 1 Model B+ at the moment) and after successfully installing RetroPie 3.6 and Kodi (as a port inside of RetroPie), I would like to simplify the setup and move to a dual boot (also hoping it might speed up the menu system a bit, since it can be really slow in Kodi). Any way to turn the existing setup into a dual boot without formatting and partitioning the SD card? And if not, what would be the best dual boot option given my system?

Thanks in advance.

Thanks for the info, Bengus. For what it’s worth the workaround mentioned on that page to disable the built in bluetooth didn’t work for me, the pi could not detect the Dualshock over the usb bluetooth.

Like this? I have used this with much success.

Tutorial: RetroPie with DualShock 4 and Bluetooth

Anyone have experience with the JUYAO Dual Joystick USB interface board?

[quote=121277]

bjkidder wrote:

Got mine to work with Raspberry pi 3!

Kernel wasn’t needed, just added the usbquirks line. Make sure your device ID is correct! Mine wasn’t the same as what is listed under the instructions with the usbquirks step. 0314:0326 instead. Sub-in whats listed when you run lsusb. rebooted and emulation station picked up two players. Configured in mame4all with use of xbox 360 controllers for players 3 and 4, works great. Works in retroarch as well.

You are awesome! Thank you so much for sharing that! I’ll try it as soon as I get home.

[/quote]

Out of curiosity what was the USB labeled as? I have five listings that show up on lsusb and none of them look like they would belong to the xin mo haha.

I tried lsusb -t and I have sorting out to do.

I just ssh’d in from my computer and removed my usbs to figure it out.

bjkidder are you using the xin mo dual arcade joysticks/buttons?

I’m using the raspberry pi b model (first one) just to test my setup then was going to order a raspberry pi3 but don’t know if it’s safe to do so now or not

Hey Guys,

Exact same issue with me. I thought for a while it was the power supply, but after going through multiple I tried using a different bluetooth adapter. That fixed my problem.

I’d love to be able to get more information about what exactly is crashing the pi, but the logs are uninformative.

I’m guessing that there is an incompatibility problem between the rpi 3’s bluetooth and the dual shock three controllers.

It’s probably an upstream problem, but if i figure out a solution that works I’ll post here.

Hi everyone!

Do someone have a working kernel fix for Raspberry Pi 3, RetroPie 3.6? (Working with Xin-mo)

We are some guys over in this thread that are wondering: (We got it to work with Raspberry pi 1 and 2 but not 3) https://www.petrockblock.com/forums/topic/how-to-get-xin-mo-dual-arcade-working-with-retropie-easy-guide/

First I just want to say thank you feederchain for this kernel, after a week of banging my head against the wall I finally got player 2 working.

The only problem I’m having now is player 2 start/select buttons are not working now, they work in the emulation station gui but not in the emulators themselves.
Did anyone else have similar issues?

I’m using the xin mo dual usb and taken the following steps so far:
1 Installed the kernel
2 Applied usb quirk to cmd.text
3 Configured joysticks and buttons in /opt/retropie/configs/all/retroarch.cfg

jstest is showing all buttons working as they should and it’s only when using emulators player 2 start select will not work.
I have tried configuring snes emulator manually putting all my control mappings above the #include line and still nothing.

Any help on this would be much appreciated guys.
Thanks

I bought a similar usb dual arcade device on ebay. I thkught it was the Xin-Mo type, but when I hooked it up to the RasPi, it said the type was ‘JUYAO_2_PLAYER_ARCADE’ type. Mine has 22 pins on both sides of the board for each of the 2 players. My issue is that I want to play Mortal Kombat or Street fighter, but I can only get 2 kick and 2 punch buttons to work along with the joysticks. Those games should have 3 punck and kick buttons. Does anyone know how I can change the config to make all 3 kick and punch buttons to work?
Appreciate any advice.

Sent from my GT-P3113 using Tapatalk

[quote=120407]
Then I have a script on my personal OpenELEC setup that I can click on named ‘Update KODI’ and it will download that file, extract it, check that the relevant files are present from the extract (and halt if they are not!), copy the existing custom keymaps I have setup for my KODI remote then proceed to delete my current setup and replace it with the downloaded setup and finally copy over my original keymap files and delete all the downloaded data that is no longer needed then reboot into my new setup. All this is done automatically for me at the click of a button and it means I can tinker with a separate OpenELEC build until I am happy with it then simply upload it to the net (using the same static link, replacing the old file) and update on my master dual boot setup and other Pi’s in the house. It also means that I don’t need to visit my mothers house every time she messes up her KODI setup (bless her!), so if it goes wrong she just has to click ‘update KODI’ at her end and it’ll fix itself automatically. Its a lot easier for me!

Well, sorry that turned into a lengthy post! I will be writing a blog on how to set up that type of script so will post a link if anyone here is interested. It may sound like a faff but it makes things a lot more easy to update, especially if you have a few builds set up yourself or for family & friends.

All the best
Steve

[/quote]

Hi Smithers,
I would very much love to have that script. It is very much a hustle going to everyone houses to fix a problem so will very much be appreciated.
Everything you are doing is great.
Thanks for everything.