new scriptmodules (lr-vice-xvic, gsplus, proper lr-mess integration!)

valerino

When I launch a VIC-20 game it does state the lr-xvic emulator is the default emulator. I noticed that the es_systems.cfg file has updated to reflect the 2 new systems. Is there anything else I need to do?

what happens ? due to what is mentioned in the post referenced here some carts may not work (emulator runs but game not start).
i may fix it later as i said in https://retropie.org.uk/forum/post/217729.
for now, my goal is to have the most possible emulators starting and running games with the default options.
can you confirm that the emulator starts but do not load game ? if so it's probably to the problem mentioned. try other games, i.e. tapes, other carts. they will work for sure.

CCFox

@valerino

Thank you for your reply.

I've tried around 30 games at random and it gets to the blue screen with the emulator box then goes back to emulation station. Doesn't even get to the ready screen.

Rgds

CCF

valerino

@CCFox said in new scriptmodules (lr-vice-xvic, gsplus, proper lr-mess integration!):

I've tried around 30 games at random and it gets to the blue screen with the emulator box

can you be more clear about that ?
anyway, it seems you have something weird.

can you verify all of this and tell me if there's any differences ? thanks!

~/RetroPie-Setup(master) » ls -l /opt/retropie/libretrocores/lr-vice-xvic                                                                                               total 3052
-rw-r--r--  1 root root   17989 Apr 20 10:17 COPYING
drwxr-xr-x 14 root root    4096 Apr 20 10:17 data
-rw-r--r--  1 root root      60 Apr 20 10:17 retropie.pkg
-rwxr-xr-x  1 root root 3095296 Apr 20 10:17 vice_xvic_libretro.so

~/RetroPie-Setup(master) » cat /opt/retropie/configs/vic20/emulators.cfg                                                                                                
lr-vice-xvic = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-vice-xvic/vice_xvic_libretro.so --config /opt/retropie/configs/vic20/retroarch.cfg %ROM%"
default = "lr-vice-xvic"

and the following in /etc/emulationstation/es_systems.cfg:

CCFox

Hello again Valerino

Working!!!

the es_systems file matches so that is OK.

The files were all lr-vice-xvic folder.

However the emulators.cfg didn't match what you had posted. So I cut and pasted what you had put and wahey it works!!!

The information in the emulators.cfg file was a mixture of my earlier mistake and the commands that was generated by your quite excellent script.

I will now backup everything you have said.

Once again thank you very much for your help.

Kind Regards

CCF

valerino

thanks to @roslof, i merged his additions into my repo!

welcome lr-mess-oric, lr-mess-ti99, lr-mess-vectrex ! :)

CCFox

Then a very big thank you to rosof as well! To you both...

A lot of the games work fine with a joypad but still need a keyboard to play Blitz though.....I'll cope. Although the C64 and Plus 4/C16 versions work with a joypad, I don't get the same sense of nostalgia as I do with the VIC-20 version. Also the Plus 4/C16 version does seem to run a little slow I think.

Now just need to create a Plus4/C16 screen for my combined Epic Noir/Chicuelo theme. I had already created one for the VIC-20. Just need to find a good bit of art for a C16/Plus4 game.

Kind Regards

CCF

valerino

i suggest you all to update from my repo and reinstall all lr-mess scripts (or, if you prefer, do it messing with each generated emulators.cfg directly).

i made changes to run_mess.sh to launch lr-mess with -cfg_directory parameter set to the 'fake core' directory. this way the lr-mess system specific (i.e. joystick) configuration persists across reboot.
i didn't notice first, it 'seemed' to work since it was saved by default in /tmp. of course, after reboot it was cleaned up.

as i said, unfortunately it requires you reinstall all lr-mess fake cores .... it will simply overwrites the emulators.cfg for each poiniting to the fixed run_mess.sh (which is now referenced directly from the RetroPie-Setup dir).

cheers!

valerino

added MSX2, MSX2+, MSX2Turbo-R to lr-bluemsx.

Zering

@valerino said in new scriptmodules (lr-vice-xvic, gsplus, proper lr-mess integration!):

