Signal Posted September 5, 2004 I downloaded the latest version of Doom64 and put the doom2.wad into the Bin\Data\doom64\Auto directory. When i try to open absolution.exe, it starts and loads everything up, but then it just closes the window and comes back to the desktop. I'm using Windows XP, and the game is suppose to be XP-compatible, right? I tried running the game in all of the compatibility modes, but it didn't work. Any help? 0 Share this post Link to post
Bashe Posted September 5, 2004 Remember that the Absolution is a stand-alone mod. It shouldn't be in the Jdoom directory. It should have it's own. Other than that, I don't know what the problem could be. 0 Share this post Link to post
Nmn Posted September 5, 2004 Do You have the latest drivers for Your video Card? 0 Share this post Link to post
Signal Posted September 5, 2004 Yep, it's in it's own directory (tho at one point i did try to run it in Doomsday/Jdoom). Hmm, i'll update my drivers, and then check it out and report if it didn't work (I'm using Geforce4 MX). EDIT: Nope, didn't work. I wonder what's wrong... I wonder if i could make it run perfectly under the Doomsday Kickstart (since this would probably make it work). I tried adding the doom64_abstin.wad -file from Bin\Data\doom64 into Doom2 wads in the Kickstart. It did start the game, but the graphics seemed all screwed up and there were some weird Doom2 interferences, such as Doom2 music and Doom2 sprites mixed with Doom64 sprites. 0 Share this post Link to post
Nmn Posted September 5, 2004 Never Use Kickstart. That's number one rule, second is put Absolution in it's own folder. Run Absolution.exe, that's it, no fooling around with Kickstarts. There are also batch files in the Bin folder, maybe try some of them? If You could post the error message (dumped into the log) here we may be able to find a proper solution. 0 Share this post Link to post
Signal Posted September 5, 2004 I'm saying this again, it's in it's own folder. I only tried running it in Kickstart after i found out it doesn't work. The opengl batch-file gives me a Windows error (the one with the error reporting and stuff), maxzone192.bat does the same as the exe-file. What log do you mean? I can't seem to find it... EDIT: Nevermind, i found the logfile. There seems to be some errors: 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. 0 Share this post Link to post
Kaiser Posted September 5, 2004 Simple. Disable Eax. use command line parameter -noeax Kinda forgot exactly the command was, so check Doomsday/Jdoom's docs (at doomsday's site) and make sure. 0 Share this post Link to post
Signal Posted September 5, 2004 Damn! It didn't work... :( Here's the complete log: 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: 00f8ccf8 W_AddFile: Data\D64data.wad W_AddFile: Data\doom64\doom64_abstin.wad W_AddFile: Data\doom64\doom64_abstin.gwa W_AddFile: Data\doom64\Auto\d64mus.wad 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. Sys_InitTimer. Sys_InitMixer: kX Wave CT4832 10k1 [9000] 0/1 Sfx_Init: Initializing DirectSound... DM_WinMusInit: 5 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 GeForce4 MX 440SE with AGP8X Texture units: 2 Texture blending stages: 8 Modulate2X: OK MultiplyAdd: OK BlendFactorAlpha: OK Maximum texture size: 2048 x 2048 Maximum texture aspect ratio: 1:2048 Maximum anisotropy: 2 Multitexturing enabled (full). 0 Share this post Link to post
Kaiser Posted September 6, 2004 hmm..try updating your direct x drivers. I see no error messages in that log.. 0 Share this post Link to post
Signal Posted September 20, 2004 I just updated my DirectX and installed doom2.wad from my friend's Doom2 -95 Edition, but it's not working. Here's my computer specs just in case: Intel Celeron 2.20 GHz 512 RAM Windows XP 0 Share this post Link to post
Nmn Posted September 20, 2004 Post the log so we can see what can be done. 0 Share this post Link to post
Pika132 Posted September 20, 2004 AFAIK the DOOM2.WAD needs to be in the /bin folder. 0 Share this post Link to post
Nmn Posted September 20, 2004 Correction. \bin\data\doom64\auto\doom2.wad 0 Share this post Link to post