@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.

@hawkes_84 It comes with more experience in config files to recognise or guess the different comment characters as well as section titles in square brackets. 🤓

I just stumbled upon this post...is this about getting 5200(and 800) carts to auto-launch? I am getting ready to build out an 800 and 5200 section on my build. I started with the 5200 and I spent the better part of this afternoon trying to work through the RetroPie documentation of loading carts, extracting, saving, etc. and I only got three to autoload so far...

Though in fairness, it was a busy day for me building JavaScript rules for online ordering templates for some of our customers, lol....among other things...

The mame cores I have installed are:
a) lr-mame2000
b) lr-mame2003
c) lr-mame2010
d) advmame
e) mame4all

Most of the arcade game mappings in the emulators.cfg file point to either lr-mame2003 or lr-mame2010.

The contents of the retroarch.cfg file in /opt/retropie/configs/mame-libretro/ is as follows:

input_overlay = "/opt/retropie/configs/all/retroarch/overlay/MAME-Horizontal.cfg" input_overlay_opacity = "1.000000" input_remapping_directory = "/opt/retropie/configs/mame-libretro/" # include "/opt/retropie/configs/all/retroarch.cfg"

So I don't see anything here that should override the global controller settings.

The runcommand.cfg file located on /opt/retropie/configs/all/ does not contain any code for the "launch menu joystick control" function right now - it does have:

disable_joystick = "0" disable_menu = "0"

...plus three other lines of code for use_art, governor, and image_delay.

I have tested the controller on the following console menus (accessed via the retropie configuration menu, from the screen where you would otherwise select a console & game):
a) Configuration Editor
b) ES Themes
c) Raspi-Config
d) Retropie Setup
...essentially every one I have tried that takes me to one of those blue menu screens the controller has not worked on.

The controller also does not work on the "File Manager" page (which appears to be a different type of interface than the other console menu pages - but I assume is still in LINUX space).

The controller does work on the Retroarch GUI when I launch it from this Retropie menu (just as it works when I am able to access RGUI from other emulators where the hotkey functionality is intact).

Thanks

Looking at the dpkg output, looks like you have the latest versions for the Bluetooth related packages - so no issue here.