if what retrowertz suggested doesn't solve your problem try to set mouse index to '0' for every user binds

@grant2258 Hello
I chekc on the system and i'm unable to find a mame2003.log
Do you know where it should be.
Also I check the runcommand.log, and tehre is only two lines who said that I launch centipede.
In the mame menu, I cna assign a button to a mouse click. But it cannot register my mouse moving.

Francis

@samuelsson

What are the contents of your /opt/retropie/configs/nes/retroarch.cfg file?

@tayocof Please don't post links to ROMs or other copyrighted materials - https://retropie.org.uk/forum/topic/2/forum-rules.

@radiusxe

The best you can hope for is to load the save state from the previous core version and work your way to an area that allows for a normal memory save. Afterwards, update the core load the save and make a new save state. I realize this wouldn't be possible for all games and it's a major hassle, but it's really the only option. It's best to only utilize save states for very casual use and at no time when it's crucial to keep them for long periods of time. Save state formats can change at any time depending on development. You might see an emulator/core keep its format throughout its lifespan, or you might see it change several times a year.

@MrLightgun thanks I just actually updated to the latest version of RetroPie release. I have been holding off because my setup was working great for the most part.

I’m almost done moving my cfgs over and making sure everything is working properly. I believe I will give this process a try and see how it goes.

Yes, I can confirm that a rebuild of lr-fceumm worked. Thank you for taking a look at it.

@edmaul69 said in NES emulators in 16:9 black bars discussion:

@backstander it doesnt work in fceumm because it became a core option. And core options override retroarch.cfg files.

in theory core options and retroarch.cfg options shouldn't really overlap. core options are those that are specific to the core you're using (enable_multitap or whatever), whereas retroarch options are potentially applicable to all libreto cores (enable_shader), although in retropie we have separate retroarch.cfg files for each core, as well as an /all/retroarch.cfg for generic options.

so in my opinion, overscan options should either be a retroarch, or a core option, not both, but i don't really know the intention/history of that option.

I just found that a lot of others are having the issues with rom sets - https://retropie.org.uk/forum/topic/5207/some-games-load-some-don-t-nes-fceumm-core/34 - going to try lr-nestopia and potentially zip with zero compression to see if that helps.

Not sure if this is the same issue with the controller not working though.

@edmaul69 at the top right of the box where you edit posts it has a link compose? which opens a popup which links to http://commonmark.org/help/ which has all the info :)

Just wanted to add that this has happened to me as well. I am using a Model A Gen1 Pi. Went through the setup without a problem and then after a reboot I get the same msg, controller not configured.