Snowberry do not launch Doomsday.exe

NemNem
edited 2012 May 12 in Technical Support
Hi,
after not having played doomsday for years, yesterday I've reinstalled the version 1.9.7. All seems to work right, but when I select a game to play nothing happen. Snowberry close and, as I said, nothing happen.
I'm using WinXP SP3 on a quite old PC (the same day I've used Risen3D with no problems).

Here some log files:

conflicts.log
__________________________________
Doomsday Engine Frontend 1.4
Launching on Sat, 12 May 2012 08:05:37
Addons to load:

Resolved addons:
__________________________________

doomsday.out
__________________________________
Executable: Doomsday Engine 1.9.7 [#425] (Stable 32-bit) Feb 29 2012 12:11:04.
Sys_InitWindowManager: Using Win32 window management.
Initializing plugins...
jDoom
jHeretic
jHexen
dpdehread
dpwadmapconverter
Shutting down the console...
__________________________________

options.rsp
__________________________________
-basedir "e:\giochi\Doomsday" -userdir "e:\giochi\Doomsday\snowberry\runtime" -sfxchan 16 -texcomp -wh 640 480 -game doom1-ultimate -iwad "E:\Giochi\Risen3D\Doom.wad" -bpp 32
__________________________________

I've searched in formus for similar problem and I've found a thread with no answers and another thread that give as a solution to use Kickstart2. I've not tested Kickstart2 because I'm not sure that is compatible with the newest version of Doomsday.

I hope that someone can help me to solve my problems

Thank you

Nem

Comments

  • Judging by the Doomsday.out it seems Doomsday.exe is being launched, but shuts down shortly afterwards. Could you add -v to the command line options (in Developer settings) or change the "Verbose messages" to level 1, and post the Doomsday.out again?
  • Thanks for reply,
    this is the new doomsday.out after adding the -v option

    _____________________________
    Executable: Doomsday Engine 1.9.7 [#425] (Stable 32-bit) Feb 29 2012 12:11:04.
    Command line (18 strings):
    0: ..\Bin\Doomsday.exe
    1: -basedir
    2: e:\giochi\Doomsday
    3: -userdir
    4: e:\giochi\Doomsday\snowberry\runtime
    5: -sfxchan
    6: 16
    7: -texcomp
    8: -wh
    9: 640
    10: 480
    11: -game
    12: doom1-ultimate
    13: -iwad
    14: E:\Giochi\Risen3D\Doom.wad
    15: -v
    16: -bpp
    17: 32
    Sys_InitWindowManager: Using Win32 window management.
    Initializing plugins...
    jDoom
    jHeretic
    jHexen
    dpdehread
    dpwadmapconverter
    Shutting down the console...
    _____________________________

    I hope it will help

    Nem
  • Hmm, there isn't any new information there... Could you try again with verbose level 2 to see if anything more is printed?
  • I've tried as you said, but seems that there isn't much more information

    doomsday.out
    ___________________________
    Executable: Doomsday Engine 1.9.7 [#425] (Stable 32-bit) Feb 29 2012 12:11:04.
    Command line (19 strings):
    0: ..\Bin\Doomsday.exe
    1: -basedir
    2: e:\giochi\Doomsday
    3: -userdir
    4: e:\giochi\Doomsday\snowberry\runtime
    5: -sfxchan
    6: 16
    7: -texcomp
    8: -wh
    9: 640
    10: 480
    11: -game
    12: doom1-ultimate
    13: -iwad
    14: E:\Giochi\Risen3D\Doom.wad
    15: -bpp
    16: 32
    17: -v
    18: -v
    Sys_InitWindowManager: Using Win32 window management.
    Initializing plugins...
    jDoom
    jHeretic
    jHexen
    dpdehread
    dpwadmapconverter
    Shutting down the console...
    ___________________________

    Nem
Sign In or Register to comment.