Problem with lr-vice

TPR

@jamrom2 Here's the runcommand.log from the same game running on another Pi build:

Parameters:
Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-vice/vice_x64_libretro.so --config /opt/retropie/configs/c64/retroarch.cfg "/home/pi/RetroPie/roms/c64/#/10th Frame.T64" --appendconfig /dev/shm/retroarch.cfg

dankcushions

@tpr when providing logs please launch the game with the verbose option to provide a verbose log - these you’ve provided so far don’t really paint a complete picture of the scenario. see read-this-first link for full verbose log instructions

jamrom2

@tpr I honestly don't know. I switched over from vice to lr-vice64 without any issues like this. I had my own, but unrelated to this.

As suggested, run it verbose and upload the log... don't post it here, it will be a mess.

Maybe there is something not set correctly somewhere, but I can't imagine what. It was a load and go for me, as is for most.

TPR

@dankcushions Thanks. I'll do that tonight. Sorry for not doing it first. I've had loads of questions answered and not needed to do that. Was hoping it might have just been something that someone else had also had happened and could point me in the right direction, but maybe this one is actually a bigger issue than I would have thought...

TPR

@dankcushions
Here is the verbose runcommand.log -
https://www.dropbox.com/s/ljbd8994zutip5g/runcommand.log?dl=0

Any help or suggestions would be appreciated.

dankcushions

@tpr as i thought, the xboxdrv stuff is a red herring. the core is having a floating point error and crashing out, and i guess xboxdrv is complaining about that.

your issue is the crash. i see a number of [libretro ERROR] s which i suspect don’t occur during logs of working games. they seem to point to a BIOS or perhaps bad rom issue. i don’t know anything about c64/vice but it sounds like it’s expecting certain files in the romset:

The C128, VIC20, SCPU64 and C64 emulators also need the following DOS ROMs for the hardware-level emulation of the 1540, 1541, 1571, 1581, 2000, and 4000 disk drives, as well as the CMD hard drive:

‘dos1540', the 1540 drive ROM (16 KiB)
‘dos1541', the 1541 drive ROM (16 KiB)
‘dos1541II', the 1541-II drive ROM (16 KiB)
‘dos1571', the 1571 drive ROM (32 KiB)
‘dos1581', the 1581 drive ROM (32 KiB)
‘dos2000', the 2000 drive ROM (32 KiB)
‘dos4000', the 4000 drive ROM (32 KiB)
‘dosCMDHD', the CMD HD boot ROM (16 KiB)

see https://vice-emu.sourceforge.io/vice_4.html
the errors imply 2000 and 4000 files are missing, but idk

you’re also running an ancient version of RA but that may not be related.

TPR

@dankcushions Thanks for that. My Pi 4 is running the same version of lr-mame with the same romset and doesn't require any BIOS files or anything. I'm going to try to update RA now and see if that may be it, but I was using an older versions since the GPi Case is Pi Zero W based and this version seemed to run pretty smoothly.

TPR

@dankcushions Well, damn... that old version of RA seemed to be exactly what was causing it. So now I need to go through all the other emulator cores on the build to make sure that didn't break anything else.

One question. I noticed I now have to "press quit twice" to exit the emulator. Do I have to set that in the RA settings > Input > Hot Key Bind for each emulator or is there a way to set that globally? I think I have about 20ish cores installed and I'm really hoping I don't have to make that change one core at a time! :P

