@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

Looking at the dependency chain startup, mounting of the media is taking the most, delaying the console-setup start.
You can try to disable the auto-mounting of the external disc and manually add the mount command in /opt/retropie/configs/all/autostart.sh, before ES starts. This way the splashscreen service will start sooner.

@mitu that's great! I honestly thought I was losing my mind! I shall now try and sort it without updating to the latest OS firmware.

@windg thanks man, i will check it later...I assume that the issue has to do something with the raspberry pi GPU, cos having the latest source, latest PPSSPP version, overclocked...could it be a GPU malfunction?

@mitu they are!!!
Thank you so much, perfect advise - as usual!

@roslof

You can try, It looks ok now.