Jump to content
LaunchBox Community Forums

Saturn Stopped Loading/Working After 13.19 Update!


Go to solution Solved by Tsik,

Recommended Posts

Posted

Hello - After the 13.19 update my Launchbox cannot run Sega Saturn when using Retroarch as the emulator. It just loads into the Saturn bios as if there were no disk in the console. I had no problem loading and playing Saturn games before the update. 
please help

Thank you.

Saturn Bios.jpg

Posted

The game file formats I'm using are .CHD and .CUE. Neither of them will launch through Launchbox or Bigbox. However I can play them in Retroarch if I don't use Launchbox.

  • 2 weeks later...
Posted

The first thing you'd want to do is to look at the following places in LaunchBox in order to trace what is going on.

Choose one of your games and follow this trail:

  • Edit the game, go into the Launching section and make sure the path to the game makes sense and that the file it's pointing to is there
  • Go into the Emulation section and make sure it's using your correct emulator
  • Enter into the Emulator section and make sure settings look correct
  • Click on the Associated Platforms section and make sure Sega Saturn is listed there and that the settings for it look correct

If you can't find anything wrong, take screenshots of each section and post them here for others to look at.

Posted (edited)

Hello there Ipman559 

I assume that the game is loading through RetroArch as stand alone, it looks like your paths are messed up...

> Retroarch path should start with something something like ..\

RetroarchLaunchboxPath.thumb.png.15690b35da9901772b8af72d68eb0007.png

> Rom path should be something like ..\

RomLaunchboxPath.thumb.png.f9368d76ec567d02a9ca57841696f417.png

Please take the time and re-browse for the files both Retroarch.exe and the Rom file and test again. 

*(I say re-browse using the "Browse" button and not just edit the path so that Launchbox could auto-compensate the paths correctly as they should be)

> Also un-tick the box "attempt to hide console window" in Retroarch edit.

 

Edited by Tsik
Posted

Hi @Tsik, I am able to load games through Retroarch standalone.

 

I tried adding the ..\ to the emulator path.

image.thumb.png.617a35c28f88fe26017784c7a4cf24aa.png

 

But that created this error.

image.png.568df16e36be4625c211441d384069e1.png

 

I believe the .. is a visual indication when you have a long file path. the dots don't really do anything. However I did go through and verify that my file paths were correct by using the "Browse" technique. Same issue.

I appreciate the help. Thanks

Posted (edited)

Actually the ..\ is not there just for visual, its there for "relativity" or "portability" reasons meaning that your system (LaunchBox) is independent of the drive letter that its installed (if lets say you have installed it in a external hard drive G:\ considering the relative paths between LaunchBox and the files used).

If the system throws an error like this then there is definitively something going on with the way you installed everything and i mean the installed locations/paths or something like this. 

In Post 2 i noticed that the paths don't match:

Location1.png.a0e38ce5baebc6858f61bcc39b9cf949.png

Location2.png.05b934fe2437ba0b5fad7886d0ef317a.png

the "ARCADE" part is missing from LaunchBox and the 'Sega Saturn' part perhaps has more than once space between the words!

Again use the browse button in the emulator edit window and point to the actual RetroArch.exe file (no adding anything by hand) and also the in the launching section of the game edit to point to the actual rom file where your rom .chd "lives", this ensures that the paths used are pointing correctly to the files they suppose to.

If Retroarch is installed inside LaunchBox\Emulators it must be like this:

Retroarchpath.thumb.png.4f73b8784ee5cc35e7f8e14045955123.png

The ..\ part is automatically added by Launchbox only if the emulator is installed outside the Launchbox directory.

Also in the game edit window in the Launching tab the path will be something like this:

Rompath.thumb.png.b0a4137f444e00cdf988446849d0d850.png

(Notice that I'm using one space between '\Sega Saturn\' and no '\Astal (USA) (3S)\' folder but that's just me, you can leave those if you want 😁)

Edited by Tsik
Posted

Hi @Tsik I tried taking the Astal rom file out of its folder and placed it directly into the rom folder to eliminate the extra folder as the issue.

I then re-browsed its file location. Still no dice!

 

Might you share with me which Libretro Core you are using for both the standalone Retroarch and the Launchbox Associated Platform?

image.thumb.png.9e358ba747bc1aef9c976bd54eaae14c.pngimage.thumb.png.ebabaa8b7127a55bdd6397d57e21058a.png

The only Libretro core that works for my Retroarch standalone is Beatle Saturn, all the other cores freeze when I try using them i.e. Yabause and Yabasanshiro.

 

Because Beatle Saturn works in the Standalone I choose mednafen_saturn_libretro in the Launchbox Associated Platforms because the internet says mednafen is the same as Beatle Saturn.

 

