@dankcushions . ok, I'll open a new thread. Thanks!

I can always fork using Git. Thanks for the heads up!

Ok, I will allow ssh access. Thank you again for your help.

Looking at Picodrive's issue list, I can see that Kolibri was reported as crashing in level 2 by some users, and slowdown by others. Therefore I think this is a problem with the individual emulator.

@dipkid glad to hear it! Yeah, the ribbon cables can be super twitchy.

The raspberry pi 2 does NOT have any wireless built in. Now that being said you can use a wireless usb dongle. But that would be a problem for a different forum for sure.

Remember you can always plug in an Ethernet cable to the rasp pi2 and then to your router then boot the pi headless or connect a monitor. (I have just connected my pi directly to my PC also.) You'll have to know how to get the IP it is assigned and then from there you can log in via ssh.

You can always transfer any data to and from the pi "local" via a usb drive using midnight commander (the "filemanger" selection) in the retropie menu. Besides it is MUCH faster that way anyway.

@mitu said in Buttons on Controller Exiting ROM.:

@blkkrow This indicates a problem with the emulator or ROM.
What game are you trying to play and what ROM ?
Have you tried looking in /var/shm/runcommand.log to see if any errors appear ?

I did not know about the run command log, I will look into that.

I am attempting to run a PSX Game, "Wild Arms". To make sure it wasn't the Rom/Emulator I attempted a SNES game.

@bakecrusader The difference of the pi 1/0 image vs the pi 2/3 image is the the pi 1/0 image has emulators that are lower end and older. Some of the libretro emulators dont run well on the p 1/0 so they include the standalone programs which run better but are harder to configure. SNES includes older versions that are buggier but faster. ECT.... It basically gets rid of the stuff that won't run well on a 1/0 and includes stuff that runs better.

Made some progress. Formatted the drive to NTFS and that sped things up considerably. I assume the wiki uses FAT32 specifically for flash drives and windows compatibility, though I'm not sure why they don't suggest exFAT.

Right now I'm working on testing if exFAT is faster or slower than NTFS.

I wish I'd known the usbromservice was more accepting of different file systems from the get go.

Thanks @caver01. I was working with all 3 AdvanceMAME options available in RetroPie.

Maybe I should install all copies of AdvanceMAME and delete the /opt/retropie/configs/mame-advmame folder, and install AdvanceMAME 1.4 again and see if it continues to get over written after I've set some controls again.

There might be an old file system redirect hanging around.

@casadero said in How do I add scanlines to MAME in retropie 4.2?:

@caver01 : correction to my recent post: I put the ROMs to the MAME-MAME4ALL folder and, later, to the ARCADE folder. there is no folder like "lr-mame2003" folder on my USB stick, but a "mame-libreto". I still do not know the difference between all these MAME Emulators, but I will start some research about that issue the coming weekend.

Please read this.

Emulators come in two basic flavors in RetroPie--standalone or libretro core. The standalone are just that--they run independently of other frameworks. They are configured independently. They might have their own way of generating display effects (advancemame for instance has some RGB effects that can be turned on). The libretro cores are all emulators that run inside of the RetroArch framework. These can share common settings for controls, video, etc. The CRT-PI shader is for RetroArch, so it won't apply to the standalone emulators, whether they are MAME or something else.

Given the two kinds of emulators, there are several different versions of MAME. Some are standalone, some libretro cores. Each requires their own ROM versions. Generally speaking, you should only use ROMs that come from a set with a version matching that version of MAME. If the location of your ROMs allows you to choose more than one emulator, you do that using the RUNCOMMAND function (which you should also click and read).

@simonster Only with Keyboard' :( damn

@akafox Thank you for the info. I will add it manually.

@buzz

Oy......sorry I should have known that (it just slipped out). I got overexcited. Sorry that I’m off to a bad start :(

Another issue, after upgrading from 4.2 to 4.3 and saving a core wide shader preset when you quit the ROM and open it again or another rom from the same core the preset is not applied (at least is saved) and you need to apply it, also in the update I lost my RetroAchievements settings

@lamaman1971 I just realized, there is an easier solution for per-ROM settings without bothering to modify an artwork .zip file. You can simply specify the ROM as a prefix to a setting inside your .rc file. For example, say you have:
display_artwork_bezel yes

but you want to forego the bezel for Tempest. Just add:
tempest/display_artwork_bezel no

which will override the bezel setting for that one ROM.

AdvanceMAME works this way for everything, so you can get very granular with controls, video--anything really. It also works to use prefixes like vertical/display_artwork_bezel no. I am not sure about all of the supported categories, but I know they exist for game resolution, orientation, vector, and possibly others. Obviously, if you wanted to have your default setting be no and then only use a bezel for a specific title with a prefix of that ROM and a setting to yes that will work too.

@tigerjonny said in anyone have an idea on this error:

@barrymossel bloody got to work away for 10 days...bloody typical would likd to try and get my head round some of it....got the retrpie screen on...then got the call...i gather its adding the rom s after that)

Yup, setting up the controller(s) and then adding roms (through one of the various ways). https://github.com/retropie/retropie-setup/wiki/Transferring-Roms