i suggest you all to update from my repo and reinstall all lr-mess scripts (or, if you prefer, do it messing with each generated emulators.cfg directly).

Sorry for asking what you guys are probably going to think is a noob question, but how do I do that?

valerino

@Zering uhm .... i assume you cloned my repo and replaced RetroPie-Setup.

so, simply

cd RetroPie-Setup
git pull

# then reinstall each of the lr-mess-blabla emulators, they will fix everything
~/RetroPie/retropie_setup.sh

or, alternatively you can do all in one shot (this will reconfigure all lr-mess-xxx it finds).

cd ~/RetroPie-Setup/scriptmodules/libretrocores
for s in lr-mess-*.sh; do sudo ~/RetroPie-Setup/retropie_packages.sh ${s%.*} configure; done

valerino

added lr-mess-m5.sh and lr-mess-gameduck.sh.

also fixed run_mess.sh to correctly support saving retroarch content directory overrides, and fixed a bug in lr-mess-ti994a.sh (need to be reinstalled). i added a note in the first post for whoever wants to add MESS systems using my scripts :)

Zering

@valerino said in new scriptmodules (lr-vice-xvic, gsplus, proper lr-mess integration!):

@Zering uhm .... i assume you cloned my repo and replaced RetroPie-Setup.

Thanks for that. But actually it's cloning your repo and replacing RetroPie-Script I don't know how to do. ^^

roslof

@valerino said in new scriptmodules (lr-vice-xvic, gsplus, proper lr-mess integration!):

added lr-mess-m5.sh and lr-mess-gameduck.sh.

also fixed run_mess.sh to correctly support saving retroarch content directory overrides, and fixed a bug in lr-mess-ti994a.sh (need to be reinstalled). i added a note in the first post for whoever wants to add MESS systems using my scripts :)

Understood (about location of %ROM%). Curious, what was the side-effect?

valerino

@roslof i need it to be the last parameter so i can extract the rom directory from it, which is needed to support saving content directory overrides. if not, i would have needed to add another parameter to run_mess.sh and change all scripts in turn.

valerino

@Zering make a backup of your original RetroPie-Setup, then in /home/pi:

git clone http://github.com/valerino/RetroPie-Setup

then follow my above post.

unfortunately, until all this is properly added to official retropie this is the easier way ..... i'm keeping my repo updated with the upstream repo, anyway, don't worry.

dmmarti

One thing I've noticed, your script creates 2 files in the /opt/retropie/configs/xxx folders being owned by user 'root'.

-rw-r--r-- 1 root root 106 Apr 27 20:44 custom-core-options.cfg
-rw-r--r-- 1 root root 76 Apr 27 20:44 retroarch.cfg.add

Is there a specific reason for this instead of having them be "pi:pi"?

If any updates are done within the Retroarch GUI (like mame_mouse_enable, etc), the changes are not saved since 'pi' does not own the file.

valerino

@dmmarti uhm no, you're right. gonna fix that in the next commit. thanks!

valerino

new systems:

lr-mess-supervision.sh (Watara Supervision)

updated cores:

lr-atari800 (added Atari XEGS)
lr-snes9x (added Sufami Turbo and Satellaview)

also fixed the bug reported by @dmmarti , you need to reinstall all scripts as specified here: https://retropie.org.uk/forum/post/217946 (hope it's the last time this is needed eheheh).

Zering

@valerino said in new scriptmodules (lr-vice-xvic, gsplus, proper lr-mess integration!):

@Zering make a backup of your original RetroPie-Setup, then in /home/pi:
git clone http://github.com/valerino/RetroPie-Setup

And I take it this writes over my current RetroPie setup? And replaces it with yours, essentially?

valerino

@Zering yep, make a backup copy if you want. or, you can take all the files you need from my repo but beware: you need to overwrite the original RetroPie-Setup/packages.sh and RetroPie-Setup/helpers.sh with mine.

in the end, it's really easier to just do as i said and clone mine directly until a better solution (=integrated in the official distro) is found.