We have some notes in the docs about dealing with a 4k resolution, but the canonical source is always the Raspberry Pi docs at https://www.raspberrypi.com/documentation/computers/configuration.html#hdmi-configuration.

EDIT: I'll add some notes about the 2nd port and a link to the video mode table listing.

@winterelf 3rd party builds are not supported by this forum.

If this were a build direct from this forum, the above fix would have worked. The file extension list in the es_system.cfg is the only change you need to make to allow a file to be shown in the game list of each system. It will just show without meta data until it is scrapped. This is also how it shows any images or videos. Once ES reads that file extension in that list, it knows what to do.

So who knows why your build is not doing that. You'll have to ask the team that created it.

@tigtagle said in Rasp-Config not working:

I also used a wolfanoz image for arcade 1up and flashed that onto my card too.

3rd party images are not supported as they are often distributed with copywrited material and are basically impossible to troubleshoot.

In case it helps anyone, the way I achieved this was to put single disk games and m3u files for multi-disk games in the root of roms/x68000, and place the images for the multi-disk games in a separate sub-folder (roms/x68000/multi) then write the m3u files to point at them.

The system ignores the sub folder and just the stuff in the root is displayed.

Root of x68000:

6b7f8744-7d12-48fc-abe3-c0ce2921bc79-image.png

Contents of 'multi' folder:

b0e9f1ad-1d6b-4241-86b0-2e4d45bc0db3-image.png

@dankcushions I have many games that run full speed with 4x MSAA and a CRT shader when using lr-mupen64plus-next. The issue I have is the temporary freezes when loading new textures/shaders for the first time. Standalone mupen64plus-GlideN64 runs at native resolution for me, i.e. 320x240, which to my eyes is unbearable on a modern screen.

Still, thanks for pointing me in the right way of the .cfg file - I wasn't sure if this was the one that would be used by mupen64plus-GlideN64 :) I will try experimenting a bit and will report back.

@mitu

Hey sorry for the lack of information I sometimes forget there can be a verity of variables. I’m nowhere near my Pi at the moment so I’ll give the information I know now, and once I get to my Pi I’ll share the rest.

Pi Model or other hardware: Raspberry Pi 4 B 4gb overclocked CPU 2Ghz

Power Supply used: Not entirely sure at the moment, but my
Pi is in the RetroFlag NesPi4 with the External usbs and Ethernet ports disconnected because of Bluetooth/WiFi interference

RetroPie Version: I installed 4.7.1 to an SD card and regular update it in the Retropie script (I know I need to be exact, I’ll get this information as soon as possible)

USB Devices connected: 1 terabyte SSD Sata to USB3

Controller used: Official Atari VCS Classic Joystick

I’ve only tested the two default RetroArch cores for NES and Genesis (I will find out exactly which ones later)

In the RetroArch menu If I go into settings -> input -> ports1 (I think it’s called that), I see that the input device is set to classic controller and the inputs match the numbers of the buttons. EX: button 0 = ‘a’.

Interestingly enough if I disconnect that controller while the game is running and connect a WiiU pro controller, the buttons remain messed up. (I tested this a long time ago so for the sake of assurance I’ll test this again). If I quit RetroArch swap controllers then open a RetroArch core buttons revert back to normal.

I will test the joystick with that command in the terminal when I get a chance, but I did do jstest and the spinners seems to read like a joystick with a single axis.

@sleve_mcdichael hello, I appreciate your help, I uploaded the files you requested here:
https://drive.google.com/drive/folders/1w5Q1e88_zQtoAH_Et1ACRX61zJqStqWi?usp=sharing

Update: Okay, not sure what reverted, but I just did a full system update this morning (usual routine every couple weeks) and the SNES bezels are fitting again.

@dankcushions said in Questions about yabasanshiro standalone emulator:

@projectfirestart sega rally works for me

I have to rectifiy this a little, it works in fact, but i have a crash when race begin that i can't trace, it happens first time i load game, then crash to Emulation Station, if i run game again it seems to work.
I am unable to find a specific pattern, happens both championship and time attack mode. It's weird but it happened also on libretro version and issue seems gone once enabled HLE Bios, but standalone version dosn't have that option...

For anyone reading with the same problem, the monitor works now with the new active adapter that comes with its own power supply

Thank you mitu ....now I remember !!

@jcax21 it worked! I never thought of using the joystick and it surprisingly worked like you said. Thanks You and have a good day.

@mahoneyt944 said in mame2003 default.cfg:

@flagrant99 io games mame2003 will default to using the content directory to save cfgs when a save directory is not specified. You'll need to specify a save directory in retroarch.cfg

savefile_directory

This could be an emulator override

Thank you! Did it.

@mitu Can I just say how much I appreciate all that you do for us @mitu? That was the exact fix. I have no idea how you knew that, but always so dedicated to this community. I cannot thank you enough!!

Hi guys!
Sorry to resurrect the old thread, but have you found the solution for this?
I fixed the aggravating intermediate screen tearing problem by switching from fkms to kms, but now I'm having those errors... I know they're not that big of a deal, but they really poke my eyes.

...I had massive tearing even with Vsync ON and double buffering - and I don't like tripple buffering because of input delay.
Switching from fkms to kms fixed it and all the games are much more responsive right now!

@lolonois Thanks, will check it out.

Thanks, now it works. :D