BigPEmu troubles...

[Shredder_guitar]

Ok, I've taken my best shot at setting up BigPemu up for Atari Jaguar CD and not having much luck. The best that I can get it to do is display the RSOD... I have atari Jaguar set up and working just fine...it's CD that I am having issues with. 

Here are my Settings in BigPEmu
 

 

Here are my settings in Launchbox....If i 'uncheck' extract rom to temp folder, then It simply loads to the settings menu in bigpemu

Screenshot of bios and emu, this is located seperate from launchbox on the same drive (location of the emu shouldn't matter....) 

Blue lighting bin/cue format

 

Screenshot of zipped rom files... These files are located on a network drive

 

I will note that If i place an extracted zip in a folder and place that folder in the BigPemu folder and open up BigPemu and play the cue file from there, that the game DOES work...So at this point I'm at a loss because I thought that extracting the zip into a temp folder and loading the game through launchbox was the same behavior as that. Any Help is appreciated. 

THEORY: I suspect that BigPemu doesn't know where to look for the temp extracted rom...how can I tell bigPemu where the extracted rom is and to load the cue file in the directory of that temp extracted rom? (I thought that's what the Default Command-Line Parameter "%romfile% -localdata" was supposed to do, if "Extract ROM Archives before running" is checked, but that appears not to be true...or there is a disconnect between where launchbox knows the rom is and where it's telling BigPemu to look for the extracted rom...if that's even happening at all.) 

*Update*
Ok, interesting find almost immediately after making this post... apparently having "-localdata" in the default command-line parameters causes Atari Jaguar CD to be problematic with loading for some reason, the documentation defines This argument as...
-localdata

Reads/writes all user data (configuration, saved states, screenshots, etc.) in a local (next to executable) "UserData" directory instead of the OS-dependent path.

 I don't know EXACTLY what that means and why it seems to matter, but after removing the flag, Atari jaguar CD's were able to load.... I did have to set my resolution and proper display screen to use...again...which indicates that it's using separate profiles for atari Jaguar and atari jaguar CD, otherwise, this has been solved. I hope that this helps someone in the future figure out why atari jaguar CD's are not able to load. 

 

 

Edited Wednesday at 10:39 PM by Shredder_guitar

[5thWolf]

As far as LB goes,

• I have no Command Line parameters
• In associated platforms extract ROMs is not checked

As for emulation of CD, I don't even have a CD bios set. the games just run.  Have you tried not setting the bios and running the game? Mine are not zipped and are .cdi format and few games as cue.

Edited yesterday at 03:23 AM by 5thWolf

[Shredder_guitar]

2 hours ago, 5thWolf said:

As far as LB goes,

• I have no Command Line parameters
• In associated platforms extract ROMs is not checked

As for emulation of CD, I don't even have a CD bios set. the games just run.  Have you tried not setting the bios and running the game? Mine are not zipped and are .cdi format and .few games as cue.

At one point the bios was not set and it still didn't run...odd that your's just works. I don't know if you did the LB installation of bigpemu.... I didn't I had a seperate install of bigpemu and added it to LB. Glad yours gave you less trouble than mind did. 

[5thWolf]

My install was not from LB.
Think it might be bad game files?

 

Edited yesterday at 04:28 AM by 5thWolf

[JoeViking245]

5 hours ago, Shredder_guitar said:

I don't know EXACTLY what that means and why it seems to matter, but after removing the flag, Atari jaguar CD's were able to load.... I did have to set my resolution and proper display screen to use...again...which indicates that it's using separate profiles for atari Jaguar and atari jaguar CD, otherwise, this has been solved. I hope that this helps someone in the future figure out why atari jaguar CD's are not able to load. 

The -localdata parameter makes it so the emulator is portable.  It creates a folder in the same location as the emulator to store data.  Otherwise (aka without the parameter), all the data is stored in the AppData folder (under C:/users/) making it not portable.

[5thWolf]

Oh snap!!! I will be definitely adding that!!

[5thWolf]

34 minutes ago, JoeViking245 said:

The -localdata parameter makes it so the emulator is portable.  It creates a folder in the same location as the emulator to store data.  Otherwise (aka without the parameter), all the data is stored in the AppData folder (under C:/users/) making it not portable.

I set the parameter and the game wouldn't launch. Removed it and game launched. Also tried it in  a .bat file and is still created the settings in appdata. Did this maybe change on recent versions of the emu? Though it still is in the FAQ as such.

Edited yesterday at 03:59 AM by 5thWolf

[5thWolf]

Hmmmm the FAQ says the command line must come after the file. There a way to tell LB to make the command come after the file? Currently seems to only set it be the
emu > command > file.
I guess it needs to be emu > file > command

Edited yesterday at 04:16 AM by 5thWolf

[JoeViking245]

7 minutes ago, 5thWolf said:

I set the parameter and the game wouldn't launch. Removed it and game launched. Also tried it in  a .bat file and is still created the settings in appdata. Did this maybe change on recent versions of the emu? Though it still is in the FAQ as such.

After adding the parameter, may need to re-setup the emulator (BIOS location etc.).

[JoeViking245]

2 minutes ago, 5thWolf said:

Hmmmm the FAQ says the command line must come after the file. There a way to tell LB to make the command come after the file?

As shown above.   %romfile% -localdata

[5thWolf]

Ah awesome!  Worked perfectly!!!!

Edited yesterday at 04:20 AM by 5thWolf

[Shredder_guitar]

14 hours ago, JoeViking245 said:

The -localdata parameter makes it so the emulator is portable.  It creates a folder in the same location as the emulator to store data.  Otherwise (aka without the parameter), all the data is stored in the AppData folder (under C:/users/) making it not portable.

Then it doesn't make any sense to me why having the -localdata parameter present doesn't work and not having it does work...the opposite should be true. My default command line options were %romfile% -localdata.....so what else could be wrong if having -localdata flag should be present? Do I have a bad profile within the bigpemu emulator that is not set up correctly? 

Edited 19 hours ago by Shredder_guitar

[JoeViking245]

36 minutes ago, Shredder_guitar said:

Do I have a bad profile within the bigpemu emulator that is not set up correctly? 

Anything's possible.

To test, you could try removing the contents of your emulators \UserData\ folder.  Then copy the contents of your \AppData\Roaming\BigPEmu\ folder into it.  Then use the %romfile% -localdata parameter(s).

If that works, you can remove the /AppData/Roaming/BigPEmu/ folder.

[Shredder_guitar]

8 hours ago, JoeViking245 said:

Anything's possible.

To test, you could try removing the contents of your emulators \UserData\ folder.  Then copy the contents of your \AppData\Roaming\BigPEmu\ folder into it.  Then use the %romfile% -localdata parameter(s).

If that works, you can remove the /AppData/Roaming/BigPEmu/ folder.

Well...that worked, actually. I still don't understand, but I'll take it.