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

DTEAM

@folly

No, I followed the instruction from Post #1 and put add-mamedev-systems-2v4.sh

here
/home/pi/RetroPie-Setup/scriptmodules/supplementary

I did that a lot of times. I don't understand why it doesn't work now.

I'm gonna re-downloaded your file

Folly

@dteam

Yes indeed you did that a lot of times, so I was confident you had a correct file.

Not really sure either what the problem is but I am quite confident that the script should work.

Is your sd card still ok ?
No problems at boot ?
Do the older scripts that you tested earlier still work ?

How old is your retropie-image, is it based upon buster ?
Perhaps an idea to update.

Btw. I read that 0237 is out now.

DTEAM

@folly
It works !! I solved the problem . I don't know why, but i had problems to transfer my file. Now It's fine. The problem was on my side. It's not a general issue

Folly

@dteam

Aha you found the problem, great to hear it's working again.

jamrom2

@folly Hiya. Doing good here with the script. I've got all my handhelds working great and moved into the TRS-80 CoCo.

Ran into a question there.. I don't see a CoCo disk/flop1 option to add in to my list.

How do I use .dsk images with this system. I'd rahter not have both the TRS-80 and the Coco, just one works for me as I already have the Dragon32 running.

Thanks!

Folly

@jamrom2

The system coco has FDC support (floppy drive controller) as an external slot, reading from the mame output.

So by default it will not support a floppy drive controller out of the box and so my script will not detect support for floppy-drive media.
No detection means that no module-script for that media is created and installed.

To be able to do that a manual line should be created to be able to add FDC support.

Looking at the mame output for coco2 or coco3, they will have FDC support OOB.

Don't know for sure, but perhaps the easiest way is to install one of these :

Driver coco2 (Color Computer 2): *computer*non-arcade
Driver coco2b (Color Computer 2B): *computer*non-arcade
Driver coco2bh (Color Computer 2B (HD6309)): *computer*non-arcade
Driver coco2h (Color Computer 2 (HD6309)): *computer*non-arcade
Driver coco3 (Color Computer 3 (NTSC)): *computer*non-arcade
Driver coco3dw1 (Color Computer 3 (NTSC; HDB-DOS)): *computer*non-arcade
Driver coco3h (Color Computer 3 (NTSC; HD6309)): *computer*non-arcade
Driver coco3p (Color Computer 3 (PAL)): *computer*non-arcade
Driver cocoe (Color Computer (Extended BASIC 1.0)): *computer*non-arcade
Driver cocoeh (Color Computer (Extended BASIC 1.0; HD6309)): *computer*non-arcade

jamrom2

@folly I put those into \BIOS\mame as well as \roms\coco

what do I pick as far as an eumlator? the lr-mame-basename, lr-mess-cmd? or any other?

jamrom2

on top of this, a few games appear to be corrupt roms and do not work properly under MESS.

a lot of artifacting and lines all over stuff. Worse is Dungeons of Daggoorath, the only reason really for me to even have the TRS-80.

I was hoping to get Flight Simulator II working as well... but that's a .dsk image.

Controls for left, right, up and down not working either. Mapping is there, but doesn't look like the system is recognizing it.

Folly

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

@folly I put those into \BIOS\mame as well as \roms\coco

what do I pick as far as an eumlator? the lr-mame-basename, lr-mess-cmd? or any other?

Explain better.

It seems you did not understand my post.
Adding the files to the directories doesn't do anything if you don't install, for example coco2, first.

If you do that a line with floppy will appear for booting a disk.
I suggest you use that.

The basename and cmd lines are only used if you want to :

make use of handmade .cmd files
if you want to run system-game bios files directly (as with classich)
if you want to run the software so mame or lr-mess will check the database, if in database, and try to boot it depending on that.
(we discovered that there are still issues using this and some combinations need fixing, but this is a difficult process, so still many combinations will not work)

jamrom2

@folly

Ok. how do I add coco2? Where does that come from?

Folly

@jamrom2

Select coco2 or coco3 in my script and it will be installed.
Select All systems > submenu.

etc. :

Rom directories become coco2 and/or coco3.
and make sure you have the bios files too.

jamrom2

@folly

well.. that's why... I don't have that list.

I must be behind a version in the script. Is that from a new version you created?

nevermind... I see you did. Let me update and see what I get.

Folly

@jamrom2

It should be in there.
All older versions have it.

If you want the latest.
Check here :
https://github.com/FollyMaddy/RetroPie-Share/blob/432d2c9db4b1497ba2da938cef1968621c5c2570/00-workdir-00/add-mamedev-systems-2v4.sh

Right-click RAW and save it where it has to be in :
/home/pi/RetroPie-Setup/scriptmodules/supplementary

Remove the old versions.

jamrom2

@folly I didn't realize it was "buried" in the massive list of systems.

That is some list, wow.

At any rate, I have it running and looked up some load commands to get it working. Works great.

