@aidy80-s Have fun. 😁

That being said, you should try one of the other MAME emulators - Mame2003 has mouse support and RetroArch seems to detect your mouse. As a plus, it supports absolute pointing devices.

Oh, forgot it is a stand-alone, that is true.
I will try to register the analog pad to the d-pad using the script then. Thanks!

You're welcome. Do you know that you can change the title subsequently by editing the first post? Just click on the little three dots at its right side and choose "edit". 🤓

@phelix01 Please provide info requested here as already requested earlier https://retropie.org.uk/forum/topic/3/read-this-first. Is there a reason you are ignoring this request? We cant help you unless you give us all the info. What type of monitor/display are you using?

@quicksilver any time I make the change to "trivial" or anything else for that matter, it gets changed right back when I restart emulation station. Anyone know why?

I have a Pi 1 Model B and NES & SNES emulation works fine. Only a tiny glitch on SNES with Super Mario Kart relating to when the bottom camera faces behind but that's because I have to use the least powerful SNES emulator. I'd say you're good to stick with the Pi 3 tbh

There’s some info here: https://github.com/RetroPie/RetroPie-Setup/issues/2961

I think RetroPie has been set up to default to these emulators if you have a RPi4.

yes, with the official image it works after your help. Now i have a similar problem (with an unofficial image) and i was hoping you could help me. Sorry for the inconvenience, thanks anyway.

@duiz Here is my idea for fixing your resolution problem.

Firstly, try this.

Change this:

#disable_overscan=1

To this:
disable_overscan=1

Reset and see if that fixes it.

If that doesn't work change this :
#framebuffer_width=1280
#framebuffer_height=720

To this :
framebuffer_width=1920
framebuffer_height=1080

Make sure to remove the # before those lines.

If it doesn't work be sure to put it back the way it was.

Hopefully one of those ideas helps.

@quicksilver Absolutely devastating. 2.4 GHz didn’t made the TV to couch distance...

So I've managed to find the issue. it seems the ps3controller driver was causing the issues.

I only used it as I couldn't get sixaxis to find my controller. Looks like I need to try and get this working.

Just tested it and It does work in regular 2003 also.

@Brunnis said in Retro Pi 4.6 - Pi4 /4kTV slow loading:

I seem to remember you can limit the pixel clock instead, but I haven't tried it.

Yes, it's possible, though this will disable the 4k video modes completely.

Also, given the performance issues with 4K, wouldn't it be better to have RetroPie be limited to 1080p max out of the box, with an easy way to enable 4K if the user wishes?

This is exactly what the hdmi_mode/hdmi_group settings do - set 1080p video mode by default, with the ability to choose 4k via runcommand (though performance will not be great). Kodi/Pixel desktop would still be able to use those modes for 4k HEVC movies/normal desktop.

Unfortunately there isn't a way to configure the video so that 'if 4k is available, use 1080p by default', so instead of forcing 1080p by default for all configurations, it's something that the user must configure after installation.

@duiz I'd recommend FBNeo for CPS2/3

@Darksavior That's what I was referring to. If you have saved out your retroarch config on older version the offset will be wrong (the aspect ratio is a number which is an offset into a list - they added a new aspect ratio, but not at the end, so it broke old configs).