To anyone with the same issue in the future: the solution is to change emulator altogether.

The lr-xxxxxxxx ones are too intermingled with retroarch and all that boogus to let you change the language easily (or at all.)

Go to the retropie setup, download a different package and go from there.

Sorry to bump this, but does anyone know how to pass additional commandline options to ffmpeg via --recordconfig?

@dudleydes said in Arcade Vs Adv-Mame...:

rc file in a text editor, go to line 42 (or search for dir_rom) and make the changes outlined in my previous post. Repeat for the other

Just did it and is working now!!! Thank you very much!
Now if i could get also the mame2014 working it would be great.

@redmomi Np Happy CRT Gaming 😉

Yes, and it solved the issue! Thanks so much - I hadn't been to that menu yet.

Woo hoo! :)

Thanks guys, autostart seems to load much faster now.
However, there is still the problem that "warp mode" is still seems to be turned on after the game starts.
I enabled the statusbar and it says that VICE is running at 187%
However, the asterisk in the emulator-menu for warp mode is not showing.

Maybe using a fastload .crt is a solution.
However i still don't get it that the builds for Pi and Win are so different in their behaviour.

@kisu2012 said in Controller Dreamcast works in BIOS but not in game:

Hi, TitQuentin
If you have problems for mapping your controller, you have a script called "reicast-joyconfig" for mapping any standard controller.
I use a bluetooth cheap controller and I run this script and works great with reicast.
You have further information on Wiki Retropie reicast at the end of the page.

Excuse my english ,
Good luck

Thank you, it works thanks to your help!

Disable the joystick or update to Kodi 17 betas.
This issue was already talked here many times... Next time please do some searches in the forum before posting issues.

Perhaps it is a bad image. I did use the same image on each of the SD cards ... I'll try downloading again tomorrow, and see how that goes. I did unplug the extra hardware and still had the same errors, so my guess is it's not hardware related.

You need to reverse that. Most fans are going to need 5v to run. You can also use the 3.3v pin (pin escapes me right now), to run fans quieter, but those are the pins to run fans on for the pi. Also recommended are heatsinks for all of the sensitive chips (including the one on the bottom of the board). Use pins 2 and 9 for the power switch but not recommended for corrupting the sd card. I got one of the push button switches that connect to the micro usb port in between the pi and the power supply. It will also clean up your power feed.

@donlar714 based on that then, if you are powering your hub and Pi separately, you could have a dodgy wi-fi dongle.

@Xyb0t said in Performance boos due to lower resolution??:

@dankcushions Well, i understand that scaling might not mean a lot, but rendering i guess will take it's toll??

they're the same thing. you can't 'render' a NES game in a higher resolution than 240x224 (or whatever it is natively). a higher render resolution just means it's scaled to that by the GPU. same with psx, etc.

(with shaders it becomes different)

How can i test for myself? Is there some form of on-screen FPS counter that i can switch on?

select + x to get to the RGUI. settings > video > show fps counter.

After a few days of testing I have managed to create my favorites folder, where I can run the roms that I like the most. Many thanks for your tutorial Dudleydes is fantastic.
Regards and thank you all

@tom1155

Not a problem. As mentioned above, if you still have any questions after reading the documentation, get back with us.