xXSagaiaXx 25 Posted September 13, 2014 Posted September 13, 2014 Has anyone came up with a switch for the nullDC dreamcast emulator?
c0m3r 95 Posted September 13, 2014 Posted September 13, 2014 In MBT I use "-config ImageReader:DefaultImage={PATH}" without the quotes. Works just fine.
xXSagaiaXx 25 Posted September 13, 2014 Author Posted September 13, 2014 Well now I cant get NullDC to work at all. Any luck on setup?
c0m3r 95 Posted September 13, 2014 Posted September 13, 2014 When you say not working what do you mean?
xXSagaiaXx 25 Posted September 13, 2014 Author Posted September 13, 2014 It wont even load a game just from the emu, let alone GB. I think its my pc I need to reboot it cause GB isn't launching any of my games for any systems.
xXSagaiaXx 25 Posted September 14, 2014 Author Posted September 14, 2014 Yeah I just tested and now GB won't launch any games. I need to check the logs.
c0m3r 95 Posted September 14, 2014 Posted September 14, 2014 When you try to launch the game from the emu do you get any error messages? Try a fresh copy of the emu aswell as from experience, nullDC can stop working randomly every so often. You also need to edit the 'nullDC.cfg' as well if you havent already. Emulator.AutoStart needs to be set to 1, Fullscreen set to 1, LoadDefaultImage set to 1 and DefaultImage set to %path%. That along with the command line I gave you should make it work in MBT. If your using classic, change {PATH} to "{rom}".
autoepg 0 Posted September 18, 2014 Posted September 18, 2014 this works for me with nulldc -config ImageReader:DefaultImage="{rom}"
xXSagaiaXx 25 Posted September 18, 2014 Author Posted September 18, 2014 Okay, everything is launching okay again (MBC just needed updating). I'll try the switches later. Thanks, S.
xXSagaiaXx 25 Posted September 19, 2014 Author Posted September 19, 2014 So @@c0m3r I keep keep getting this error message when nullDC tries to start up.
c0m3r 95 Posted September 19, 2014 Posted September 19, 2014 Was that from launching the emulator directly or through media browser? If direct then that is the correct behaviour. The stuff i said to change in the ini will cause that error but should work from mediabrowser.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now