Apparently it was a problem with the .bak file for my controller located at /opt/configs/all/retroarch-joypads/. Deleting it solved the whole situation. I noticed that the script module is configured to ignore it, but I thought it might not be for some reason and sure enough it paid off. A new .bak has even been created and is not throwing Mupen64plus off, so I assume it was a fluke of some kind.

@chartman said in MAME 2010 .cfg save files:

@dankcushions said in MAME 2010 .cfg save files:

@chartman said in MAME 2010 .cfg save files:

@dankcushions said in MAME 2010 .cfg save files:

I know it remains marked as "Experimental", but am I to assume that the MAME 2010 core just isn't used by many people? I mean surely this one issue is the primary roadblock to it's mainstream use.

it took me a bunch of work to get mame2003 to create and save to the right directories. mame2003 runs most of its romset full speed on pi2 and 3. personally, i don't see the need to use mame2010 on a pi - what important games does it run fullspeed on this hardware that mame2003 does not? anyway, at that point, we might as well just get current mame working (which is a whole other story!)

still, people are welcome to make similar changes to mame2010 if they want to get it saving :) you'll want to do something like https://github.com/libretro/mame2003-libretro/compare/4145a3bdce45467dcdc9f1bf01aa643e5d4a94c4...a6a2b942fd899965492b66a29328cc093c88b99f

Big reason for me to switch to MAME2010 is not the supported ROMS, but the supported features. Being able to cocktail mode (Mirror) Horizontal games on a cocktail cabinet is amazing. Not supported in 2003. Cocktail for vertical games works in both.

not sure i understand. do you mean when it flips the screen for the second player? because that is something that is set within the dipswitches/setup menu of the game itself, and is possible in mame2003: https://github.com/RetroPie/RetroPie-Setup/wiki/lr-mame2003#service-menu

The dipswitch/setup menu works great for vertical games with Cocktail mode built in to the original hardware. Most vertical games designed for cocktail cabinets have that dipswitch setting. The setting I am talking about is in the same menu, but under Video Options, not dipswitch settings, and it is a setting for "Cocktail Mode" which is part of the MAME emulator and not the original hardware. With this setting and a 90% rotate you can start a horizontal game like Metal Slug on a 16x9 Cocktail table and have the game run split screen with the game mirrored and facing both players on the cocktail table like this picture:

0_1475076868413_IMG_6858.JPG

you can achieve this same effect with a special shader in any libretro core (eg, mame2003). see http://libretro.com/forums/showthread.php?t=6991

not sure if it's ready to be released yet...

Ya, it's nice and keeps things cool... but again, if have a cable (game controller) with a metal end on it, one small touch at the wrong time and ZAP! there goes your board, possible MicroSD Card as well.

Not so much a worry on mine, but I know for sure that the 2 kids will have stuff getting into it, and one of them has a cat. Enough said on that one. :)

I'm not sure if it's possible to do what's been discussed so far.

What should work though, is when the emulator is starting there's a box that comes up and you can press 'a' to go to a config page and you can set a different default emulator for that game, as well as some other settings.

Obviously this could be a pain to do for A LOT of games, but if you have that many games you want to change the default emulator for, there's a way to change the default emulator for a whole system (I'm not really sure how to do this but I remember seeing it can be done).

Things like FileZilla, Midnight Commander, WinSCP, etc should work fine to do that (It shouldn't matter for doing this but you may want to have emulationstation closed), but honestly, for ease of access, i'd just enable the samba sharing feature and access the roms folder from the file explorer.

Depending on how much you've scraped and whether you'd want to do it again, you could try deleting the gamelist.xml also.

Never mind everyone. After installing it, I apparently needed to update it, now it is scraping everything. Thanks anyway though.

@meleu I got you, that's exactly what I ended up doing. Thanks again for the assistance with that. Sorry I've had a long day and my communication skills are at a minimum right now which is what my wife has recently told me. ;-) Thanks again.

You'll need to create a type route sound output and direct both hardware outputs to it:

http://www.6by9.net/output-to-multiple-audio-devices-with-alsa/

Got it. Gonna get on that now. I guess they will show up next to the RetroPie link once data is there.

@surfrock66 if you are about to explode with so much desire to use RGUI, the advice I give is: use it through emulationstation RetroPie menu only. And do not enable "Save Config on Exit" when playing games.

We got some improvements to decrease the madness of the RGUI fans, but it's still confusing. ;-)

@jrmymllr said in ti99sim on 4.0.2:

I installed a few optional emulators such as jzintv, and those had binaries. But I noticed the experimental emulators, such as ti99sim, only lists source. Does this indeed mean it must be compiled, and if so, are there any instructions on how to do this?

just select it as normal and it will compile.

I got it working. I had a couple lines added in the config file that I did when I was trying to get my wiimote working. I just commented them out and it started working. I haven't tried to see if the wiimote still works after making the change. When I was trying to get it to work I changed and added quite a bit of stuff so hopefully it isn't needed.

@jrmymllr yes, it remembers. at least, for all the lr-emulators, and emulationstation itself.

Hi all,

I was worrying about setting this controller up on my system
RPi3
RetroPie 4.0.3
The Xin-Mo shows up as "Bus 001 Device 007: ID 16c0:05e1 Van Ooijen Technische Informatica Free shared USB VID/PID pair for CDC devices

I added usbhid.quirks=0x16c0:0x05e1:0x040 to /boot/cmdline.txt after a space after the last entry on the same line and rebooted.

I have a NES controller as Joystick one.

I reset emulation station in RetroPie-Setup, Configuration / Tools to Clear/Reset Emulation Station input config and restarted EmulationStation and configured the new controller by pressing a Xin-Mo button on Player 1. I could then control the EmulatinStation/RetroPie menus via Xin-Mo P1. This shows as Joystick 2.

I then fired up a game in Mame4All (Streetfighter2) and hit Tab when the game started and Selected Input General. For UI Cancel I chose , My NES controller Hotkets Select+Start and also Xin-Mo Select +Start as my ROM exit keys.

I then added P1 and P2 settings in Input (This Game) for Xin-Mo P1 and P2. My joy 2 and joy3,as NES controller is joy1.

This is working for me. I hope this helps anyone trying to keep up with getting this working on new versions of everything.

Cheers

Stuart

@Laserdisc
Hi

On the Pimoroni forum there have been several people with this type of issue and the fix was to re-solder the existing audio jack socket.

Cheers

Paul

Hi Buzz, yes I have installed. Now is on the SD card in the directory Roms/Dreamcast a systemManager.cdi file, but not on the HDD.

I did the same thing too except I created a sub-folder within the roms directory and called it mame-samples and edited both the 1.4x and the 0.9x versions of the mame-advmame.rc file and referenced my folder there as I found some of my games were using the 0.94 version while others were using the 1.4 version of the rc file.

On the sample path line, I appended the updated folder path to the existing entry.

dir_sample /home/pi/RetroPie/roms/mame-advmame/samples:/home/pi/RetroPie/roms/arcade/sample:/home/pi/RetroPie/roms/mame-samples

Any new audio samples I'll download will go to this folder instead of within the samples folder of ADV-MAME.

The samples work when they're zipped, not extracted.

Yes, the second one you linked. you would connect your power in to the microusb port. The full USB port would go to the PI's micro port. Blue/White would go to GPIO. Power switch would be soldered to switch +/- connections... If you could fashion something to use the reset switch, you could connect that to the reset connections. You can also connect the front led to the LED/Gnd ports as well... (GND is shared between reset and led)