@BuZz

I tried to remove it but it causes retroarch to crash. Here's the log: https://pastebin.com/dFx4K74J

Let me know if you need me to do more testing !

Thanks for your time.

Hello and welcom to this forum.

Did you configure the controller via Emulation Station correctly? Maybe do it again to be sure. There's a script to assign controllers to players. It works very well for me. Maybe it's worth a try for you.

If all of that doesn't help, please give us the information that's asked for in https://retropie.org.uk/forum/topic/3/read-this-first.

@mitu
tank you...
now , I can play Vigilante 8 with reicast oss.

@zerojay Hi just for clarity it is Lr-GPSP that crashes, Lr-mgba seems to pass this point fine.

@gmesmer Sorry, totally forgot about this. I'm away from my Pi tonight but I'll do that tomorrow.

Edit: I've done that now, doesn't even load up. Just black screen then back to Emulation Station.

@aerolito welcome to the forum. You've given almost no information about your problem, please add some more information as outlined here: https://retropie.org.uk/forum/topic/3/read-this-first

Also, when do you get this message? What are you trying to do?

This issue is now fixed as of 8-24-2020. Update from source if you experience this issue.

@stoo said in Gauntlet and Gauntlet 2 on lr-fbneo possible bug:

Are there titles that don't work with it?

Yeah there are, i don't have a full list but i can mention some :

sega system 24 (you found this one) and probably any other arcade systems using several m68k sega system 18 and megadrive (m68k worked differently on those systems, so you need another version of cyclone which apparently wouldn't work with "normal" 68k games) some neogeo games in mvs/unibios, they seem to work with aes though

@gizmo90 said in Retroarch Integer Scale setting not saving:

Any idea why the cfg file is being ignored?

If you're running a custom image, then we don't know how it was modified or configured from a stock RetroPie image.

It turns out that md_lbl and md_ need to have seperate size values for the "X" for some reason... it seems to be fixed now:

Should be fixed now, just update your RetroPie-Setu script and re-install (from source).

@Lolonois The PR has some users adding their metrics for the PS feature. Since then there have been more Pis released and every Pi that's more powerful than the previous one will use less cpu % while ideling.

The main concept of is is that is allows switching from a vsynced rendering to an event driven rendering. It makes no sense to keep rendering the same screen if no changes are present. Thus saving cpu cycles and increasing the battery life. on PiZero there are significant savings (40-60% based on theme). I implemented this feature cos my handheld build was overheating while doing nothing but ES. Animations are not a priority on a battery life focused build and Instant PS mode almost doubled my standby time. ie time spend browsing games on ES.

Please refer to the PR and https://retropie.org.uk/forum/topic/11304/testers-needed-power-saver-features-pr-172 where we have had extensive discussions and testing for the same

Thanks for providing the log file. I don't notice anything different between the 2 runs, so it's not something related to a configuration.
Try removing pulseaudio completely then reboot the system, this might get rid of any PA interference.

@BuZz : I saw this menu, but it provides me only with the choices "bookmark" and "share".

In fact the first post is not editable, but other ones are editable (I just edited this one)

@Styleshift Please open a new topic and add the info from https://retropie.org.uk/forum/topic/3/read-this-first. You shouldn't get the error in the topic unless you've manually downgraded the libsdl2(-dev) package.

@pamput Yes it does indeed appear to be fixed now

Yes, other games are fine. I am quite sure it's a bug and proposing a fix here:
https://github.com/RetroPie/EmulationStation/pull/592

@BuZz
Pi Model: 3B
Power Supply used: Official
Built From: on top of existing OS

You’re right, it’s a custom image.
I downgraded the firmware to 1.2019401-1 via rasbiantools in retropie_packages. Now everything works fine. I suppose this is some bug in the vc in newer firmware.