trzy / Supermodel

Official repository of the Sega Model 3 arcade emulator.

Home Page:https://supermodel3.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Cannot run any roms on 0.3a, [Error] Could not open '<rom>.zip'. No issue with 0.2a.

bonniebear opened this issue · comments

I am unable to run any rom file, only getting an '[Error] Could not open '.zip' message. This only happens with the last few vision's I've tried of 0.3a (up to 0.3a-git-e59ecea at the time of this post)

I found this thread on the Launchbox forums with the same issues as me, and after trying both the 32 and 64bit versions (I doubt that matters much), the same rom file runs without issue(I have only tried scud.zip on everything since that seems to have the least issues that far back, I can try others if you'd like).

No idea what might be causing the issue with 0.3. Here's my 0.2 error log with most of the relevant hardware info:

Started as:
	argv[0] = Supermodel
	argv[1] = scud.zip

OpenGL information:
                   Vendor: ATI Technologies Inc.
                 Renderer: AMD Radeon RX 6650 XT
                  Version: 4.6.0 Compatibility Profile Context 24.1.1.240110
 Shading Language Version: 4.60
Maximum Vertex Array Size: 536870911 vertices
     Maximum Texture Size: 16384 texels
Maximum Vertex Attributes: 32
  Maximum Vertex Uniforms: 8000

Program settings:
	XResolution               = 496
	YResolution               = 384
	FullScreen                = 0
	Throttle                  = 1
	ShowFrameRate             = 0
	InputSystem               = dinput
	FlipStereo                = 0
	DirectInputConstForceMax  = 100
	DirectInputSelfCenterMax  = 100
	DirectInputFrictionMax    = 100
	DirectInputVibrateMax     = 100
	XInputConstForceThreshold = 30
	XInputConstForceMax       = 100
	XInputVibrateMax          = 100
	MultiThreaded             = 1
	PowerPCFrequency          = 50
	EmulateSound              = 1
	EmulateDSB                = 1
	SoundVolume               = 100
	MusicVolume               = 100
	ForceFeedback             = 0
	VertexShader              = 
	FragmentShader            = 

Audio device information:
    Frequency: 44100
     Channels: 2
Sample Format: 32784

Static vertex buffer size: 61.42 MB
Dynamic vertex buffer size: 5.62 MB
Program terminated normally.

Let me know if you might need further information or need me to try another build.

My guess is that the zip file doesn't exist where Supermodel thinks it does. I don't know how Launchbox works, sorry, but if you cans how me what you are doing on the command line that would help. In this case, scud.zip must be in the same directory as supermodel.exe and it looks like it works. Check argv[0] in the log and it may show you that Supermodel is actually executing from a different directory than your ROM is in.

For troubleshooting the emulator, I am running everything from cmd. No Launchbox, no GUI. (Eventually I want to use Launchbox as a frontend, but after I figure this issue out)

The zip files are in the default \ROMs\ folder in in 0.3 and the main application folder in 0.2.

The whole log when I try to launch it again is:

[Info]  Supermodel Version 0.3a-git-e59ecea
[Info]  Started as:
[Info]    argv[0] = Supermodel
[Info]    argv[1] = scud.zip
[Error] Could not open 'scud.zip'.

I have screenshots of my cmd prompt and windows folder for reference, this should all be correct?

cmd
filesrom

Got it, thanks! Tried that and I think I have found the actual problem here. Now I get

[Error] Unable to initialize SDL audio sub-system: Audio target 'dsound' not available

[Info]  Program terminated due to an error.

So is the emulator trying to access my audio driver but can't for some reason? I'm using standard Windows 10 Realtek HD audio so it can't be that DirectSound isn't there.

Full log-file attached.

Supermodel.log

I have never seen this before personally, although I vaguely recall someone has had this issue on the forums. Not sure what to advise. This has to do with your audio drivers somehow. See if you can update them or otherwise track down the issue. It's likely also going to happen in other SDL2 apps.