Doomsday 1.13.2 crashes on start

yoginc

I'm using Win vista sp2. It installs okay and I got thru all the initial setup, but when I select 'launch' to play, it crashes with the message 'doomsday.exe has stopped working'. I also get a message in the notification area saying that the DEP (Data Execution Prevention) has intentionally closed doomsday to 'protect the computer'. I tried adding an exception in the DEP settings for snowberry and even turning it off completely using command prompt, but even then it crashes and gives me that message. Can anyone tell me what's going on?

John

If you are using any "addons" you might try disabling all of them and add them back one at a time to see if one of them is the problem.

If you are not using any "addons" but just plain Doomsday then you might consider re-downloading the 1.13.2 to make for sure you did not get a bad download or installation. Make for sure you delete the old installation completely before installing again.

DaniJ

In cases like this it is a good idea to post your doomsday.out (see the notice at the top of this forum).

yoginc

John wrote:

If you are using any "addons" you might try disabling all of them and add them back one at a time to see if one of them is the problem.

If you are not using any "addons" but just plain Doomsday then you might consider re-downloading the 1.13.2 to make for sure you did not get a bad download or installation. Make for sure you delete the old installation completely before installing again.

At first I had the jdoom and jhexen resource packs enabled as addons. But then I uninstalled it, cleared the registry, and did a fresh install with doomsday from another mirror without any addons, but still got the same error.

DaniJ wrote:

In cases like this it is a good idea to post your doomsday.out (see the notice at the top of this forum).

I guess i'll try that, cause it didn't show up any error log, just a message by windows.

yoginc

Ok I opened doomsday.out with notepad and this is what i get, though I'm not sure what it means

Application path: C:\Program Files\Doomsday\Bin\Doomsday.exe
Enabled log entry level: MESSAGE
Created a new 32.0 MB memory volume.
Executable: Doomsday Engine 1.13.2 (Stable 32-bit #1109) Jan 14 2014 08:52:47.
Command line (12 strings):
  0: ..\Bin\Doomsday.exe
  1: -basedir
  2: C:\Program Files\Doomsday/
  3: -sfxchan
  4: 16
  5: -notexcomp
  6: -game
  7: hexen
  8: -iwad
  9: F:\Temp\Doomsday\More WADs\hexen.wad
  10: -userdir
  11: C:\Users\Dell\Documents\Doomsday Frontend\runtime/
RenderSystem: Loading shader definitions from read-only archive entry "data/renderer.pack/
              shaders.dei" at path "/data/doomsday.pk3/data/renderer.pack/shaders.dei"
              (out of archive in read-only native file "(basedir)\data\doomsday.pk3")
Initializing plugins...
  (id:1) dehread
  (id:2) doom
  (id:3) heretic
  (id:4) hexen
  (id:5) wadmapconverter

I'm also posting an image of the message i get in the notification area when it crashes.

Gordon

turn that off that can cause untold amounts of problems i have had similar problems with DEP not just with DDay.

yoginc

Gordon wrote:

turn that off that can cause untold amounts of problems i have had similar problems with DEP not just with DDay.

That's exactly what I did. I tried making an exception in the the DEP control panel for doomsday.exe but it tells me that I cannot turn off DEP for this particular program and that it always has to remain on. I even tried manually shutting of DEP globally using command prompt but to no avail. I don't know how it can cause doomsday to stop working even when its turned off.

DaniJ

I can see no obvious reason from your log as to why its not working.

Is the F: drive a network share perhaps? Have you tried putting your IWADs on the same drive? (it shouldn't matter, though).

What happens if you run doomsday.exe directly?

yoginc

DaniJ wrote:

I can see no obvious reason from your log as to why its not working.

Is the F: drive a network share perhaps? Have you tried putting your IWADs on the same drive? (it shouldn't matter, though).

What happens if you run doomsday.exe directly?

Well no, the F drive is not a network drive. Just a regular data drive. Yes, I did try putting all IWADs in the same drive (although not in the same folder as doomsday) but nothing. Running doomsday.exe directly also gives the same result. I also found it strange that DEP would not include it in the exception list. I've never had this DEP interfering with the running of any other programs ever before this.

DaniJ

Did you perhaps install Doomsday as a user with different privileges to the one you are trying to run it as? I've also never encountered a DEP issue with Doomsday.

Try adding -vv to the command line for extra log verbosity and see if there is any more info about the problem in doomsday.out

Vermil

In the past, IIRC, I've believe I've read comments about the Snowberry launcher causing a crash if the users documents folder isn't on the same drive as it (Snowberry by default overrules the default location for Dday's config files and instead puts them all in ones documents folder).

Obviously, you've said that running Doomsday.exe (i.e bypassing the launcher) also doesn't work. But it might be worth trying an install of Dday to your main drive all the same?

yoginc

DaniJ wrote:

Did you perhaps install Doomsday as a user with different privileges to the one you are trying to run it as? I've also never encountered a DEP issue with Doomsday.

Try adding -vv to the command line for extra log verbosity and see if there is any more info about the problem in doomsday.out

Well I did that and here's the .out. Although don't see much of a difference.

Application path: F:\Games\Doomsday\Bin\Doomsday.exe
Created a new 32.0 MB memory volume.
Folder > 

DirectoryFeed::prune: Pruning "C:\Users\Dell\Documents\Doomsday Frontend\runtime\
                 

              persist.pack": status has changed
Executable: Doomsday Engine 1.14.0 [#1185] 

(Candidate 32-bit) Mar 31 2014 03:34:49
RenderSystem: Loading shader definitions from read-only 

archive entry "data/renderer.pack/
              shaders.dei" [path 

"/data/doomsday.pk3/data/renderer.pack/shaders.dei"]
              from archive in read-only 

"(basedir)\data\doomsday.pk3"

Yeah, this is version 1.14 of doomsday which I though of installing, but it gave me the same results as with 1.13.2

Vermil wrote:

In the past, IIRC, I've believe I've read comments about the Snowberry launcher causing a crash if the users documents folder isn't on the same drive as it (Snowberry by default overrules the default location for Dday's config files and instead puts them all in ones documents folder).

Obviously, you've said that running Doomsday.exe (i.e bypassing the launcher) also doesn't work. But it might be worth trying an install of Dday to your main drive all the same?

Well, I tried that already. My first install of doomsday was on the same drive(OS drive) as my documents. No success in that.

Gordon

i don't know if we can help you with this as your using vista now is there a way to go into safe mode and turn off DEP. if you can great as it seems that vista is not allowing games that are not on it's register aka the games panel. i know that DDay dose not go there at all. so that could be the defining factor also too have you tried running it as admin? aka right clicking and selecting run as administrator.

yoginc

Yup...tried running as admin but to no avail. Is there an earlier version of doomsday I could try? Perhaps that might work.

Gordon

there is but i forgot where it might be.

Vermil

Old stable and unstable versions of Dday can be found here:
http://sourceforge.net/projects/deng/files/

You can also download the last couple of stable releases and unstable releases in-between, from here:
http://www.dengine.net/builds