NullDC 104r50 Crashing with Autoload

[newmanfamilyvlogs]

I've seen several threads on various forums addressing the issue of NullDC crashing when Autoload=1 and a default image is specified. However this also seems to be the preferred method for launching games via a frontend (in my case, Hyperspin).

Does anyone know what causes this crash and how to resolve it?

[Jollywest]

It could be System Specific, not sure what setup you have but I run NullDC without problems on the following spec (albeit on GameEx);

Intel 8400 cpu
Radeon HD4870x2 gpu
Vista 64-bit
4Gb Ram

I've attached my NullDC.cfg file.

The command line I use for NullDC in GameEx is as follows;

nullDC_Win32_Release-NoTrace.exe -config ImageReader:DefaultImage="[ROMPATH]\[ROMFILE]"

I would of thought this will be different for you using HyperSpin, and would probably also depend on if your using Hyperlaunch, but the Parameters should be similar if not the same.
Maybe someone could chip in with an exact command line to run NullDC on HyperSpin... 

[newmanfamilyvlogs]

This happens outside of hyperspin.

[Jollywest]

Sorry I took your question slightly the wrong way, thinking that NullDC crashed when Autoload=1 through HyperSpin.

[BadMouth]

The front ends modify the cfg file to substitute the game name for "defualt(sp)" when they launch.

DefaultImage=defualt.cdi in the config file doesn't really mean anything and isn't pointing to a valid cdi.
Demul will crash if autoload=1 and DefaultImage isn't changed to a valid cdi.
If I want to launch demul outside of MALA, I have to change autoload=0 before doing so or it will crash.

The other way to do it would be to specify a default game to load, but it would launch the game when you click on the exe instead of just loading Demul.
Hyperspin will still swap in the game you selected when launching it from the front end.

As far as launching from the front end goes...
If their command line isn't working, my guess would be that it either isn't successfully modifying the cfg file before launching demul
or that it isn't specifying the correct path to the cdi.

The command line for MALA is
-config ImageReader:defaultImage="%path%\%rom%.%ext%" -fullscreen=1