Although to get lr-vice running at a decent speed on the GPi Case (or I'm assuming with any Pi Zero based setup) I needed to do this in RA:

Options > Show Audio Options ON
then
Audio > SID Engine - Change to fastSID

Now the core seems to run pretty close to full speed! If you don't make that change, the core barely runs at all.

TPR

@dankcushions Something else I just noticed about updating to the latest version of RA. There is a few second delay after a game starts where I can perform any hotkey functions, like go into the RA menu or exit a game. Seems to be about a 7 second delay. Anything I can do to fix that?

sleve_mcdichael

@tpr said in Problem with lr-vice:

I noticed I now have to "press quit twice" to exit the emulator. Do I have to set that in the RA settings > Input > Hot Key Bind for each emulator or is there a way to set that globally? I think I have about 20ish cores installed and I'm really hoping I don't have to make that change one core at a time! :P

You can put quit_press_twice = "false" in your retroarch.cfg (or change it from "true" to "false" if it's already there.)

dankcushions

@tpr said in Problem with lr-vice:

@dankcushions Thanks for that. My Pi 4 is running the same version of lr-mame with the same romset and doesn't require any BIOS files or anything.

lr-mame? do you mean lr-vice?

One question. I noticed I now have to "press quit twice" to exit the emulator. Do I have to set that in the RA settings > Input > Hot Key Bind for each emulator or is there a way to set that globally? I think I have about 20ish cores installed and I'm really hoping I don't have to make that change one core at a time! :P

hmm, that should have set to true on your global /opt/retropie/configs/all/retroarch.cfg when you updated: https://github.com/RetroPie/RetroPie-Setup/blob/a9198687e573694f01fd0b434100b86b1babff9e/scriptmodules/emulators/retroarch.sh#L265-L266

if so, i suspect your /opt/retropie/configs/c64/retroarch.cfg is not default and is full of all the options, overriding /all/retroarch.cfg? - perhaps you saved it when in the retroarch menu? this would mean you're running your own config, outside of retropie's remit, so you'd have to make your own change there (unless you returned it to default by deleting it, then renaming the retroarch.cfg.rp-dist to retroarch.cfg

this might fix your 7 second thing also

TPR

@dankcushions said in Problem with lr-vice:

@tpr said in Problem with lr-vice:

@dankcushions Thanks for that. My Pi 4 is running the same version of lr-mame with the same romset and doesn't require any BIOS files or anything.

lr-mame? do you mean lr-vice?

Yes, sorry. I was just doing something in mame so it was on my mind!

One question. I noticed I now have to "press quit twice" to exit the emulator. Do I have to set that in the RA settings > Input > Hot Key Bind for each emulator or is there a way to set that globally? I think I have about 20ish cores installed and I'm really hoping I don't have to make that change one core at a time! :P

hmm, that should have set to true on your global /opt/retropie/configs/all/retroarch.cfg when you updated: https://github.com/RetroPie/RetroPie-Setup/blob/a9198687e573694f01fd0b434100b86b1babff9e/scriptmodules/emulators/retroarch.sh#L265-L266

if so, i suspect your /opt/retropie/configs/c64/retroarch.cfg is not default and is full of all the options, overriding /all/retroarch.cfg? - perhaps you saved it when in the retroarch menu? this would mean you're running your own config, outside of retropie's remit, so you'd have to make your own change there (unless you returned it to default by deleting it, then renaming the retroarch.cfg.rp-dist to retroarch.cfg

this might fix your 7 second thing also

I did mange to get the "press quit twice" thing fixed however I'm still getting the delay once any core opens. It seems to be a global thing, not just with lr-vice. Any ideas as to what could be causing it? It wasn't an issue before I updated RA.

TPR

@dankcushions Also, I never touched /all/retroarch.cfg I only went into each emulator core, chose "close content" then went into my settings > Input > Hotkey Binds, and turned off the "Press Quit Twice" option, and then saved current configuration, where I can see it saved it into the emulator core directory. But even before I did any of that, I was still getting the delay from the vanilla install of the new version of RA.

Here is the file from my /opt/retropie/configs/all/retroarch.cfg
https://www.dropbox.com/s/sl0hkfue8zjsp5i/retroarch.cfg?dl=0

See anything that could be causing the issue?

EDIT: I don't see anything in there about disabling press quit twice and this is the file that was downloaded "from binary" yesterday.

TPR

@dankcushions So I made another change. I went into every one of my emulation core config folders and changed the retroarch.cfg to the following. Now all the cores seem to work without the delay and I can also press quit once to get out of the core. I'm not sure if this was the best way to do it, or if you think there was a better way, but at least, for now, this "works."

Settings made here will only override settings in the global retroarch.cfg if placed above the #include line

input_remapping_directory = "/opt/retropie/configs/nes/"

quit_press_twice = "false"

#include "/opt/retropie/configs/all/retroarch.cfg"

dankcushions

@tpr please quote code blocks via the markup: https://retropie.org.uk/forum/topic/3/read-this-first

Here is the file from my /opt/retropie/configs/all/retroarch.cfg

https://www.dropbox.com/s/sl0hkfue8zjsp5i/retroarch.cfg?dl=0

did you update the retropie-setup script before updating retroarch? i'm not quite sure how you could get the retroarch update with the quit twice feature, without also getting the cfg change, mind.

So I made another change. I went into every one of my emulation core config folders and changed the retroarch.cfg to the following. Now all the cores seem to work without the delay and I can also press quit once to get out of the core. I'm not sure if this was the best way to do it, or if you think there was a better way, but at least, for now, this "works."

the better way is to add the quite_press_twice setting to /all/retroarch.cfg, as you want it to apply to every core. i think this issue you have is that you went into individual cores and saved retroarch settings. this makes you /opt/retropie/configs/nes (or whatever)/retroarch.cfg get replaced with an entire set of retroarch settings, removes the #include "/opt/retropie/configs/all/retroarch.cfg", so it now operates independently from the global /all/retroarch.cfg settings and future config updates, and is on you to maintain.

this is why i would suggest doing any config changes via https://retropie.org.uk/docs/Configuration-Editor, which maintains the hierarchy.

TPR

@dankcushions I'm going to do a full update and reinstall of as much as I can right now.