new scriptmodules (lr-vice-xvic, gsplus, proper lr-mess integration!)
-
@valerino said in new scriptmodules (lr-vice-xvic, gsplus, proper lr-mess integration!):
uhm ... looking here: https://github.com/RetroPie/RetroPie-Setup/pull/3109 (my old pull request) seems there's no intention to integrate this is in the main repo.
I don't know why you got that impression, you're more than welcome to add something new to RetroPie. Any PR might receive correction, comments - you've received already quite a few.
-
@mitu indeed i replied to that PR. ok for lr-vice (that was just an experiment), but for lr-mess there's no other way to currently integrate it easily, my solution seems easy enough (fact) and without side effects.
probably yes, a separate menu without polluting the 'exp' section is needed. i'm working on it. -
@valerino said in new scriptmodules (lr-vice-xvic, gsplus, proper lr-mess integration!):
lr-mess there's no other way to currently integrate it easily, my solution seems easy enough (fact) and without side effects.
What exactly is the issue with
lr-mess? Maybe there is an alternate solution. -
@mitu ah, don't ask me :)
https://github.com/RetroPie/RetroPie-Setup/pull/3109#issuecomment-620490323
of course there will be other solutions. i proposed mine, implemented it and it seems enough stable, easy to add other systems, isolated each one, and safe to use. that's why i'm sharing it.
-
@valerino said in new scriptmodules (lr-vice-xvic, gsplus, proper lr-mess integration!):
@mitu ah, don't ask me :)
No, I meant what is the problem that you're trying to solve with that alternate solution that you proposed and why
lr-messcannot be run like the other Libretro cores. -
@mitu because you're forced to use softlists with lr-mess, or anyway 'mess' yourself with configurations after the installation to have everything running from the frontend 'as normal'. and mess systems are like separate cores anyway.
with my solution you have each system ready out of the box, easy. -
@valerino said in new scriptmodules (lr-vice-xvic, gsplus, proper lr-mess integration!):
because you're forced to use softlists with lr-mess, or anyway 'mess' yourself with configurations after the installation to have everything running from the frontend 'as normal'.
What's the upstream recommendation/default ?
-
@mitu https://github.com/retropie/retropie-setup/wiki/MESS
it works like mame, you need to have roms named the way they're defined in the softlists, plus they need to match a hash. it's completely non-practical for computer systems.
my way you can use whichever rom you want, as with every other emulator.
i wouldn't have spent the last week nights doing that if it already existed, believe me :) -
@valerino said in new scriptmodules (lr-vice-xvic, gsplus, proper lr-mess integration!):
my way you can use whichever rom you want, as with every other emulator.
I see, except that MAME/MESS doesn't always work like that.
We have a special section in the Docs for Arcade to emphasize the need to use the proper ROMset (validated) for the MAME version and still get a lot of question from users that copy a random/incorrect MAME roms and they get an error.
I understand that the 'no softlist' method it's easier, but wouldn't also lead to similar issues as with arcade emulation ?
-
@mitu well, mess is a bit different than mame (i know they now converged, but for simplicity keep them separate).
mess emulates different computer/console systems, they will load everything as normal (as any computer/console do in other emulators), once booted their BIOS/OS. mess just enforces the BIOS is correct through hashes, and that's right.
the additional 'softlist' enforcement i really don't know why it has been put in place for mess, luckily it can be disabled.mame is a completely different beast. each mame driver (well, mostly) is specific for a game, which may exist in different dump version. that's why you have i.e. 5 versions of dkong.zip, for example. still, it's the same game.
with mess you have i.e. the samcoupe driver, which will just ensure to load the samcoupe bios/os. that's all. then you put whichever disk/tape you want, as with every other computer emulator. you don't have people begging stuff don't work for i.e. lr-vice. or, if there's any, you just simply answer 'live with it'.hope i've been clear.... i understand you want to protect from begging users, i'm all for practical things i know....
-
anyway, i keep adding systems on my fork until i'm done :)
added SamCoupe (lr-mess-samcoupe) and Amstrad GX4000 (lr-mess-gx4000) -
Good Afternoon All
I have just download the Retropie 4.6 version and I was wondering if the setup folder that you copy over is compatible with this new version.
Rgds
CCF
-
@CCFox i don't know. probably is, i also updated mine and my repo is on par with 4.6 now.
anyway, just backup first, don't worry for you retroarch configuration etc... they're not touched anyway by my code. -
I updated to Retropie 4.6 and the installation went fine as expected. I copied over that Retropie Setup folder and installed lr-vice. I then tried to install lr-xvic and it failed. Log below:
Log started at: Tue 28 Apr 20:01:32 BST 2020
RetroPie-Setup version: 4.5.20 (21a099a7)
System: Raspbian GNU/Linux 10 (buster) - Linux retropie 4.19.97-v7+ #1294 SMP Thu Jan 30 13:15:58 GMT 2020 armv7l GNU/Linux
/home/pi/RetroPie-Setup/tmp/build/lr-vice-xvic /home/pi= = = = = = = = = = = = = = = = = = = = =
Getting sources for 'lr-vice-xvic' : Commodore Vic20 emulator - port of VICE for libretro
= = = = = = = = = = = = = = = = = = = = =git clone --recursive --depth 1 --branch master "https://github.com/libretro/vice-libretro.git" "/home/pi/RetroPie-Setup/tmp/build/lr-vice-xvic"
Cloning into '/home/pi/RetroPie-Setup/tmp/build/lr-vice-xvic'...
Checking out files: 35% (3049/8514)
Checking out files: 36% (3066/8514)
Checking out files: 37% (3151/8514)
Checking out files: 38% (3236/8514)
Checking out files: 39% (3321/8514)
Checking out files: 40% (3406/8514)
Checking out files: 41% (3491/8514)
Checking out files: 42% (3576/8514)
Checking out files: 43% (3662/8514)
Checking out files: 44% (3747/8514)
Checking out files: 45% (3832/8514)
Checking out files: 46% (3917/8514)
Checking out files: 46% (3991/8514)
Checking out files: 47% (4002/8514)
Checking out files: 48% (4087/8514)
Checking out files: 49% (4172/8514)
Checking out files: 50% (4257/8514)
Checking out files: 51% (4343/8514)
Checking out files: 52% (4428/8514)
Checking out files: 53% (4513/8514)
Checking out files: 53% (4585/8514)
Checking out files: 54% (4598/8514)
Checking out files: 55% (4683/8514)
Checking out files: 56% (4768/8514)
Checking out files: 57% (4853/8514)
Checking out files: 58% (4939/8514)
Checking out files: 59% (5024/8514)
Checking out files: 60% (5109/8514)
Checking out files: 61% (5194/8514)
Checking out files: 62% (5279/8514)
Checking out files: 63% (5364/8514)
Checking out files: 64% (5449/8514)
Checking out files: 65% (5535/8514)
Checking out files: 66% (5620/8514)
Checking out files: 67% (5705/8514)
Checking out files: 68% (5790/8514)
Checking out files: 69% (5875/8514)
Checking out files: 70% (5960/8514)
Checking out files: 71% (6045/8514)
Checking out files: 72% (6131/8514)
Checking out files: 73% (6216/8514)
Checking out files: 74% (6301/8514)
Checking out files: 75% (6386/8514)
Checking out files: 76% (6471/8514)
Checking out files: 77% (6556/8514)
Checking out files: 78% (6641/8514)
Checking out files: 79% (6727/8514)
Checking out files: 80% (6812/8514)
Checking out files: 81% (6897/8514)
Checking out files: 82% (6982/8514)
Checking out files: 83% (7067/8514)
Checking out files: 84% (7152/8514)
Checking out files: 84% (7157/8514)
Checking out files: 85% (7237/8514)
Checking out files: 86% (7323/8514)
Checking out files: 87% (7408/8514)
Checking out files: 88% (7493/8514)
Checking out files: 89% (7578/8514)
Checking out files: 90% (7663/8514)
Checking out files: 91% (7748/8514)
Checking out files: 92% (7833/8514)
Checking out files: 93% (7919/8514)
Checking out files: 94% (8004/8514)
Checking out files: 95% (8089/8514)
Checking out files: 96% (8174/8514)
Checking out files: 97% (8259/8514)
Checking out files: 98% (8344/8514)
Checking out files: 99% (8429/8514)
Checking out files: 100% (8514/8514)
Checking out files: 100% (8514/8514), done.
HEAD is now in branch 'master' at commit '61c8c53ae99614b79c6014c483ba48a1e1a469eb'
/home/pi
/home/pi/RetroPie-Setup/tmp/build/lr-vice-xvic /home/pi= = = = = = = = = = = = = = = = = = = = =
Building 'lr-vice-xvic' : Commodore Vic20 emulator - port of VICE for libretro
= = = = = = = = = = = = = = = = = = = = =make: Makefile.libretro: No such file or directory
make: *** No rule to make target 'Makefile.libretro'. Stop.
make: Makefile.libretro: No such file or directory
make: *** No rule to make target 'Makefile.libretro'. Stop.
/home/pi
Could not successfully build lr-vice-xvic - Commodore Vic20 emulator - port of VICE for libretro (/home/pi/RetroPie-Setup/tmp/build/lr-vice-xvic/vice_xvic_libretro.so not found).Log ended at: Tue 28 Apr 20:02:22 BST 2020
Total running time: 0 hours, 0 mins, 50 secsI will try Plus 4 and report back
KR
CCF
-
-
@CCFox uhm. same happens to me. lr-vice repo has changed and the lr-vice retropie scripts (both upstream and mine) has not been updated.
fix is simple, in all lr-vice.sh, lr-vice-xvic.sh,lr-vice-blabla just replaceMakefile.libretro
with
Makefile
that's all.
i will fix in a commit later on my fork. -
-
@CCFox i just committed the fix on my repo
-
I am currently installing lr-mess and it has so far as writing 4 hours. it is 3.30am here in England.
Is this normal?
Rgds
CCF
-
@CCFox said in new scriptmodules (lr-vice-xvic, gsplus, proper lr-mess integration!):
I am currently installing lr-mess and it has so far as writing 4 hours. it is 3.30am here in England.
If you're installing from source, it takes a long time to compile. On a (stock) Pi3B took me more than 1 day. The Pi4B is more powerful, it's faster to compile and it doesn't take that much.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.