DRD Team

I recently downloaded the latest version and the game immediatly crashes on startup, heres the crashdump

Any help would be appreciated as ive written over the last version and I'm having to resort to standard Zdoom.

thanks

Hard to tell. Can you give any further information (System specs, output from starting with '+logfile log')?

I can see where it crashes - but not why.

hmm, well this is what i get at the startup after it crashes if this is any help:

adding ./doom.wad (2306 lumps)
I_Init: Setting up machine state.
CPU Speed: 2800.107326 MHz
CPU Vendor ID: GenuineIntel
Name: Intel(R) Pentium(R) 4 CPU 2.80GHz 4 CPU 2.80GHz
Family 15, Model 2, Stepping 9
Features: MMX SSE SSE2
I_InitSound: Initializing FMOD
Setting DirectSound output succeeded
Setting driver 0 succeeded
Initialization succeeded
V_Init: allocate screen.
S_Init: Setting up sound.
ST_Init: Init startup screen.
P_Init: Checking cmd-line parameters...
G_ParseMapInfo: Load map definitions.
S_InitData: Load sound definitions.
LoadDecorations: Load external actors.
R_Init: Init Doom refresh subsystem.
DecalLibrary: Load decals.
M_Init: Init miscellaneous info.
P_Init: Init Playloop state.
D_CheckNetGame: Checking network game status.
player 1 of 1 (1 nodes)
I_InitInput
I_StartupMouse
I_StartupJoystick
I_StartupKeyboard
GL_VENDOR:

could it be something with my graphics card? Im running a GeForce 6600GT AGP4X

I can't say. This looks like the driver isn't returning proper GL identification strings.

damn :S well i thought it might be a driver issue but i got the latest drivers, weird, as version 1.0.22 works and this one doesnt...

grr its really starting to piss me off now!

ive had to downgrade to a 5200 anyway, but i have the latest drivers and the latest GZDoom and its still the same problem! could you have accidently removed vendor ID strings in 0.24? as versions below that work!

please help, I seriously cant be the only one suffering this! and other games work fine. Anyone else out there with an old Gforce experiencing the same problems?

Graf Zahl wrote:This looks like the driver isn't returning proper GL identification strings.

Virtue wrote:Anyone else out there with an old Gforce experiencing the same problems?

Might this be related to this in any way?

I don't think so. The messages look quite different. But it's really hard to tell what is going on here with two computers available that never had any problems with GL initialization.