Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
DoomCup

Doom64 TC Crash Problem

Recommended Posts

I have no idea where this goes. There's no troubleshooting or anything at the website for the thing, so I thought I'd ask here.

I just dl'd the Doom64 TC thing and installed it, put all the files in their proper places. When I ran it, the console showed and the screen went black as the program started.

Then the desktop.

I tried with OpenGl. Not only do I get dumped to the desktop, but I get stuck in the 640x480 resolution.

What do I do?

Share this post


Link to post

Post Systemspecs.
Mine runs fine on my Pc with a Gforce.
Tried it on an old Celeron500 with Sis6xx chipset and it crashed - gfx driver-issue.

Share this post


Link to post

I run a computer with NVidia GeForce 6800 XT.

I also have 2.11 ghz dual core, 2gb Ram.

I also just installed the latest drivers.

Share this post


Link to post

Here's the output file:

Con_Init: Initializing the console.
SW_Init: Startup message window opened.
Executable: Version 1.1.05 Dec 7 2003 (DGL).
Z_Init: Init zone memory allocation daemon.
32.0 Mb allocated for zone.
Parsing configuration files.
W_Init: Init WADfiles.
W_AddFile: Data\doom64\Auto\DOOM2.WAD
IWAD identification: 00f36acb
W_AddFile: Data\D64data.wad
W_AddFile: Data\doom64\doom64_abstin.wad
W_AddFile: Data\doom64\doom64_abstin.gwa
W_AddFile: Data\doom64\Auto\D64_data.pk3
W_AddFile: Data\doom64\Auto\D64_data2.pk3
Reading definition file: Defs\Doomsday.ded
Reading definition file: Defs\doom64\doom64.ded
156 sprite names
1334 states
234 things
85 lights
116 sound effects
68 songs
352 text strings
22 particle generators
4 detail textures
40 map infos
15 finales
1610 line types
189 sector types
Sys_Init: Setting up machine state.
Sys_Init: Initializing keyboard, mouse and joystick.
I_InitJoystick: GGE909 PC Recoil Pad
Sys_InitTimer.
Sys_InitMixer: Realtek HD Audio output
Sfx_Init: Initializing DirectSound...
DS_DSoundInit: EAX initialized.
DS_EAXSetdw (prop:11 value:2) failed. Result: 80004001.
DS_EAXSetdw (prop:2 value:-10000) failed. Result: 80004001.
DS_EAXSetf (prop:5 value:0.372500) failed. Result: 80004001.
DS_EAXSetdw (prop:3 value:0) failed. Result: 80004001.
DS_EAXSetf (prop:4 value:1.300000) failed. Result: 80004001.
DM_WinMusInit: 1 MIDI-Out devices present.
DM_WinMusInit: MIDI initialized.
S_Init: OK.
R_Init: Init the refresh daemon.
R_InitModels: Initializing MD2 models.
R_InitModels: Done in 0.00 seconds.
Net_InitGame: Initializing game data.
GL_Init: Initializing Doomsday Graphics Library.
DG_Init: Direct3D 8.1.
Direct3D information:
Driver: nv4_disp.dll
Description: NVIDIA GeForce 6800 XT
Texture units: 2
Texture blending stages: 8
Modulate2X: OK
MultiplyAdd: OK
BlendFactorAlpha: OK
Maximum texture size: 4096 x 4096
Maximum texture aspect ratio: 1:4096
Maximum anisotropy: 16
Multitexturing enabled (full).

That's as far as it gets.

Share this post


Link to post

Doomcup, have you tried an older gfx-driver?
How can I redirect the startup-info into a file?
I furthermore tried running Doom64 on an
P450 + RivaTnt - works.
P450 + GforceMx - works.

Quite a puzzle...

Share this post


Link to post

DoomCup's out file says "32.0 Mb allocated for zone"?


You might need to allocate more memory ("-maxzone XXXm" or "-mem XXXm" anything from 1-256). You may not even be able to start Doom64TC with such a small ammount as 32mb.

Thankfully the 1.9 beta series of Dday has done away with memory limits (it will use as much as your system has) and having to set the availible memory at start up.

Doom64TC also appears to have some problems running on newer hardware (it is based on a version of Dday that is about 4 years old).

_bruce_ said:
How can I redirect the startup-info into a file?


Have a look for a .out file in the Doom64TC folder (I know it's called "Doomsday.out" in Doomsday, but the Doom64TC might have changed the name)

Share this post


Link to post

Thanks.
Ok, looked through it - everything's the same as Doomcups startup, besides the gfx cards name.

I have no clue.

Share this post


Link to post

Tried the memory thing. Still nothing. I don't get what's wrong with it...

I've tried everything I could think of. Any more ideas?

Wait, could it have something to do with the doom 2 wad I used?

Share this post


Link to post
DoomCup said:

Tried the memory thing. Still nothing. I don't get what's wrong with it...

I've tried everything I could think of. Any more ideas?

Wait, could it have something to do with the doom 2 wad I used?


Unlikely, but possible....hey...

...wait...

....if you "cheaply" downloaded the Doom2.wad you'll go to HELL ;-)

Share this post


Link to post

I have the same problem with a radeon x850, which is a shame since i missed it the first time around.

_bruce_ said:

Unlikely, but possible....hey...

...wait...

....if you "cheaply" downloaded the Doom2.wad you'll go to HELL ;-)


I had a doom2.wad that ive used for years which at some point xwe/nwt had modified only slightly and doomsday comments on it, now that i dug up my doom2 cd and got the original wad of it doomsday dosent moan but doom64 dosent load still. Must just be gfx drivers/ directx issues.

Any chance of an update?

Share this post


Link to post

Pffff.... this is pretty tough.
Only things I can think of are global driver settings...
Anisotropy, VSync, TrippleBuffer, one or two display setup, maybe some of these settings fuck it up?

Share this post


Link to post

I had the same problem as the OP and after playing around with it for about a week I think I finally discovered what is wrong. This seems really stupid, but apparently the executable doesn't like path names that contain spaces. When I moved my installation from "Program Files" to another directory that doesn't have spaces in its name everything seemed to work fine. I wish that they would fix this, as I like to keep my Doom files together, but this seems like a fix for anyone with this problem. This is strange because plain Doomsday doesn't seem to have this issue.

Share this post


Link to post
Liberation said:

well this is how i have mine installed/ C:\doom64\Absolution\Bin theres no spaces there and it still dosent work.


I must apologize, for it seems that I was too hasty in my conclusion. I can get it to run in a directory with spaces, but for some reason it always crashes when I try to put it in the original directory that I had it in (I tried reinstalling several times too).

When I tried moving my installation to different directories, I noticed that it consistently worked in some, but consistently crashed in others. When I first tested it, the installations that crashed had, by coincidence, spaces in their paths, so I made the assumption that that had something to do with it, especially since it is a common problem in some programs (usually older ones, though). Further testing, however, indicates that I was wrong.

It seems that the Absolution source code is available, so maybe I can dig through that later to try to find the problem.

Share this post


Link to post

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×