Development of module-script generator for lr-mess, lr-mame and mame standalone

RussellB

Can I recommend moving the location of the run_mess file away from the home directory and into something like /opt/retropie/scripts? I moved it because I don't like having rom dependencies in the home folder.

RussellB

Folly

@russellb said in Development of module-script generator for lr-mess and mame standalone:

@folly,

Can I recommend moving the location of the run_mess file away from the home directory and into something like /opt/retropie/scripts? I moved it because I don't like having rom dependencies in the home folder.

RussellB

I understand what you mean, but there problems doing it that way.

The problem is, the run_mess.sh script is within the fork of @valerino of the RetroPie-Setup.
So when you clone the repository the run_mess.sh script is already there.
In the github Repositories you don't have the directories /opt/retropie/...... .
If you want it there you have to "install/copy" it.
So that is why it's in that place.

If we really want this, all the 30+ valerino scripts have to be changed by hand.
And you have to make an installer part for the run_mess.sh.
I don't think Valerino has time for that.

I could change my script, but then it isn't compatible anymore with the Valerino fork.
An other reason not put in /opt/retropie/...... is, you have to be "root" to copy it in that folder.
My generator script, the one without the front-end gui, can be run without root user.
I like to keep it that way.

So overall, it is better to keep it this way to avoid problems.

I hope you understand.

Folly

This post is deleted!

Folly

This post is deleted!

Folly

I had a bad connection so my post was tripled.
That's why I removed above posts.

RussellB

@folly said in Development of module-script generator for lr-mess and mame standalone:

@russellb said in Development of module-script generator for lr-mess and mame standalone:

@folly,

Can I recommend moving the location of the run_mess file away from the home directory and into something like /opt/retropie/scripts? I moved it because I don't like having rom dependencies in the home folder.

RussellB

I understand what you mean, but there problems doing it that way.

The problem is, the run_mess.sh script is within the fork of @valerino of the RetroPie-Setup.
So when you clone the repository the run_mess.sh script is already there.
In the github Repositories you don't have the directories /opt/retropie/...... .
If you want it there you have to "install/copy" it.
So that is why it's in that place.

If we really want this, all the 30+ valerino scripts have to be changed by hand.
And you have to make an installer part for the run_mess.sh.
I don't think Valerino has time for that.

I could change my script, but then it isn't compatible anymore with the Valerino fork.
An other reason not put in /opt/retropie/...... is, you have to be "root" to copy it in that folder.
My generator script, the one without the front-end gui, can be run without root user.
I like to keep it that way.

So overall, it is better to keep it this way to avoid problems.

I hope you understand.

Got it. Thanks.

Folly

@dteam

Here a small update on the progress on the front-end module script :

I am working on the front-end module-script add-mamedev-systems-test5.sh.
I have made some progress in rebuilding and building stuff into the front-end.
I can now generate sub-menu's for #,A,B,C etc .
But I can't show the systems already in there, this seems quite difficult at the moment.
Progress is really slow at the moment.

I have to leave it for a while and re-think my approach again.
I hope I can find some better/easier ways.

Another idea is to make this script in such a way that I can just copy and paste my generate-systems-lr-mess_mame-2v0-alpha.sh into the front-end module-script.
That way I can just maintain the 2v0 script and paste it into the front-end each time when I update it.

DTEAM

@folly said in Development of module-script generator for lr-mess and mame standalone:

Another idea is to make this script in such a way that I can just copy and paste my generate-systems-lr-mess_mame-2v0-alpha.sh into the front-end module-script.
That way I can just maintain the 2v0 script and paste it into the front-end each time when I update it.

This is what I am doing at the moment with V1.8.

Folly

@dteam

Ok, yes indeed you can do that too.
Btw. I have been keeping 2.0 and 1.8 both up to date.

DTEAM

@folly
I know. I updated my cdimono1 with v1.8 to see what RussellB did.

I'm running adam for coleco_sgm with MAME. I created a separate folder for that (coleco_sgm). Everything goes well exepted the MAME UI menu. I'm not able to go in. Have you a solution for that. It's the first time I met this problem.

mame-system-adam-cart1 = "/opt/retropie/emulators/mame/mame -v -c adam -cart1 %ROM%"

Folly

@dteam

You should use the scroll-lock key to toggle between FULL and PARTIAL emulation.
With PARTIAL the UI should be enabled.

If this doesn't work we have to look further.

Folly

@RussellB

I added your edited code to my repository.
I also added it to my standalone scripts :
generate-systems-lr-mess_mame-1v8-alpha.sh
generate-systems-lr-mess_mame-2v0-alpha.sh
When running above script, the run_mess.sh script is always updated by the script.

https://github.com/FollyMaddy/RetroPie-Share/tree/main/00-scriptmodules-00

This shows the difference betweem the original and yours :
https://github.com/FollyMaddy/RetroPie-Share/commit/5f915ca6d2e05f3ff6f0dc7fe6b8ff21ca1d6677

Folly

@DTEAM @RussellB

I did one test.
Can you both do some tests too ?

I like to know if it still works ok.

DTEAM

@folly said in Development of module-script generator for lr-mess and mame standalone:

@dteam
You should use the scroll-lock key to toggle between FULL and PARTIAL emulation.
With PARTIAL the UI should be enabled.
If this doesn't work we have to look further.

Fixed. It was a simple problem with my default.cfg file in /home/pi/RetroPie/roms/mame/cfg
Not a real issue

Folly

@dteam

Indeed, I was thinking you knew about the scroll-lock part ,so indeed it had to be something else.
Nice to have that one fixed !

DTEAM

@folly said in Development of module-script generator for lr-mess and mame standalone:

I did one test.
Can you both do some tests too ?
I like to know if it still works ok.

~~Nothing happens for me. Is It supposed to generate a .cmd (per game) file in /home/pi/RetroPie/roms/cdimono1 when we load a game?~~

It works

Folly

@DTEAM

Nice to hear it works !
I think @RussellB will test it with some bezels, don't you think too ?

Folly

For those who are reading these posts and really don't know what the run_mess.sh does :

The run_mess.sh makes a temporary <game>.cmd file to start the game with lr-mess and adds all the necessary things in this .cmd file to start the game correctly .
The original version of run_mess.sh always made the same <game>.cmd named tmpmess.cmd .
After you have played the game, this tmpmess.cmd file is removed again.

The edited version of run_mess.sh now makes the <game>.cmd named after the game.
That way it's unique per rom/game.
This allows us to specify custom configs, including bezels and screen locations, etc. per rom/game that wasn't possible with the original run_mess.sh.

DTEAM

@folly
SOLVED : For Coleco_sgm, I'm trying set scroll-lock automaticly when we the system load.

~~Any idea~~ you need -ui_active

mame-system-adam-cart1-autoframeskip = "/opt/retropie/emulators/mame/mame -v -c -autoframeskip adam -ui_active -cart1 %ROM%"

Folly

@dteam

I tried this :

mame-system-adam-cart1-ui = "/opt/retropie/emulators/mame/mame -v -c adam -uimodekey TAB -cart1 %ROM%"

Now the TAB works as (SCRLOCK + UI) button at the same time.
Seems quite nice, you preserve FULL keyboard emulation until TAB is pressed.

Edit :
I will try that -ui_active too.
OK, that works too, nice finding !

It looks like you boot in PARTIAL keyboard emulation.
Don't know if that could be a problem.

We should do some more tests.
This would be nice function to add, it could make things much simpler..