I was hoping you could share with me which cores you use on Retroarch and which core you associate with on Launchbox.

 

FYI - I have tried every Saturn Libretro available within the Associated Platform of Launchbox. I get the same result every time no matter which one I pick.

 

Theoretically - If I can use Beatle Saturn Core in Retroarch standalone then I should be able to use it as the Associated Platform for Launchbox.

 

Thank you for your continued help and patience 😅

Posted
1 hour ago, Ipman559 said:

Might you share with me which Libretro Core you are using for both the standalone Retroarch and the Launchbox Associated Platform?

Sure why not 😀, I play all my Saturn games with Beetle Saturn (mednafen_saturn_libretro) [including Astal] and Kronos (Kronos_libretro) for STV, 

Yabause and YabaSanshiro are a bit outdated and are not recommended as it says here and here

1 hour ago, Ipman559 said:

because the internet says mednafen is the same as Beatle Saturn

Mednafen is indeed a fork Beetle Saturn (Libreto Link).

Retroarchcoresassoc.thumb.png.7d53cb8888a205a7d83d0aa24878df4c.png

(Skip the --appendconfig...cfg part above as it doesn't matter, keeping only the default -f)

Now lets take it from the start using only 'Beetle Saturn' shall we? 🙂...

Let me ask some questions (assuming your paths in LaunchBox are correct):

- Was the problem about freezing or not booting the game (loads to Bios only)?

- Does the problem occurs in all of your Saturn games or just Astal? (If you have any other than that..)

- Did the bios files needed for Beetle Saturn are the correct? (look in the core info for the md5)

mednafen_saturn_libretroinfo.thumb.png.23fd7ed4e0fc96504cdd9031be9afdc0.png

- Did you try to remove the Beetle Saturn config options (Beetle Saturn.opt) file from the config folder in order to reset the options? (I use all the default ones)

- What version of RetroArch/Core are you using?  

Retroarchandcoreversion.png.f5fa3148dd0e18453de22cd12cb66c9e.png

As the last step try a temporary fresh installation of Lunchbox/Retroarch in another location and import your game/s just for that System.

Posted (edited)

Oh wait... I just saw that the 'Extract Roms' boxes for all your platforms are ticked !!!

2 hours ago, Ipman559 said:

image.thumb.png.ebabaa8b7127a55bdd6397d57e21058a.png

If your rom file is in .chd format this option is not needed.!

It is only used if the rom file is .zip compressed.🙂

Edited by Tsik
Posted

@Tsik 

In response to your questions

image.thumb.png.cd41b732280ced0a37d25c2f9c63dc1a.png

My problem is the game won't boot, it goes directly to the bios every time.

Yes, the problem occurs no matter which Saturn game I try to launch.

Yes, my bios files match your screenshot exactly... See below

image.thumb.png.8002e69d9be30d2938b39ebe61b840e8.png

I removed the Beetle Saturn config file .opt and restarted and launched a game through Retroarch.

Here is the version I am running

image.thumb.png.9537c90903e4e5e497c488a62068f3e7.png

Everything seems to be correct. I am running the latest version of both Retroarch and Launchbox. I never used to have a problem launching Saturn games via Launchbox until I updated to 13.19. I even updated to and am currently running 13.20. 

 

I'd sure hate to uninstall and reinstall Launchbox. I've never had to do that before. Is there a way to do that without loosing all my media files? My current Launchbox file size is 130 GB 😭

image.png.7159062c6e1548dfac64011dde64b4fe.png

  • Solution
Posted (edited)

Hey, I hope I caught you.!

You don't have to uninstall anything, first did you uncheck the the 'Extract Roms' boxes from the Platform assoc. window? (this option is 'off' by default)

You can install Launchbox a second time in a separate temporary location just for testing.

When I am doing test with beta releases for example i temporary rename my current installation folder to let's say "Launchbox [Bauckup]" and then reinstall an other instance in the same Location as before or in another folder,

After testing just delele the LaunchBox-test folder and rename "LaunchBox [Backup]" back to "LaunchBox" everything will be back to normal.

Remember Launchbox is made that it is completely system independent and DRM free so you can have as may installations as you want in the same machine.

I' am pretty sure that your problem does not associated with your Launcbox version because i am using the latest 13.19 in my Win10/11 PC without any problems.🙂

Edited by Tsik
Posted

@Tsik Okay, I figured out my problem. I did as you suggested above. I setup a new instance of Launchbox. Did a fresh install and downloaded a few Saturn roms from the Archive. Without any setup modifications at all the games simply launched and played just fine without issue.

I then went back to my current build of Launchbox. Deleted the Saturn Platform and imported the new rom files I just downloaded and without issue the games launched as they should.

I guess I just needed to dump my Saturn roms and start fresh!

Thanks for the help.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...