Sega model 3 #segamodel3

Folly

@dteam said in Sega model 3 #segamodel3:

@folly said in Sega model 3 #segamodel3:
@mechafatnick said in Sega model 3 #segamodel3:
I will have to take some time to process this information.

@folly WIll people want to skip the initial boot sequence?

Not for fun.
I think they do want it, especially for lemans24, because it will take 1 minute to get the first good screen and be playable.
for the purist it can be frustrating to cut the scene at the beginning..

I don’t know. If you save after that scene and load your savestate the next time. It could be ok?

Perhaps I am not clear, no scenes are cut.
Only the menu saying it is "single" etc. and booting the rom that produces strange screens etc.

DTEAM

@folly
Ok, now i understand. Good idea!
If you do that, can you set the good country to switch japanese to english when it’s available.

Folly

@dteam said in Sega model 3 #segamodel3:

@folly
Ok, now i understand. Good idea!
If you do that, can you set the good country to switch japanese to english when it’s available.

👍

We have to test, don't know.
But I think that can work.

Folly

@mechafatnick

I made a fork of the source-code.
That way I can do some push-requests if needed.

I am still learning with that part so perhaps we can learn from each other about :

syncing/fetching upstream
do pull requests
etc.

Folly

@mechafatnick @DTEAM

I just found that we don't need the NVRAMs if we don't want to.
I made some save-states and booted with them, removing the NVRAMs before the boot made them boot directly without the need of a nvram file.

Something to take into account.

mechafatnick

That's good to know! worth noting that save states are 30mb each though so i'm not sure we should deploy them when we don't have to (i've used one with Skichamp though, to get round an annoying drive board error)

I've updated my repo with the Nvram files and Save state i've created so far + my ini file with my collection of game-related settings (I use Visual Studio Code for source control if that helps)

DTEAM

@mechafatnick @Folly
Maybe you should create a new thread like we did for Development of module-script generator for lr-mess and mame standalone . Like this, you could start with a small crash cours on how to install and use the script and continue with showing where you are in the developpement process.

Because, right now, you don't have the control of the first post in this thread.

Do you think it's a good idea?

Folly

@mechafatnick said in Sega model 3 #segamodel3:

That's good to know! worth noting that save states are 30mb each though so i'm not sure we should deploy them when we don't have to (i've used one with Skichamp though, to get round an annoying drive board error)

Indeed we could just do those that are only problematic.
Others can have just the NVRAMs.

I've updated my repo with the Nvram files and Save state i've created so far + my ini file with my collection of game-related settings (I use Visual Studio Code for source control if that helps)

Will have a look at that.

Folly

@dteam said in Sega model 3 #segamodel3:

@mechafatnick @Folly
Maybe you should create a new thread like we did for Development of module-script generator for lr-mess and mame standalone . Like this, you could start with a small crash cours on how to install and use the script and continue with showing where you are in the developpement process.

Because, right now, you don't have the control of the first post in this thread.

Do you think it's a good idea?

I think that's a good idea.

mechafatnick

@folly

Right, just uploaded a load more default NVRAMs (covering everything i think) along with a .ini with settings for a load more games.

Shocking find of the morning: the Pi can handle the PPC clocked at the real 66hz and beyond. This means we're able to have the sound in games like Spikeout and Daytona with minimal slowdown.

N.B,

Sega Rally loses the menu if you insert coin before the demo mode. SWA won't load the game (iof you wait till Darth Vader appears it works)

Folly

@mechafatnick

Can you rename nvram to NVRAM ?
Can you rename *.st0 to *.st ?
(gamename of the .st has to be like the zip)

Otherwise I it won't work.

Folly

@mechafatnick @DTEAM

I added the module-script to github
link_to_commit

Isn't tested yet on NVRAM and Saves, as the source doesn't have the proper NVRAM directory yet.
If it doesn't find the correct directory, It will install though, but without copying those directories.

mechafatnick

@folly yeah sorry we popped to Costco!

I've renamed those files so it should all work now.

Folly

@mechafatnick said in Sega model 3 #segamodel3:

@folly yeah sorry we popped to Costco!

I've renamed those files so it should all work now.

Perfect, we can test !!!!
Curious if this will work OOB. ;-)

FIXED EDIT: I have to fix an issue, NVRAM and Saves directories are not copied correctly.

Folly

@mechafatnick

Can you check your Supermodel.ini ?
If I use the old Supermodel.ini then it seems to run fine.

I get an error in runcommand.log that says there is an error in line 366 of Supermodel.ini.

If you want more info I can post the runcommand.log

mechafatnick

@folly It's alright! i forgot to put a ; in front of a comment. Updated.

Folly

@mechafatnick

I still have to fix some issues.
Can take a while.......

Folly

@mechafatnick

Can you remove this from the Supermodel.ini ? :

GameXMLFile= /opt/retropie/emulators/supermodel/bin/Config/Games.xml

My module-script places the emulator files in :
/opt/retropie/emulators/supermodel-mechafatnick

I have done this to prevent the mix-up with manual installs that otherwise will brake.
As I use pushd in the runcommand-line it will automatically find the XML file without the need of putting it in the ini file or as an option in the runcommand-line.
With above line still added in ini file , then the emulator will not find the XML because it will search in the wrong directory.

mechafatnick

@folly Done! I suspect the couple of save states will have to be changed too then.

Folly

@mechafatnick said in Sega model 3 #segamodel3:

@folly Done! I suspect the couple of save states will have to be changed too then.

Yes, indeed I saw that.

We have to decide whether we put them in the runcommand-line or in the ini.

If I put it in the runcommand-line the source code is still, sort of, compatible with a manual install and people can add just .st files without editing the ini file.

If you think we should prefer to put it in the ini file, just let me know.