This brings the question about systems. The idea of using Retropie is to sort of isolate or condense several systems under one umbrella. These old Computer systems kinds present their issues with the amount of variances to them, some with little change. Like the Apple, we saw it was best to go Apple IIe and Apple IIgs.

What about a Tandy package that covers the Coco, Coco2 and Coco 3 plus the TRS-80 16? Otherwise Emulationstation is going to require a lot more themes for each system and each of the variants.

Right now, I have Tandy Coco for carts and cass, Coco 3 for Disk and TRS-80 16 for really old stuff. I think this is overkill.

What are your thoughts on this?

Folly

@jamrom2

Well you have got a point there.

For some systems the script is already doing that.
For instance classich is generated if one of the systems is installed from what we think should be in the classich.
With konamih etc it's the same.

The script also looks for other matches.
Different MSX types will automatically be installed under MSX.

But not all can be automatically matched.

So for some, like for instance, BBC micro or Amiga, the names are changed on the fly a bit to generate a match to RetroPie system name
(you call it the umbrella name)

Before we add such an umbrella we have to make sure these types are almost the same.
If the systems not alike it's better to keep them separate.

For arcade only systems I want to do somewhat the same but the problem is I don't want to add 34000 systems in the script for checking. So I have to think of an other solution. Besides, for a few weeks ago we didn't even had the possibility to sort arcade from the non-arcade. now we can, so the solution is more within reach.

So the project is evolving from

a standalone generator-script (still available)
to a front-end script which includes the generator-script
and now to a front-end with data-manager that still includes the generator-script

Hope you understand all this.

jamrom2

@folly

I certainly do and I like it. Thank you for all the work. It's great to have all these individual systems fully running

Folly

@jamrom2

I added some special things in the latest script.
For instance you can use the search option now.
Just type in what you are looking for and it will generate the list for you.
And there is more.

Folly

I added the new mame0237 database with sorted_info and tried to add as much search entry's as possible.
Here you can read the .ini files used for adding the search entry's :
https://github.com/FollyMaddy/RetroPie-Share/blob/55ecbb14bf6774efb093eb62917f9cafad05fa9e/00-databases-00/sorted_info_creation/readme.md
I did not add the normal arcade entry as this is files huge.
If we want to sort on arcade we can do an inverted search of "@non-arcade!" and we get all the arcade without adding the data to the file.

Also added a script update for mame0237.
I decided to take the version number of mame for the new update.
Then it's easy to know that the script is made for the mame0237 data.

Summarized :

data 0237 entry's are added earlier with "@"
("*" isn't used anymore because of compatibility issues with lubuntu)
(searching can be done with "@forum", for example)
uses mame0237 data
add subgui for restricted browser / downloader for adding more.
minor improvements / fixes

https://github.com/FollyMaddy/RetroPie-Share/blob/55ecbb14bf6774efb093eb62917f9cafad05fa9e/00-workdir-00/add-mamedev-systems-0237.sh

jamrom2

@folly

Hi. Thought I'd get back to you with a lot of results and try to narrow down the Tandy Coco/TRS-80 setup.

I've been playing around with various .cass, .rom .ccc and .dsk images. I've found that there is an issue with the Tandy Coco1 (coco) side of the emulator. The video artifacting doesn't work properly on many of the games. I was thinking it was me, but after testing some of the .cass versions of the same game on both systems, and seeing that they work in the coco3 variant, I realized it's definitely MESS causing this.

So that brings me to the possible answer. The Tandy Coco3 is the best choice for all four game file forms as it seems the game files in all forms work the best, although do not look the best. The image is very sharp on the Coco3, unlike softer colors and warmer CRT look of the Coco (even though I have a CRT shader active on both). The Coco video artifacting just does not handle the game files well on the Coco and gives all kind of corrupt images. You can see what I mean with the attached images.

This is one thing I never liked about MESS, it's a great emulator with all kinds of possibilities, but because it emulates so many systems, there are bound to be issues somewhere. I've played around with what little options you have to sort the artificating issues, but nothing helps. So I moved on and will just use the Coco3 emulator. To me, as a gamer only, the TRS-80 12/16 is basically useless to have in my system choice as it just doesn't have many game choices that are worth playing.

That's the thing with Retropie. Most users are looking for just getting the games working, and not the variants. Like the Apple IIe and IIgs, the same can be said for the Tandy. Best to go with what works and gives the user the best/easiest experience. Not sure if that is the goal of the project, or if it's just to get things working, but I can say for most that their goal is to have systems that work with little effort.

Using the keyboard on the Tandy is another issue, but anyone that uses Retropie for old PC emulation knows they have to tweak things to get it all to work. Since they added "game focus" to the options, that has to be turned on in order to use some of the keys on the keyboard.

At any rate, it's been challenging to get all these systems working and see what works best for a common user/gamer. I'd say the Coco3 is the best for the Tandy selection.

jamrom2

Coco2 works really well. And has the softer look that the Coco1 has. I'm going to use that as well.