Please report all (suspected) bugs related to the GAME here.

Make sure to also include your system specs as follows:

CPU
GPU (+used driver version)
RAM
Soundcard
OS
Overclocked anything - if yes, what if no then post: O/C no
Any special cvar settings you've made
FSAA - if yes, which setting

Server browser bug

I've noticed the ingame server browser has a few problems when attempting to sort or filter the list in any way, and actually misreports selected servers. If the server browser is left alone, each listed server is correct - but attempting to resort that list in any way, causes your client to connect to the wrong server.

For instance, I sort the servers by ping and attempt to join a local server with no players and an 80ms ping - I end up joining a server halfway across the world with players already in it, and an astronomical ping time.

This doesn't seem to be related to configuration or specific hardware settings, as I've seen this issue manifest on a wide number of systems. I suspect that it effects everyone, and have gotten lots of complaints about lag when on Australian servers by Americans who attempted to join more local servers. But for reference's sake, here's my specs:

CPU: Pentium 4 3GHz, 800FSB (Northwood).
MOBO: ASUS P4P800 Deluxe, 865PE chipset.
GPU: Sapphire branded Radeon 9800XT, 256MB model plus Catalyst 4.7's and beta 4.9's.
RAM: 1024MB (2x512MB) DDR400 Kingmax.
Sound: Creative Audigy 2 ZS Platinum Pro.
OS: Windows XP Pro SP1, up to date.

No overclockings. No real CVAR modifications. No FSAA used.

There's also the Snow bug? that may be a driver/overclocking issue, or whatever.
Here's a screenie of the problem:

Read this thread to find out more on that one:
http://www.doom3world.org/phpbb2/viewtopic.php?t=2851

eskimo roll wrote:

There's also the Snow bug? that may be a driver/overclocking issue, or whatever.

That looks like a video card problem. It can come from overclocking or overheating, but can also be a hardware fault with the card/chipset itself.

I have an issue which I originally reported as snow, but not like the screenshot above - it's more like static. Others are seeing this also, and from the limited knowledge about the issue, it appears at this stage to be an issue with the ATI OpenGL driver on certain cards.

ATI Radeon 9800 Pro (128Meg - currently using Cat 4.7 but tired many others, including Omega 2.5.88)
2.8GHz Pentium IV
1Gig DDR400 RAM
200Gig SATA Hard Drive
Gigabyte Motherboard (GA-8I series of some sort)
Windows XP SP1

Quote:

Basically, "use" in the PDA GUI is bound to "fire" instead of defaulting to the L-mouse button. Which is stupid and awkward, but not a game-breaker.

In other words, to click on something on the PDA screen, I have to move the mouse pointer to the right place, and then hit my "fire" key (which is "E" on the keyboard). In order to scroll through a PDA email, I need to hold down fire/E while moving the mouse.

They should have just had *all* mouse behavior revert to normal while using the PDA, but probably didn't anticipate/test with an unusual config. Bleh.

Thanks pjw for reporting this!

sizeDown command sizes viewport down, and moves it to the left lower corner, while it should be centered. This is obvious a bug.

Im using a:

ati radeon 9700 mobility 128 mb
512mb ram
sigmatel audio driver
2.8 ghz
windows xp
no overclocking
the only thing i tried was changing the cachemeg from 20 to 64 but i only got slightly longer gameplay (5-10 mins.)

constantly locking up at random points during gameplay.
i tried my standard drivers as well as the beta catalyst driver to no avail.
please HELP!!!

Link to Activision support page for Doom3

Link

_shank wrote:

Link to Activison support for Doom3

Should we consider that as a bug?
:lol:

BNA! wrote:

_shank wrote:

Link to Activison support for Doom3

Should we consider that as a bug?
:lol:

its away to resolve the bug's (bbcode is so picky...took me some time to get the link made)

Quote:

ok, the fix to enable 5.1 sound is to change the settings in the control panel. But what does that mean? Do I now every time I want to watch a dvd go back to 7.1 (I guess so)? Or should this setting even be 5.1 for 5.1 movies? Shouldn't Doom3 accept 7.1 as a setting and switch to 5.1 internally (if yes, a fix please, id!). I don't mind that my centre back speaker is mute for Doom3, but I like to still watch my 6.1 dvds in 6.1, without changing the setting all the time!!!

Thanks fergusdog for reporting this in!

i killed an IMP in a doorway and i don't remember if the door just opened or not but the imp got stuck and was spinning rapidly before it melted. kinda wierd seems a bug in the physics code.

On my video card (PNY Geforce 4 4200) the game was olmost pitch black at default settings, all i could see was lighting flares and GUI's. after changing the r_renderer to NV10 it went away (it was using a default NV20 path).
Intel 2.5ghz on Intel D865PERL
Audigy2
1gb ram
WinXP SP1.

I can open the game and play for five minutes at most, but then it closes and goes back to windows with no error or anything. All drivers are the most up to date from manufacturer's website and windows display settings match those in the game. I've tried everything. Help!!!

System:
CPU - Athalon XP 2200+ 1.8Ghz
GPU - NVidia GeForce3 Ti 200 Driver = v62.11
RAM - 512 MB DDR
Sound Card - Vinyl AC'97
O/C no

The game installed without a problem, and seemed to be fine when it first started (id intro was perfect)... then, when the next screens came up all the graphics turned into a garbled mess! The cursor, text, and other images come and go and I can't see what I'm doing at all. I've read through other posts that mention anything about weird graphics and done whatever they suggested for those (updated all drivers, etc.) and no matter what, I still have the same garbled graphics.

I also thought that maybe if I got past the setup screens, the game might be okay... nope, the same thing happens even when I start a new game.

Please help, I'd like to at least play the game~
dhughes

btw.. i ran dxdiag.. and it didn't show anything was wrong.
no overclocking either~

win xp sp1
2.8 ghz
512 ram
ati 9700 pro 4.7
sblive 5.1

http://img.photobucket.com/albums/v431/ ... aphics.jpg

!!!Just wanted to post the outcome... turns out my Dell video card, was defective from the beginning. I saw little signs (and didn't recognize them as such) from day one, but because the programs I normally run didn't seem affected, I didn't question the occasional "artifacting"~ After weeks of trying A to Z to "fix" the graphics for Doom 3~ I switched cards, first with an identical ATI 9700 pro 128 (this one purchased from retail store) ... results.. no problems, no artifacts... then, I put my OLD Nvidia Ti 500 in, with the same results (although a bit slower), no artifacts.

So, I can now play Doom 3~ and will NOT BE purchasing any more systems from Dell.com!

Thanks for everyones input...
dhughes

Doom3 crashes after the cut scenes if they are allowed to play to completion, completely freezing the computer and requiring a hard reboot (removing the battery on the laptop). It also runs choppy prior to this point.

The laptop is a dell (i'm sorry i don't have the make and model currently as it isn't mine, i will edit it in when i can to add more information).

Processor: Pentium 3.4 EE (i believe)
Ram: at least 1gb
Video Card: Radeon 9700 128mb
Sound: unsure
OS: WinXP home

Nothing has been overclocked unless it shipped that way. We have attempted loading all the newest drivers (mb, sound, ati) to ensure that is not the problem. We are also going to try the other recommendations from the activsion help site, and if any solution is found i'll edit and post here. Any help is required (my father is dying to play this and won't be home to his home pc till next week).

Feffer wrote:

Processor: Pentium 3.4 EE (i believe)

On a laptop? I don't think so.

Ok multiplayer has stopped working entirely for me. Whenever I click to join a server and it connect, Doom 3 shuts down. However, I can create servers with no problem. What's even stranger is that it was working fine before, and now it has died. I have made no multiplayer or networking modifications to the DoomConfig.

Another bug. When using com_allowConsole 1 and -nointro, the main menu doesn't load, only the console shows up and it takes up the entire screen. However, when you type com_allowConsole 0 into the console, the main menu loads, and you can use Doom 3 like normal.

My system:

Gf Ti4200 64MB
AMD 2600+
512Mt RAM

The problem: The game seems to use rasterized lighting, smoke and shadow effects like the game wouldn't be in 32-bit mode. The game looks just fine and smooth in my friends computer that has Radeon 9700.

I have crashes which happen at the same points in the game every single time. For example, in mars_city2, I step up to one particular door and it hangs; in the next level after that, there's a cutscene when you walk out of the elevator and the camera flies through an airvent and shows the bald guy w/ sunglasses talking to someone else, well the game hangs every single time when the bald heads come into the frame... wierdness...

I've been loading some maps using the console and when I finish the particular part of a map and it's time to go to the next part, I keep a console error unable to find "current map name".proc This has happened to me with three different maps. Does anyone have any idea as to what's happening here?

mac53 wrote:

Here's what I think it is. 1.3.1. has been built with the 64 bit vista in mind and it's dumb-founded when ran on a 32 bit os. Doom 3 was built for 32 bits and so was all the patches up to 1.3.1. It's appearing to me, that it's a case of 'either, or'... not 'both' when it comes to software, especially in this case. Personally, I think that 1.3.1. is a beta and hasn't been tested properly. I'm not a pro here, nor do I claim to be a 'puter wiz', but there are times where it doesn't take a 'rocket scientist' to see what's going on, just one to explain it! I want to help with this and I'll do my best.

To the best of my knowledge the Vista changes were related to detecting whether a OpenGL ICD is installed. If not you should get a warning relating to performance if you're using the Vista OpenGL wrapper without driver support. Can't be 100% on that as I never tried on Vista without an ICD. I linked to it before, but Timothee Besset's plan has the full release info...

http://www.bluesnews.com/plans/476/

Doom 3 is still 32-bit (Vista still comes as both, don't forget). As for testing it did have a full QA pass. I used each of the test releases with no problems from early Dec 2006 until it was released in Feb 2007. I played the RoE expansion pack right through just in case.

The Mac developers Aspyr did an independent QA test of their build.

We've been running the patch on our servers since release with no problems. My mod server has had nearly 400 individual players connect to it since it was upgraded to 1.3.1.

Now, I don't deny that you and vinnie_jones do have some sort of problem but you're the only two people I've heard from that could not get 1.3.1 running.

I think it is also useful to clear up some terminology. A "crash" is when the game does something unexpected and can't recover from it. Like simply dropping back to the desktop or giving you one of those error boxes like you have seen.

Other problems, such as the DLL API message, are not "crashes" but are genuine error conditions that the game has detected and reported to you (a mod built for a different release in this case).

One thing you could try is to do disable EAX/OpenAL. I've had one player recently whose D3 would crash on startup when these were enabled.

You can do this by editing DoomConfig.cfg and making sure the appropriate values are set to zero.

seta s_useEAXReverb "0"
seta s_useOpenAL "0"

Sim

simulation wrote:

Now, I don't deny that you and vinnie_jones do have some sort of problem but you're the only two people I've heard from that could not get 1.3.1 running.

Thank you for the correction in a professional manner. You are correct, I used the wrong term. "Freezes" explains it exactly.

rich_is_bored wrote:

Unfortunately, those dialogs are worthless. I couldn't begin to tell you what the problem is.

Agreed that in general they're not too helpful. However you can sometimes get some info from them. If you click the "click here" link, you'll get another dialog which shows some basic information about the crash. Significantly, it shows the module, which can sometimes point you at the problem (eg if its "nvogl.dll" then its probably an nVidia OpenGL issue).

If its in gamex86.dll, and you're running a mod, the mod author may be able to use the "faulting address" to tell you something about the crash.

Also while its open, depending on how your Windows is configured there might be a .mdmp file hanging around in your temp directory associated with this crash, which might be helpful to a programmer to trace the issue. It'll probably get deleted as you close the dialog though.

simulation wrote:

To the best of my knowledge the Vista changes were related to detecting whether a OpenGL ICD is installed. If not you should get a warning relating to performance if you're using the Vista OpenGL wrapper without driver support. Can't be 100% on that as I never tried on Vista without an ICD. I linked to it before, but Timothee Besset's plan has the full release info...

http://www.bluesnews.com/plans/476/

Doom 3 is still 32-bit (Vista still comes as both, don't forget). As for testing it did have a full QA pass. I used each of the test releases with no problems from early Dec 2006 until it was released in Feb 2007. I played the RoE expansion pack right through just in case.

The link you posted here, takes you to the version that I was using, and causing the posted issues.

mac53 wrote:

simulation wrote:

To the best of my knowledge the Vista changes were related to detecting whether a OpenGL ICD is installed. If not you should get a warning relating to performance if you're using the Vista OpenGL wrapper without driver support. Can't be 100% on that as I never tried on Vista without an ICD. I linked to it before, but Timothee Besset's plan has the full release info...

http://www.bluesnews.com/plans/476/

Doom 3 is still 32-bit (Vista still comes as both, don't forget). As for testing it did have a full QA pass. I used each of the test releases with no problems from early Dec 2006 until it was released in Feb 2007. I played the RoE expansion pack right through just in case.

The link you posted here, takes you to the version that I was using, and causing the posted issues.

Yes, I realise that. I was linking so you could read the info about the release straight from the developer who created it.

@simulation

Thank you, [for me] reading that garble doesn't help me any... I wish it does.

hehe im not at all surprised im one of the few (?)
people who has problems with the new patch, i had the same
bs with the 1.32 patch for far cry (altho THAT patch was so flawed
crytec or whatever theyre called actually withdrew it),
i also had serious issues with that MoH box (dont rememebr the name but it had 4 cd-s in it) but i googled that and many had issues with that
as well, sometimes i just wanna take the comp and chuck it
through the window and just "retire" to some console

For the time being, if not forever, im sticking with the 1.3 patch

Could anyone tell me why when I go to activate the EAX in the sound options menu, it freezes my system? I have the Audigy 2 zs Platinum SB sound card with ALL the updated bells and whistles. EAX console, DTS, the whole nine yards. There's no logical reason why this option should freeze my system. I saw an eax update for doom3, but there's no way I'm going to uninstall my current Creative software and drivers to install this crap. There has to be some way to activate this feature, I have this option in my current software. :evil:

The cvar for enabling EAX is s_useEAXReverb. You could try adding...

Code:

s_useEAXReverb 1

... to DoomConfig.cfg

I did and it froze Doom 3 while I tried to apply the setting within the menu and entering the attribute within the cfg file gives me this. Doom 3 doesn't even load...

Issue resolved thanks to Doomworld. This is an issue pertaining just to Creative "Soundblaster" Audigy series cards. If you using Creative and want the EAX reverb and are not able to get it to function, then here is a link that will answer many questions pertaining to this.

http://forums.creative.com/creative...id=soundblaster

There's also a software that installs the proper API to make Doom 3's EAX HD reverb functional. If I get enough requests, I can upload this API software and post the link to it here.

EAX issue resolved.

Hi, im new to this forum...

I builded a new pc and these are the specs:

CPU: AMD phenom 9850 2.5Ghz
Memory: Corsair XMS2 DDR2 800Mhz
Video: 2x EVGA 9800GT in SLI mode
Motherboard: Asus M3N-HT Deluxe
HDD: Western Digital Caviar 250GB

When i play doom 3, i get to play for about a minute or two, and then my PC shuts down completely... i need to power it on and then wait till it shows some video, sometimes i need to reset it 2 or 3 times because it doesnt show any video at all...

I think i have a Drivers issue, but i want to know how can i fix it... please help...

It abruptly powers off? That sounds like a hardware issue. How long have you had this new PC? A few days?

I have problems with the display. All characters appear to be half in light and half in shadow.

Here's a screenshot of what it looks like:

My system:
CPU: Intel Core 2 Duo 2.80 GHZ
RAM: 4 GB DDR2
GPU: Intel G41 Express Chipset (driver version 8.15.10.2555)
Sound card: Realtek HD audio
OS: Windows 7 Ultimate x64 bit SP1
No overclock

Not a fan of integrated video cards, but I guess that your problem is caused by video drivers.

Check for updates.

I've been loading some maps using the console and when I finish the particular part of a map and it's time to go to the next part, I keep a console error unable to find "current map name".proc This has happened to me with three different maps. Does anyone have any idea as to what's happening here?

mac53 wrote:

Here's what I think it is. 1.3.1. has been built with the 64 bit vista in mind and it's dumb-founded when ran on a 32 bit os. Doom 3 was built for 32 bits and so was all the patches up to 1.3.1. It's appearing to me, that it's a case of 'either, or'... not 'both' when it comes to software, especially in this case. Personally, I think that 1.3.1. is a beta and hasn't been tested properly. I'm not a pro here, nor do I claim to be a 'puter wiz', but there are times where it doesn't take a 'rocket scientist' to see what's going on, just one to explain it! I want to help with this and I'll do my best.

To the best of my knowledge the Vista changes were related to detecting whether a OpenGL ICD is installed. If not you should get a warning relating to performance if you're using the Vista OpenGL wrapper without driver support. Can't be 100% on that as I never tried on Vista without an ICD. I linked to it before, but Timothee Besset's plan has the full release info...

http://www.bluesnews.com/plans/476/

Doom 3 is still 32-bit (Vista still comes as both, don't forget). As for testing it did have a full QA pass. I used each of the test releases with no problems from early Dec 2006 until it was released in Feb 2007. I played the RoE expansion pack right through just in case.

The Mac developers Aspyr did an independent QA test of their build.

We've been running the patch on our servers since release with no problems. My mod server has had nearly 400 individual players connect to it since it was upgraded to 1.3.1.

Now, I don't deny that you and vinnie_jones do have some sort of problem but you're the only two people I've heard from that could not get 1.3.1 running.

I think it is also useful to clear up some terminology. A "crash" is when the game does something unexpected and can't recover from it. Like simply dropping back to the desktop or giving you one of those error boxes like you have seen.

Other problems, such as the DLL API message, are not "crashes" but are genuine error conditions that the game has detected and reported to you (a mod built for a different release in this case).

One thing you could try is to do disable EAX/OpenAL. I've had one player recently whose D3 would crash on startup when these were enabled.

You can do this by editing DoomConfig.cfg and making sure the appropriate values are set to zero.

seta s_useEAXReverb "0"
seta s_useOpenAL "0"

Sim

simulation wrote:

Now, I don't deny that you and vinnie_jones do have some sort of problem but you're the only two people I've heard from that could not get 1.3.1 running.

Thank you for the correction in a professional manner. You are correct, I used the wrong term. "Freezes" explains it exactly.

rich_is_bored wrote:

Unfortunately, those dialogs are worthless. I couldn't begin to tell you what the problem is.

Agreed that in general they're not too helpful. However you can sometimes get some info from them. If you click the "click here" link, you'll get another dialog which shows some basic information about the crash. Significantly, it shows the module, which can sometimes point you at the problem (eg if its "nvogl.dll" then its probably an nVidia OpenGL issue).

If its in gamex86.dll, and you're running a mod, the mod author may be able to use the "faulting address" to tell you something about the crash.

Also while its open, depending on how your Windows is configured there might be a .mdmp file hanging around in your temp directory associated with this crash, which might be helpful to a programmer to trace the issue. It'll probably get deleted as you close the dialog though.

simulation wrote:

To the best of my knowledge the Vista changes were related to detecting whether a OpenGL ICD is installed. If not you should get a warning relating to performance if you're using the Vista OpenGL wrapper without driver support. Can't be 100% on that as I never tried on Vista without an ICD. I linked to it before, but Timothee Besset's plan has the full release info...

http://www.bluesnews.com/plans/476/

Doom 3 is still 32-bit (Vista still comes as both, don't forget). As for testing it did have a full QA pass. I used each of the test releases with no problems from early Dec 2006 until it was released in Feb 2007. I played the RoE expansion pack right through just in case.

The link you posted here, takes you to the version that I was using, and causing the posted issues.

mac53 wrote:

simulation wrote:

To the best of my knowledge the Vista changes were related to detecting whether a OpenGL ICD is installed. If not you should get a warning relating to performance if you're using the Vista OpenGL wrapper without driver support. Can't be 100% on that as I never tried on Vista without an ICD. I linked to it before, but Timothee Besset's plan has the full release info...

http://www.bluesnews.com/plans/476/

Doom 3 is still 32-bit (Vista still comes as both, don't forget). As for testing it did have a full QA pass. I used each of the test releases with no problems from early Dec 2006 until it was released in Feb 2007. I played the RoE expansion pack right through just in case.

The link you posted here, takes you to the version that I was using, and causing the posted issues.

Yes, I realise that. I was linking so you could read the info about the release straight from the developer who created it.

@simulation

Thank you, [for me] reading that garble doesn't help me any... I wish it does.

hehe im not at all surprised im one of the few (?)
people who has problems with the new patch, i had the same
bs with the 1.32 patch for far cry (altho THAT patch was so flawed
crytec or whatever theyre called actually withdrew it),
i also had serious issues with that MoH box (dont rememebr the name but it had 4 cd-s in it) but i googled that and many had issues with that
as well, sometimes i just wanna take the comp and chuck it
through the window and just "retire" to some console

For the time being, if not forever, im sticking with the 1.3 patch

Could anyone tell me why when I go to activate the EAX in the sound options menu, it freezes my system? I have the Audigy 2 zs Platinum SB sound card with ALL the updated bells and whistles. EAX console, DTS, the whole nine yards. There's no logical reason why this option should freeze my system. I saw an eax update for doom3, but there's no way I'm going to uninstall my current Creative software and drivers to install this crap. There has to be some way to activate this feature, I have this option in my current software. :evil:

The cvar for enabling EAX is s_useEAXReverb. You could try adding...

Code:

s_useEAXReverb 1

... to DoomConfig.cfg

I did and it froze Doom 3 while I tried to apply the setting within the menu and entering the attribute within the cfg file gives me this. Doom 3 doesn't even load...

Issue resolved thanks to Doomworld. This is an issue pertaining just to Creative "Soundblaster" Audigy series cards. If you using Creative and want the EAX reverb and are not able to get it to function, then here is a link that will answer many questions pertaining to this.

http://forums.creative.com/creative...id=soundblaster

There's also a software that installs the proper API to make Doom 3's EAX HD reverb functional. If I get enough requests, I can upload this API software and post the link to it here.

EAX issue resolved.

Hi, im new to this forum...

I builded a new pc and these are the specs:

CPU: AMD phenom 9850 2.5Ghz
Memory: Corsair XMS2 DDR2 800Mhz
Video: 2x EVGA 9800GT in SLI mode
Motherboard: Asus M3N-HT Deluxe
HDD: Western Digital Caviar 250GB

When i play doom 3, i get to play for about a minute or two, and then my PC shuts down completely... i need to power it on and then wait till it shows some video, sometimes i need to reset it 2 or 3 times because it doesnt show any video at all...

I think i have a Drivers issue, but i want to know how can i fix it... please help...

It abruptly powers off? That sounds like a hardware issue. How long have you had this new PC? A few days?

Please report all (suspected) bugs related to the GAME here.

Make sure to also include your system specs as follows:

CPU
GPU (+used driver version)
RAM
Soundcard
OS
Overclocked anything - if yes, what if no then post: O/C no
Any special cvar settings you've made
FSAA - if yes, which setting

Server browser bug

I've noticed the ingame server browser has a few problems when attempting to sort or filter the list in any way, and actually misreports selected servers. If the server browser is left alone, each listed server is correct - but attempting to resort that list in any way, causes your client to connect to the wrong server.

For instance, I sort the servers by ping and attempt to join a local server with no players and an 80ms ping - I end up joining a server halfway across the world with players already in it, and an astronomical ping time.

This doesn't seem to be related to configuration or specific hardware settings, as I've seen this issue manifest on a wide number of systems. I suspect that it effects everyone, and have gotten lots of complaints about lag when on Australian servers by Americans who attempted to join more local servers. But for reference's sake, here's my specs:

CPU: Pentium 4 3GHz, 800FSB (Northwood).
MOBO: ASUS P4P800 Deluxe, 865PE chipset.
GPU: Sapphire branded Radeon 9800XT, 256MB model plus Catalyst 4.7's and beta 4.9's.
RAM: 1024MB (2x512MB) DDR400 Kingmax.
Sound: Creative Audigy 2 ZS Platinum Pro.
OS: Windows XP Pro SP1, up to date.

No overclockings. No real CVAR modifications. No FSAA used.

There's also the Snow bug? that may be a driver/overclocking issue, or whatever.
Here's a screenie of the problem:

Read this thread to find out more on that one:
http://www.doom3world.org/phpbb2/viewtopic.php?t=2851

eskimo roll wrote:

There's also the Snow bug? that may be a driver/overclocking issue, or whatever.

That looks like a video card problem. It can come from overclocking or overheating, but can also be a hardware fault with the card/chipset itself.

I have an issue which I originally reported as snow, but not like the screenshot above - it's more like static. Others are seeing this also, and from the limited knowledge about the issue, it appears at this stage to be an issue with the ATI OpenGL driver on certain cards.

ATI Radeon 9800 Pro (128Meg - currently using Cat 4.7 but tired many others, including Omega 2.5.88)
2.8GHz Pentium IV
1Gig DDR400 RAM
200Gig SATA Hard Drive
Gigabyte Motherboard (GA-8I series of some sort)
Windows XP SP1

Quote:

Basically, "use" in the PDA GUI is bound to "fire" instead of defaulting to the L-mouse button. Which is stupid and awkward, but not a game-breaker.

In other words, to click on something on the PDA screen, I have to move the mouse pointer to the right place, and then hit my "fire" key (which is "E" on the keyboard). In order to scroll through a PDA email, I need to hold down fire/E while moving the mouse.

They should have just had *all* mouse behavior revert to normal while using the PDA, but probably didn't anticipate/test with an unusual config. Bleh.

Thanks pjw for reporting this!

sizeDown command sizes viewport down, and moves it to the left lower corner, while it should be centered. This is obvious a bug.

Im using a:

ati radeon 9700 mobility 128 mb
512mb ram
sigmatel audio driver
2.8 ghz
windows xp
no overclocking
the only thing i tried was changing the cachemeg from 20 to 64 but i only got slightly longer gameplay (5-10 mins.)

constantly locking up at random points during gameplay.
i tried my standard drivers as well as the beta catalyst driver to no avail.
please HELP!!!

Link to Activision support page for Doom3

Link

_shank wrote:

Link to Activison support for Doom3

Should we consider that as a bug?
:lol:

BNA! wrote:

_shank wrote:

Link to Activison support for Doom3

Should we consider that as a bug?
:lol:

its away to resolve the bug's (bbcode is so picky...took me some time to get the link made)

Quote:

ok, the fix to enable 5.1 sound is to change the settings in the control panel. But what does that mean? Do I now every time I want to watch a dvd go back to 7.1 (I guess so)? Or should this setting even be 5.1 for 5.1 movies? Shouldn't Doom3 accept 7.1 as a setting and switch to 5.1 internally (if yes, a fix please, id!). I don't mind that my centre back speaker is mute for Doom3, but I like to still watch my 6.1 dvds in 6.1, without changing the setting all the time!!!

Thanks fergusdog for reporting this in!

i killed an IMP in a doorway and i don't remember if the door just opened or not but the imp got stuck and was spinning rapidly before it melted. kinda wierd seems a bug in the physics code.

On my video card (PNY Geforce 4 4200) the game was olmost pitch black at default settings, all i could see was lighting flares and GUI's. after changing the r_renderer to NV10 it went away (it was using a default NV20 path).
Intel 2.5ghz on Intel D865PERL
Audigy2
1gb ram
WinXP SP1.

I can open the game and play for five minutes at most, but then it closes and goes back to windows with no error or anything. All drivers are the most up to date from manufacturer's website and windows display settings match those in the game. I've tried everything. Help!!!

System:
CPU - Athalon XP 2200+ 1.8Ghz
GPU - NVidia GeForce3 Ti 200 Driver = v62.11
RAM - 512 MB DDR
Sound Card - Vinyl AC'97
O/C no

The game installed without a problem, and seemed to be fine when it first started (id intro was perfect)... then, when the next screens came up all the graphics turned into a garbled mess! The cursor, text, and other images come and go and I can't see what I'm doing at all. I've read through other posts that mention anything about weird graphics and done whatever they suggested for those (updated all drivers, etc.) and no matter what, I still have the same garbled graphics.

I also thought that maybe if I got past the setup screens, the game might be okay... nope, the same thing happens even when I start a new game.

Please help, I'd like to at least play the game~
dhughes

btw.. i ran dxdiag.. and it didn't show anything was wrong.
no overclocking either~

win xp sp1
2.8 ghz
512 ram
ati 9700 pro 4.7
sblive 5.1

http://img.photobucket.com/albums/v431/ ... aphics.jpg

!!!Just wanted to post the outcome... turns out my Dell video card, was defective from the beginning. I saw little signs (and didn't recognize them as such) from day one, but because the programs I normally run didn't seem affected, I didn't question the occasional "artifacting"~ After weeks of trying A to Z to "fix" the graphics for Doom 3~ I switched cards, first with an identical ATI 9700 pro 128 (this one purchased from retail store) ... results.. no problems, no artifacts... then, I put my OLD Nvidia Ti 500 in, with the same results (although a bit slower), no artifacts.

So, I can now play Doom 3~ and will NOT BE purchasing any more systems from Dell.com!

Thanks for everyones input...
dhughes

Doom3 crashes after the cut scenes if they are allowed to play to completion, completely freezing the computer and requiring a hard reboot (removing the battery on the laptop). It also runs choppy prior to this point.

The laptop is a dell (i'm sorry i don't have the make and model currently as it isn't mine, i will edit it in when i can to add more information).

Processor: Pentium 3.4 EE (i believe)
Ram: at least 1gb
Video Card: Radeon 9700 128mb
Sound: unsure
OS: WinXP home

Nothing has been overclocked unless it shipped that way. We have attempted loading all the newest drivers (mb, sound, ati) to ensure that is not the problem. We are also going to try the other recommendations from the activsion help site, and if any solution is found i'll edit and post here. Any help is required (my father is dying to play this and won't be home to his home pc till next week).

Feffer wrote:

Processor: Pentium 3.4 EE (i believe)

On a laptop? I don't think so.

Ok multiplayer has stopped working entirely for me. Whenever I click to join a server and it connect, Doom 3 shuts down. However, I can create servers with no problem. What's even stranger is that it was working fine before, and now it has died. I have made no multiplayer or networking modifications to the DoomConfig.

Another bug. When using com_allowConsole 1 and -nointro, the main menu doesn't load, only the console shows up and it takes up the entire screen. However, when you type com_allowConsole 0 into the console, the main menu loads, and you can use Doom 3 like normal.

My system:

Gf Ti4200 64MB
AMD 2600+
512Mt RAM

The problem: The game seems to use rasterized lighting, smoke and shadow effects like the game wouldn't be in 32-bit mode. The game looks just fine and smooth in my friends computer that has Radeon 9700.

I have crashes which happen at the same points in the game every single time. For example, in mars_city2, I step up to one particular door and it hangs; in the next level after that, there's a cutscene when you walk out of the elevator and the camera flies through an airvent and shows the bald guy w/ sunglasses talking to someone else, well the game hangs every single time when the bald heads come into the frame... wierdness...

I've been loading some maps using the console and when I finish the particular part of a map and it's time to go to the next part, I keep a console error unable to find "current map name".proc This has happened to me with three different maps. Does anyone have any idea as to what's happening here?

mac53 wrote:

Here's what I think it is. 1.3.1. has been built with the 64 bit vista in mind and it's dumb-founded when ran on a 32 bit os. Doom 3 was built for 32 bits and so was all the patches up to 1.3.1. It's appearing to me, that it's a case of 'either, or'... not 'both' when it comes to software, especially in this case. Personally, I think that 1.3.1. is a beta and hasn't been tested properly. I'm not a pro here, nor do I claim to be a 'puter wiz', but there are times where it doesn't take a 'rocket scientist' to see what's going on, just one to explain it! I want to help with this and I'll do my best.

To the best of my knowledge the Vista changes were related to detecting whether a OpenGL ICD is installed. If not you should get a warning relating to performance if you're using the Vista OpenGL wrapper without driver support. Can't be 100% on that as I never tried on Vista without an ICD. I linked to it before, but Timothee Besset's plan has the full release info...

http://www.bluesnews.com/plans/476/

Doom 3 is still 32-bit (Vista still comes as both, don't forget). As for testing it did have a full QA pass. I used each of the test releases with no problems from early Dec 2006 until it was released in Feb 2007. I played the RoE expansion pack right through just in case.

The Mac developers Aspyr did an independent QA test of their build.

We've been running the patch on our servers since release with no problems. My mod server has had nearly 400 individual players connect to it since it was upgraded to 1.3.1.

Now, I don't deny that you and vinnie_jones do have some sort of problem but you're the only two people I've heard from that could not get 1.3.1 running.

I think it is also useful to clear up some terminology. A "crash" is when the game does something unexpected and can't recover from it. Like simply dropping back to the desktop or giving you one of those error boxes like you have seen.

Other problems, such as the DLL API message, are not "crashes" but are genuine error conditions that the game has detected and reported to you (a mod built for a different release in this case).

One thing you could try is to do disable EAX/OpenAL. I've had one player recently whose D3 would crash on startup when these were enabled.

You can do this by editing DoomConfig.cfg and making sure the appropriate values are set to zero.

seta s_useEAXReverb "0"
seta s_useOpenAL "0"

Sim

simulation wrote:

Now, I don't deny that you and vinnie_jones do have some sort of problem but you're the only two people I've heard from that could not get 1.3.1 running.

Thank you for the correction in a professional manner. You are correct, I used the wrong term. "Freezes" explains it exactly.

rich_is_bored wrote:

Unfortunately, those dialogs are worthless. I couldn't begin to tell you what the problem is.

Agreed that in general they're not too helpful. However you can sometimes get some info from them. If you click the "click here" link, you'll get another dialog which shows some basic information about the crash. Significantly, it shows the module, which can sometimes point you at the problem (eg if its "nvogl.dll" then its probably an nVidia OpenGL issue).

If its in gamex86.dll, and you're running a mod, the mod author may be able to use the "faulting address" to tell you something about the crash.

Also while its open, depending on how your Windows is configured there might be a .mdmp file hanging around in your temp directory associated with this crash, which might be helpful to a programmer to trace the issue. It'll probably get deleted as you close the dialog though.

simulation wrote:

To the best of my knowledge the Vista changes were related to detecting whether a OpenGL ICD is installed. If not you should get a warning relating to performance if you're using the Vista OpenGL wrapper without driver support. Can't be 100% on that as I never tried on Vista without an ICD. I linked to it before, but Timothee Besset's plan has the full release info...

http://www.bluesnews.com/plans/476/

Doom 3 is still 32-bit (Vista still comes as both, don't forget). As for testing it did have a full QA pass. I used each of the test releases with no problems from early Dec 2006 until it was released in Feb 2007. I played the RoE expansion pack right through just in case.

The link you posted here, takes you to the version that I was using, and causing the posted issues.

mac53 wrote:

simulation wrote:

To the best of my knowledge the Vista changes were related to detecting whether a OpenGL ICD is installed. If not you should get a warning relating to performance if you're using the Vista OpenGL wrapper without driver support. Can't be 100% on that as I never tried on Vista without an ICD. I linked to it before, but Timothee Besset's plan has the full release info...

http://www.bluesnews.com/plans/476/

Doom 3 is still 32-bit (Vista still comes as both, don't forget). As for testing it did have a full QA pass. I used each of the test releases with no problems from early Dec 2006 until it was released in Feb 2007. I played the RoE expansion pack right through just in case.

The link you posted here, takes you to the version that I was using, and causing the posted issues.

Yes, I realise that. I was linking so you could read the info about the release straight from the developer who created it.

@simulation

Thank you, [for me] reading that garble doesn't help me any... I wish it does.

hehe im not at all surprised im one of the few (?)
people who has problems with the new patch, i had the same
bs with the 1.32 patch for far cry (altho THAT patch was so flawed
crytec or whatever theyre called actually withdrew it),
i also had serious issues with that MoH box (dont rememebr the name but it had 4 cd-s in it) but i googled that and many had issues with that
as well, sometimes i just wanna take the comp and chuck it
through the window and just "retire" to some console

For the time being, if not forever, im sticking with the 1.3 patch

Could anyone tell me why when I go to activate the EAX in the sound options menu, it freezes my system? I have the Audigy 2 zs Platinum SB sound card with ALL the updated bells and whistles. EAX console, DTS, the whole nine yards. There's no logical reason why this option should freeze my system. I saw an eax update for doom3, but there's no way I'm going to uninstall my current Creative software and drivers to install this crap. There has to be some way to activate this feature, I have this option in my current software. :evil:

The cvar for enabling EAX is s_useEAXReverb. You could try adding...

Code:

s_useEAXReverb 1

... to DoomConfig.cfg

I did and it froze Doom 3 while I tried to apply the setting within the menu and entering the attribute within the cfg file gives me this. Doom 3 doesn't even load...

Issue resolved thanks to Doomworld. This is an issue pertaining just to Creative "Soundblaster" Audigy series cards. If you using Creative and want the EAX reverb and are not able to get it to function, then here is a link that will answer many questions pertaining to this.

http://forums.creative.com/creative...id=soundblaster

There's also a software that installs the proper API to make Doom 3's EAX HD reverb functional. If I get enough requests, I can upload this API software and post the link to it here.

EAX issue resolved.

Hi, im new to this forum...

I builded a new pc and these are the specs:

CPU: AMD phenom 9850 2.5Ghz
Memory: Corsair XMS2 DDR2 800Mhz
Video: 2x EVGA 9800GT in SLI mode
Motherboard: Asus M3N-HT Deluxe
HDD: Western Digital Caviar 250GB

When i play doom 3, i get to play for about a minute or two, and then my PC shuts down completely... i need to power it on and then wait till it shows some video, sometimes i need to reset it 2 or 3 times because it doesnt show any video at all...

I think i have a Drivers issue, but i want to know how can i fix it... please help...

It abruptly powers off? That sounds like a hardware issue. How long have you had this new PC? A few days?

I have problems with the display. All characters appear to be half in light and half in shadow.

Here's a screenshot of what it looks like:

My system:
CPU: Intel Core 2 Duo 2.80 GHZ
RAM: 4 GB DDR2
GPU: Intel G41 Express Chipset (driver version 8.15.10.2555)
Sound card: Realtek HD audio
OS: Windows 7 Ultimate x64 bit SP1
No overclock

Not a fan of integrated video cards, but I guess that your problem is caused by video drivers.

Check for updates.

How do I explain this? When playing Doom 3 and I'm walking through doing my thing, all of a sudden the run mode locks in and won't return to normal unless I exit out of the game. Then when I'm back at my desk-top, at least 15 or so icons are blue as if they were all selected. I can't turn this off. I tried "Ctrl", "Alt" & "Del" and the "task manager" doesn't open, so I can't see what's going on. Start, "Turn Off Computer", doesn't function either. The only way I can reboot my computer is to hit the "reset" button and this is the only way that will get me out of this situation. This happens ALOT! :evil:

Edited: I have patches 1, 2, & 3 installed along with "ROE" expansion.
I'm running WinXP Home, SP2 on 64 bit hardware.

ASUS K8V SE DELUXE > Motherboard
AMD ATHLON "64", 3200+ > Processor
2 gig memory > dual channel
VIA K8T800 > MB Drivers
MAXTOR 6L3000RO > Drive > not overclocked
NVIDIA GeForce 7600 GS > 256 > not overclocked

Finally my system crashes. I went into my "System Information" and found this error log.

5/18/2007 12:00 AM Application Error Faulting application doom3.exe, version 1.0.0.1, faulting module doom3.exe, version 1.0.0.1, fault address 0x00085ff6.


I just finished with a fresh install and here it is again:

5/18/2007 1:06 AM Application Error Faulting application doom3.exe, version 1.0.0.1, faulting module doom3.exe, version 1.0.0.1, fault address 0x0001e03f.


Man, what's going on here? :evil:

My last report:

Code:

DOOM 1.3.1302 win-x86 May 12 2005 10:40:52
2002 MHz AMD CPU with MMX & 3DNow! & SSE & SSE2
2048 MB System Memory
256 MB Video Memory
Winsock Initialized
Found interface: {64B2528E-7662-44E9-A250-AFC1E4178E39} Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter, Copper RJ-45 - Packet Scheduler Miniport - 10.0.0.4/255.255.255.0
Sys_InitNetworking: adding loopback interface
doom using MMX & SSE & SSE2 for SIMD processing
enabled Flush-To-Zero mode
enabled Denormals-Are-Zero mode
------ Initializing File System ------
Loaded pk4 C:\Program Files\Doom 3\base\game00.pk4 with checksum 0x29cdb978
Loaded pk4 C:\Program Files\Doom 3\base\pak000.pk4 with checksum 0xc9d99db8
Loaded pk4 C:\Program Files\Doom 3\base\pak001.pk4 with checksum 0x40244be0
Loaded pk4 C:\Program Files\Doom 3\base\pak002.pk4 with checksum 0x64243cc7
Loaded pk4 C:\Program Files\Doom 3\base\pak003.pk4 with checksum 0x79bee669
Loaded pk4 C:\Program Files\Doom 3\base\pak004.pk4 with checksum 0x765e4f8b
Loaded pk4 C:\Program Files\Doom 3\base\pak005.pk4 with checksum 0x8ffc3621
Loaded pk4 C:\Program Files\Doom 3\base\pak006.pk4 with checksum 0x95b65ab
Current search path:
C:\Program Files\Doom 3/base
C:\Program Files\Doom 3\base\pak006.pk4 (48 files)
C:\Program Files\Doom 3\base\pak005.pk4 (63 files)
C:\Program Files\Doom 3\base\pak004.pk4 (5137 files)
C:\Program Files\Doom 3\base\pak003.pk4 (4676 files)
C:\Program Files\Doom 3\base\pak002.pk4 (6120 files)
C:\Program Files\Doom 3\base\pak001.pk4 (8972 files)
C:\Program Files\Doom 3\base\pak000.pk4 (2698 files)
C:\Program Files\Doom 3\base\game00.pk4 (2 files)
game DLL: 0x0 in pak: 0x0
Addon pk4s:
file system initialized.
--------------------------------------
----- Initializing Decls -----
------------------------------
------- Initializing renderSystem --------
using ARB renderSystem
renderSystem initialized.
--------------------------------------
5180 strings read from strings/english.lang
Couldn't open journal files
execing editor.cfg
execing default.cfg
execing DoomConfig.cfg
couldn't exec autoexec.cfg
5180 strings read from strings/english.lang
----- Initializing Sound System ------
sound system initialized.
--------------------------------------
----- R_InitOpenGL -----
Initializing OpenGL subsystem
...registered window class
...registered fake window class
...initializing QGL
...calling LoadLibrary( 'opengl32' ): succeeded
...calling CDS: ok
...created window @ 0,0 (1280x1024)
Initializing OpenGL driver
...getting DC: succeeded
...PIXELFORMAT 10 selected
...creating GL context: succeeded
...making context current: succeeded

------- Input Initialization -------
Initializing DirectInput...
mouse: DirectInput initialized.
keyboard: DirectInput initialized.
------------------------------------
sound: STEREO
...using GL_ARB_multitexture
...using GL_ARB_texture_env_combine
...using GL_ARB_texture_cube_map
...using GL_ARB_texture_env_dot3
...using GL_ARB_texture_env_add
...using GL_ARB_texture_non_power_of_two
...using GL_ARB_texture_compression
...using GL_EXT_texture_compression_s3tc
...using GL_EXT_texture_filter_anisotropic
   maxTextureAnisotropy: 16.000000
...using GL_1.4_texture_lod_bias
X..GL_EXT_shared_texture_palette not found
...using GL_EXT_texture3D
...using GL_EXT_stencil_wrap
...using GL_NV_register_combiners
...using GL_EXT_stencil_two_side
X..GL_ATI_fragment_shader not found
X..GL_ATI_text_fragment_shader not found
...using GL_ARB_vertex_buffer_object
...using GL_ARB_vertex_program
...using GL_ARB_fragment_program
...using EXT_depth_bounds_test
---------- R_NV20_Init ----------
---------------------------------
----------- R200_Init -----------
Not available.
---------- R_ARB2_Init ----------
Available.
---------------------------------
----- R_ReloadARBPrograms -----
glprogs/test.vfp
glprogs/test.vfp
glprogs/interaction.vfp
glprogs/interaction.vfp
glprogs/bumpyEnvironment.vfp
glprogs/bumpyEnvironment.vfp
glprogs/ambientLight.vfp
glprogs/ambientLight.vfp
glprogs/shadow.vp
glprogs/R200_interaction.vp
glprogs/nv20_bumpAndLight.vp
glprogs/nv20_diffuseColor.vp
glprogs/nv20_specularColor.vp
glprogs/nv20_diffuseAndSpecularColor.vp
glprogs/environment.vfp
glprogs/environment.vfp
glprogs/arbVP_glasswarp.txt: File not found
glprogs/arbFP_glasswarp.txt: File not found
-------------------------------
using ARB_vertex_buffer_object memory
using ARB2 renderSystem
found DLL in pak file: C:\Program Files\Doom 3\base\game00.pk4/gamex86.dll
copy gamex86.dll to C:\Program Files\Doom 3\base\gamex86.dll
0 0 1280 1024
Regenerated world, staticAllocCount = 0.
Shutting down sound hardware
idRenderSystem::Shutdown()
Shutting down OpenGL subsystem
...wglMakeCurrent( NULL, NULL ): success
...deleting GL context: success
...releasing DC: success
...destroying window
...shutting down QGL
...unloading OpenGL DLL
wrong game DLL API version

I'm not sure what's going on there but this is curious...

Code:

wrong game DLL API version

Generally this error message means the game library and main executable are not the same version.

It's pretty common to see this error message creep up when dealing with mods but I assume you're running the vanilla game, in which case it sounds more like the latest patch didn't install correctly.

I would suggest reinstalling the game from scratch, installing ROE, and then installing the 1.3.1 patch.

The problem is that I'm running into this ALL THE TIME! I have uninstalled and reinstalled this game atleast four to five times, each with the same issue. I use all the patches and yes you are correct, I am running a mod, [Annihilation X], to be exact. Did you read the very beginning where the game locks up in the running mode on me? I have a lot of strange sh!t going on here.

mac53 wrote:

My last report:

DOOM 1.3.1302 win-x86 May 12 2005 10:40:52

... snip ...

------ Initializing File System ------
Loaded pk4 C:\Program Files\Doom 3\base\game00.pk4 with checksum 0x29cdb978
Loaded pk4 C:\Program Files\Doom 3\base\pak000.pk4 with checksum 0xc9d99db8
Loaded pk4 C:\Program Files\Doom 3\base\pak001.pk4 with checksum 0x40244be0
Loaded pk4 C:\Program Files\Doom 3\base\pak002.pk4 with checksum 0x64243cc7
Loaded pk4 C:\Program Files\Doom 3\base\pak003.pk4 with checksum 0x79bee669
Loaded pk4 C:\Program Files\Doom 3\base\pak004.pk4 with checksum 0x765e4f8b
Loaded pk4 C:\Program Files\Doom 3\base\pak005.pk4 with checksum 0x8ffc3621
Loaded pk4 C:\Program Files\Doom 3\base\pak006.pk4 with checksum 0x95b65ab
Current search path:
C:\Program Files\Doom 3/base
C:\Program Files\Doom 3\base\pak006.pk4 (48 files)
C:\Program Files\Doom 3\base\pak005.pk4 (63 files)
C:\Program Files\Doom 3\base\pak004.pk4 (5137 files)
C:\Program Files\Doom 3\base\pak003.pk4 (4676 files)
C:\Program Files\Doom 3\base\pak002.pk4 (6120 files)
C:\Program Files\Doom 3\base\pak001.pk4 (8972 files)
C:\Program Files\Doom 3\base\pak000.pk4 (2698 files)
C:\Program Files\Doom 3\base\game00.pk4 (2 files)
game DLL: 0x0 in pak: 0x0

.. snip ...

found DLL in pak file: C:\Program Files\Doom 3\base\game00.pk4/gamex86.dll
copy gamex86.dll to C:\Program Files\Doom 3\base\gamex86.dll

You have a misconfigured install here. "DOOM 1.3.1302" means you are running the EXE from the 1.3 patch (May 2005).

In your "base" folder you should also have the following files...

pak007.pk4
game01.pk4
game02.pk4
game03.pk4

You're using Windows, it should be trying to load the gamex86.dll file from game03.pk4 but what is happening is that it is using the one from game00.pk4 (from 1.0, 1.1 or 1.2) which is not compatible with the EXE you have in the "C:\Program Files\Doom 3" folder.

Also, the log you posted here isn't running the Annihilation-X mod, just standard Doom 3.

Sim

Hmm... I just read the info on the the Annihilation-X mod. It looks to me as though they've included copyrighted music tracks within the game. Naughty naughty. Unless they got permission from KorN et al of course.

simulation wrote:

Hmm... I just read the info on the the Annihilation-X mod. It looks to me as though they've included copyrighted music tracks within the game. Naughty naughty. Unless they got permission from KorN et al of course.

Hmm...! I don't know about that part. Actually, yes I do! I'll unpak the pk4 file they're in and get rid of the SOB's, then just repak the file without them. Now, that you had brought that up has me in doubt! I don't like that music anyway!

simulation wrote:

Also, the log you posted here isn't running the Annihilation-X mod, just standard Doom 3.

Well, that's really strange, because It's running the mod that has caused much of this issue... second thought, it's not only the mod I was having these issues with. In the beginning statement of my post, where the forward - run mode would lock on, started when I was playing just the Doom3 game! :cry:

Any suggestions?

Added: I'm getting to go through another fresh install using all three patches. I'll screenshot my directory's folder and show what files are in them. Hopefully this will help to figure out what's going on. :shock:

What folder did the mod install itself in? Or did you do a manual install? If so, where did you put it?

Mods should go in their own folder e.g.

"C:\Program Files\Doom 3\AnnX"

and then you start doom with a fs_game parameter

doom3.exe +set fs_game AnnX

or just load it from the mods menu.

NEVER install a full mod into the "base" folder. The only PK4 files you should find in there (other than the standard ones) are custom MP mods.

Sim

Here's my directory...

C:\Program Files\Doom 3\Annihilation X

I put nothing in my Doom 3 base directory. If mods are full versions, then they get dropped into the Doom 3 directory in their own folders and I load them from the "Mods" menu. :wink:

I'll be back... doing a fresh install and going to test it... again!!

If you're getting a suddenly-running-all-the-time "bug" then it might be evil StickyKeys because you're holding shift for a number of seconds, or can happen when playing with the process priority from the task manager.

LDAsh wrote:

If you're getting a suddenly-running-all-the-time "bug" then it might be evil StickyKeys because you're holding shift for a number of seconds, or can happen when playing with the process priority from the task manager.

Thank you... but I have "StickyKeys" turned off. :wink:

Ok.. here's what my directories look like.

Code:

Contents of base folder after first install and no patch applied:

doomkey
game00.pk4
pak000.pk4
pak001.pk4
pak002.pk4
pak003.pk4
pak004.pk4
-----------------------------------------------------
Applying [D3_1_1.exe]

pak005.pk4  -  added
----------------------------------------------------
Installing [D3_ROE] and the inevitable [D3_1_2.exe] patch.

pak006.pk4  -  added
xpkey  -  added

Including the directory:  C:\Program Files\Doom 3\d3xp   which contains;

game00.pk4
pak000.pk4
--------------------------------------------------------

Installing the [DOOM3_1.3.1.exe] patch.

Added to base folder;

game01.pk4
game02.pk4
game03.pk4
pak007.pk4
pak008.pk4
----------------------------------------------------------

Added to d3xp folder;

game01.pk4
game02.pk4
game03.pk4
pak001.pk4

These are the files I have in both directories after installing Doom3, ROE and all three patches.

Crazy idea: Just install d3. no ROE or any other mod. just plain D3.

Does the problem happen then?

if no, install a (one) mod.

Does the problem happen then?

etc

Hex wrote:

Crazy idea: Just install d3. no ROE or any other mod. just plain D3.

Does the problem happen then?

if no, install a (one) mod.

Does the problem happen then?

etc

Hmm... Not a bad idea! :wink:

I do have this issue though. It won't F5 "quicksave" for me. Here's the console report. Edited: Actually, let me be a little more clear about what I'm saying here. When I try to load a save that I attempted a "F5" save, this is what I've been getting.

Any help here? :cry:

That issue is likely derivative of the issue we discussed initially. The main executable and the game library being loaded are not compatible. Because of this discrepancy, you may find all sorts of features that don't function properly. Saving and loading games is not an exception.

Prior to reinstallation, if you haven't already, delete the Doom 3 folder and all it's contents. You don't need any stray files from a previous install present possibly causing the problem to reoccur.

For the time being, don't concern yourself with any mods. Your goal is simply to get Doom 3 working.

Also, don't bother with the intermediate updates. Simply install the game and then immediately update to 1.3.1. Delete any patches you currently have on your desktop and download the 1.3.1 patch from a reputable source if not directly from id itself.

Okay... Thank you very much... I'll do exactly as you say! Your patients and understanding is highly appreciated.

Edited: I just checked Id Software's site for offical updates as you suggested. Unfortunately, they don't carry it anymore. I ran into a dead link there.

mac53 wrote:

I just checked Id Software's site for offical updates as you suggested. Unfortunately, they don't carry it anymore. I ran into a dead link there.

The only "official" word from id Software about the 1.3.1 patch has been in Timothee Besset's .plan...

http://www.bluesnews.com/plans/476/

Sim

mac53 wrote:

How do I explain this? When playing Doom 3 and I'm walking through doing my thing, all of a sudden the run mode locks in and won't return to normal unless I exit out of the game. Then when I'm back at my desk-top, at least 15 or so icons are blue as if they were all selected. I can't turn this off. I tried "Ctrl", "Alt" & "Del" and the "task manager" doesn't open, so I can't see what's going on. Start, "Turn Off Computer", doesn't function either. The only way I can reboot my computer is to hit the "reset" button and this is the only way that will get me out of this situation. This happens ALOT! :evil:

Then

rich_is_bored wrote:

For the time being, don't concern yourself with any mods. Your goal is simply to get Doom 3 working.

Also, don't bother with the intermediate updates. Simply install the game and then immediately update to 1.3.1. Delete any patches you currently have on your desktop and download the 1.3.1 patch from a reputable source if not directly from id itself.

I followed your instructions, this time I installed Doom 3 with just the [DOOM3-1.3.1] patch and no mods. Started to play the game and into the third map when it did it again. This time I was able to "screenshot" the Desktop.

What do I do now?...

Launch the game and type "conDump test" into the console. Then browse to your Doom 3 installation directory, open the base folder and locate a file named test.txt.

Open this file. This will be a dump of all the output from the console. Locate the following lines...

Code:

DOOM 1.3.1.1304 win-x86 Jan 16 2007 15:36:51

Code:

found DLL in pak file: C:\Program Files\Doom 3\base\game03.pk4/gamex86.dll

The first line should read "DOOM 1.3.1.1304" as you have installed the latest patch. The second line should read "game03.pk4" as it should be loading the version of gamex86.dll from that pk4.

If these two lines match the criteria outlined above, then the patch has been installed successfully and it's time to rule out the game itself as the cause of your problems.

That said, it sounds to me like the game is losing focus and your input is being inadvertently interpreted by windows as clicking and dragging about on the desktop. That would explain the stuck key and the selected icons on your desktop.

The question however is why the game would lose focus and that's hard to answer. Obviously it's some process running in the background that's at fault. But it's pretty much impossible to determine which without knowing everything that you have installed and subsequently the common faults experienced with each of those applications.

The best I can tell you is to try running the game with as few background processes running as possible. You might try running windows in safe mode permitted Doom 3 will run under those conditions.

I'm not saying that's going to solve your problems but it will verify that the problem is indeed caused by some external program. From that point you will have to isolate the offending program by via trial and error.

I suggest learning how to prevent programs from launching alongside windows by using "msconfig". Google it if need be.

i never seen a desktop with more icons on it ever

in my experience its best to have as few things on desktop
as possible, better to have them on the quickstart down left
next to start, just a friendly advice

vinnie_jones wrote:

i never seen a desktop with more icons on it ever

in my experience its best to have as few things on desktop
as possible, better to have them on the quickstart down left
next to start, just a friendly advice

You think that's a lot!!! You should have seen some of the other computers I have seen. Icons on the desktop is just a thing of preference, that's all. :wink:

rich_is_bored wrote:

Launch the game and type "conDump test" into the console. Then browse to your Doom 3 installation directory, open the base folder and locate a file named test.txt.

Open this file. This will be a dump of all the output from the console. Locate the following lines...

Code:

DOOM 1.3.1.1304 win-x86 Jan 16 2007 15:36:51

Code:

found DLL in pak file: C:\Program Files\Doom 3\base\game03.pk4/gamex86.dll

The first line should read "DOOM 1.3.1.1304" as you have installed the latest patch. The second line should read "game03.pk4" as it should be loading the version of gamex86.dll from that pk4.

If these two lines match the criteria outlined above, then the patch has been installed successfully and it's time to rule out the game itself as the cause of your problems.

That said, it sounds to me like the game is losing focus and your input is being inadvertently interpreted by windows as clicking and dragging about on the desktop. That would explain the stuck key and the selected icons on your desktop.

The question however is why the game would lose focus and that's hard to answer. Obviously it's some process running in the background that's at fault. But it's pretty much impossible to determine which without knowing everything that you have installed and subsequently the common faults experienced with each of those applications.

The best I can tell you is to try running the game with as few background processes running as possible. You might try running windows in safe mode permitted Doom 3 will run under those conditions.

I'm not saying that's going to solve your problems but it will verify that the problem is indeed caused by some external program. From that point you will have to isolate the offending program by via trial and error.

I suggest learning how to prevent programs from launching alongside windows by using "msconfig". Google it if need be.

Ok guys, sorry to have taken so long in getting back to you with this, it's just the [whole-ball-of-wax] just frustrated me and I had to walk away for awhile.

rich_is_bored...[Hmm... I bet it is]

I did the con dump you taught me to do and here's the whole 'nine-yards', because it wrote to notepad. I have a problem! Here's the report:

Con Test wrote:

DOOM 1.3.1.1304 win-x86 Jan 16 2007 15:36:51
2002 MHz AMD CPU with MMX & 3DNow! & SSE & SSE2
2048 MB System Memory
256 MB Video Memory
Winsock Initialized
Found interface: {64B2528E-7662-44E9-A250-AFC1E4178E39} Marvell Yukon Gigabit
Ethernet 10/100/1000Base-T Adapter, Copper RJ-45 - Packet Scheduler Miniport -
10.0.0.4/255.255.255.0
Sys_InitNetworking: adding loopback interface
doom using MMX & SSE & SSE2 for SIMD processing
enabled Flush-To-Zero mode
enabled Denormals-Are-Zero mode

Section Edited: Too much info...

What now, buddy?

So exactly what goes wrong now? That dump looks fine for base D3 using 1.3.1.1304. And it connected OK to the master server at id to set your guid value.

What happens next that is wrong?

@simulation

If you don't mind taking the time and starting here:

http://www.doom3world.org/phpbb2/viewto ... c&start=60
and reading through because there are numerous issues occuring.

The last one is that Doom 3 is totally crashing when I load a mod... any mod, doesn't matter!

now, according to "rich_is_bored" he had stated that when a con test is conducted that these two lines should appear at the top of the test

Code:

DOOM 1.3.1.1304 win-x86 Jan 16 2007 15:36:51

Code:

found DLL in pak file: C:\Program Files\Doom 3\base\game03.pk4/gamex86.dll

Look at the test results I posted, the second code I listed here, never ocurred, so it is apparent that there's an issue going on here.

You need to read to catch up, budddy.
------------------------------------------------------------------

Edited:

Reinstalled Doom3 w/ ROE & DOOM3-1.3.1.exe update patch.

Everthing looked fine in the test report except at the bottom where I have it posted here.

condump test wrote:

DOOM 1.3.1.1304 win-x86 Jan 16 2007 15:36:51
2002 MHz AMD CPU with MMX & 3DNow! & SSE & SSE2
2048 MB System Memory
256 MB Video Memory
Winsock Initialized
Found interface: {64B2528E-7662-44E9-A250-AFC1E4178E39} Marvell Yukon Gigabit
Ethernet 10/100/1000Base-T Adapter, Copper RJ-45 - Packet Scheduler Miniport -
10.0.0.4/255.255.255.0
Sys_InitNetworking: adding loopback interface
doom using MMX & SSE & SSE2 for SIMD processing
enabled Flush-To-Zero mode
enabled Denormals-Are-Zero mode
------ Initializing File System ------
Loaded pk4 C:\Program Files\Doom 3\base\game00.pk4 with checksum 0x29cdb978
Loaded pk4 C:\Program Files\Doom 3\base\game01.pk4 with checksum 0x51c6981f
Loaded pk4 C:\Program Files\Doom 3\base\game02.pk4 with checksum 0xf3ec6f7
Loaded pk4 C:\Program Files\Doom 3\base\game03.pk4 with checksum 0x5d4230ea
Loaded pk4 C:\Program Files\Doom 3\base\pak000.pk4 with checksum 0x2cb26dc3
Loaded pk4 C:\Program Files\Doom 3\base\pak001.pk4 with checksum 0x40244be0
Loaded pk4 C:\Program Files\Doom 3\base\pak002.pk4 with checksum 0x64243cc7
Loaded pk4 C:\Program Files\Doom 3\base\pak003.pk4 with checksum 0x79bee669
Loaded pk4 C:\Program Files\Doom 3\base\pak004.pk4 with checksum 0x765e4f8b
Loaded pk4 C:\Program Files\Doom 3\base\pak005.pk4 with checksum 0x8ffc3621
Loaded pk4 C:\Program Files\Doom 3\base\pak006.pk4 with checksum 0x95b65ab
Loaded pk4 C:\Program Files\Doom 3\base\pak007.pk4 with checksum 0x666bdb3c
Loaded pk4 C:\Program Files\Doom 3\base\pak008.pk4 with checksum 0x23ae5993
Current search path:
C:\Program Files\Doom 3/base
C:\Program Files\Doom 3\base\pak008.pk4 (3 files)
C:\Program Files\Doom 3\base\pak007.pk4 (38 files)
C:\Program Files\Doom 3\base\pak006.pk4 (48 files)
C:\Program Files\Doom 3\base\pak005.pk4 (63 files)
C:\Program Files\Doom 3\base\pak004.pk4 (5137 files)
C:\Program Files\Doom 3\base\pak003.pk4 (4676 files)
C:\Program Files\Doom 3\base\pak002.pk4 (6120 files)
C:\Program Files\Doom 3\base\pak001.pk4 (8972 files)
C:\Program Files\Doom 3\base\pak000.pk4 (2698 files)
C:\Program Files\Doom 3\base\game03.pk4 (2 files)
C:\Program Files\Doom 3\base\game02.pk4 (2 files)
C:\Program Files\Doom 3\base\game01.pk4 (2 files)
C:\Program Files\Doom 3\base\game00.pk4 (2 files)
game DLL: 0x0 in pak: 0x0
Addon pk4s:
file system initialized.
--------------------------------------
----- Initializing Decls -----
------------------------------
------- Initializing renderSystem --------
using ARB renderSystem
renderSystem initialized.
--------------------------------------
5206 strings read from strings/english.lang
Couldn't open journal files
execing editor.cfg
execing default.cfg
execing DoomConfig.cfg
couldn't exec autoexec.cfg
5206 strings read from strings/english.lang
----- Initializing Sound System ------
sound system initialized.
--------------------------------------
----- R_InitOpenGL -----
Initializing OpenGL subsystem
...registered window class
...registered fake window class
...initializing QGL
...calling LoadLibrary( 'opengl32' ): succeeded
...calling CDS: ok
...created window @ 0,0 (1024x768)
Initializing OpenGL driver
...getting DC: succeeded
...PIXELFORMAT 10 selected
...creating GL context: succeeded
...making context current: succeeded

------- Input Initialization -------
Initializing DirectInput...
mouse: DirectInput initialized.
keyboard: DirectInput initialized.
------------------------------------
sound: STEREO
...using GL_ARB_multitexture
...using GL_ARB_texture_env_combine
...using GL_ARB_texture_cube_map
...using GL_ARB_texture_env_dot3
...using GL_ARB_texture_env_add
...using GL_ARB_texture_non_power_of_two
...using GL_ARB_texture_compression
...using GL_EXT_texture_compression_s3tc
...using GL_EXT_texture_filter_anisotropic
maxTextureAnisotropy: 16.000000
...using GL_1.4_texture_lod_bias
X..GL_EXT_shared_texture_palette not found
...using GL_EXT_texture3D
...using GL_EXT_stencil_wrap
...using GL_NV_register_combiners
...using GL_EXT_stencil_two_side
X..GL_ATI_fragment_shader not found
X..GL_ATI_text_fragment_shader not found
...using GL_ARB_vertex_buffer_object
...using GL_ARB_vertex_program
...using GL_ARB_fragment_program
...using EXT_depth_bounds_test
---------- R_NV20_Init ----------
---------------------------------
----------- R200_Init -----------
Not available.
---------- R_ARB2_Init ----------
Available.
---------------------------------
----- R_ReloadARBPrograms -----
glprogs/test.vfp
glprogs/test.vfp
glprogs/interaction.vfp
glprogs/interaction.vfp
glprogs/bumpyEnvironment.vfp
glprogs/bumpyEnvironment.vfp
glprogs/ambientLight.vfp
glprogs/ambientLight.vfp
glprogs/shadow.vp
glprogs/R200_interaction.vp
glprogs/nv20_bumpAndLight.vp
glprogs/nv20_diffuseColor.vp
glprogs/nv20_specularColor.vp
glprogs/nv20_diffuseAndSpecularColor.vp
glprogs/environment.vfp
glprogs/environment.vfp
glprogs/arbVP_glasswarp.txt: File not found
glprogs/arbFP_glasswarp.txt: File not found
-------------------------------
using ARB_vertex_buffer_object memory
using ARB2 renderSystem
found DLL in pak file: C:\Program Files\Doom 3\base\game03.pk4/gamex86.dll
copy gamex86.dll to C:\Program Files\Doom 3\base\gamex86.dll
game using MMX & SSE & SSE2 for SIMD processing
enabled Flush-To-Zero mode
enabled Denormals-Are-Zero mode
--------- Initializing Game ----------
gamename: baseDOOM-1
gamedate: Jan 16 2007
Initializing event system
...473 event definitions
Initializing class hierarchy
...142 classes, 191092 bytes for event callbacks
Initializing scripts
Compiled 'interpolateShaderParm': 1355.1 ms
---------- Compile stats ----------

Memory usage:
Strings: 79, 9648 bytes
Statements: 67875, 1357500 bytes
Functions: 2109, 250532 bytes
Variables: 147376 bytes
Mem used: 2476344 bytes
Static data: 2277552 bytes
Allocated: 3281600 bytes
Thread size: 7068 bytes

...6 aas types
game initialized.
--------------------------------------
-------- Initializing Session --------
WARNING: idChoiceWindow::InitVars: gui 'guis/mainmenu.gui' window 'SNDBPrimary
' references undefined cvar 's_driver'
session initialized
--------------------------------------
--- Common Initialization Complete ---
------------- Warnings ---------------
during DOOM 3 initialization...
WARNING: idChoiceWindow::InitVars: gui 'guis/mainmenu.gui' window 'SNDBPrimary
' references undefined cvar 's_driver'
1 warnings
guid set to lC2fU1LyeEE
]condump test
Dumped console text to test.txt.

Is this something to be concerned about? Doom 3 is still crashing when I try to launch a mod from the opening screen. :evil:

The warning at the end is fine, just ignore it. The menus reference a CVar that only exists in the Linux build of the game.

As for your other problem the log you posted has been edited so I can't check through it now.

As for mods not working, have the ones you tried been updated to work with the new D3 1.3.1 patch that you're using?

Edit: I just checked with one of the Annihilation-X team; it is only for D3 1.3 right now. They're working on a 1.3.1 compatible version.

Edit Again: Apparently he was misinformed. There are no gamecode changes in A-X so it should work with 1.3 or 1.3.1. I downloaded it from here...

http://doom3.filefront.com/file/Annihilation_X;76651

... and got not problems starting it up.

@simulation

I have "AnnihilationX" and it also is crashing Doom3. I have reposted the "conDump test" for your review. But, not matter what I do, I just can't run any mods no matter what they are, without me getting a "Doom3 has to shut down, now" warning. I don't know what the hell going on. Before, when I first started to run into problems, there were other [different] issues happening..., now I can't even get to the point where the first ones ocurred without it crashing on me first. :oops:

I've looked at your condump and both lines are present and match the criteria I outlined originally. For all intensive purposes, Doom 3 appears to be up to date and it should run without issue.

That said, I'm assuming the game itself runs without any problems. It's only when you try to launch a mod that the game crashes.

And judging from your description you end up staring at a dialog like this...

Unfortunately, those dialogs are worthless. I couldn't begin to tell you what the problem is.

The only thing I can do is suggest an alternative way to launch mods. One that hopefully avoids whatever causes the crash.

That said, you can try making a shortcut to launch Doom 3 with the appropriate command line parameters to launch each mod.

General instructions are here...

http://www.modwiki.net/wiki/Startup_parameters#Windows

What you're aiming for is something like this...

Code:

"C:\Program Files\Doom3.exe" +set fs_game [name of mod folder]

Aside from that, I have no clue what to suggest.

rich_is_bored wrote:

Unfortunately, those dialogs are worthless. I couldn't begin to tell you what the problem is.

If you click on the "click here" you'll get some basic error info.

Under the "Error signature" section you'll see ModName. This is nothing to do with game "mods", it is the name of the windows module in which the error occurred. That may help you locate the source of the problem.

If ModName is doom3.exe or gamex86.dll then the problem is probably just doom related. If ModName is something else do a google search on the name and see what turns up.

Sim

simulation wrote:

rich_is_bored wrote:

Unfortunately, those dialogs are worthless. I couldn't begin to tell you what the problem is.

If you click on the "click here" you'll get some basic error info.

Under the "Error signature" section you'll see ModName. This is nothing to do with game "mods", it is the name of the windows module in which the error occurred. That may help you locate the source of the problem.

If ModName is doom3.exe or gamex86.dll then the problem is probably just doom related. If ModName is something else do a google search on the name and see what turns up.

Sim

I did do that and it was Doom3.exe... anyway, I really would like to thank you guys for being there during this "wonderful" moment, you really helped me to try to funnel this down. Someone told me that the 3.1.1 patch was the blame and not to use it, just use the 3.1 patch instead. Well, I followed his instructions with a new install and using the 3.1..., it doesn't crash anymore and I'm actually running mods now.

nice

im also avoiding that 1.31 patch, it totally screwed me
over too and im having no issues with anything with
"only" the 1.3 patch installed

vinnie_jones wrote:

nice

it totally screwed me over too

Can you be more specific? Would be useful to add your issues to the "knowledge base" of problems people have with 1.3.1.

simulation wrote:

vinnie_jones wrote:

nice

it totally screwed me over too

Can you be more specific? Would be useful to add your issues to the "knowledge base" of problems people have with 1.3.1.

There's really not much to add as far as details...except... don't use it.

lol very succinct there mac ^^
well to put it short, i dl the 1.31 patch,
patched my doom3 and then crahsboombang sorta,
nada worked, tried to run my doom modded stuff with fs_game
as per usual, crashed, tried to run vanilla doom by start-programs-doom3
ie NOT any desktop shortcut, crashed, tried to run doom via
an unaltered shortcut, crashed, thats about it, well that and
some language i cannot really write here, it ended with me
simply flushing doom from my computer as well as the
1,31 patch, now i reinstalled doom with 1.3 only,
dont wanna repeat meself but 1.31 wont get near my
doom again EVERRRR !

Thats 4 things now ill never have on my computer as long
as i can draw breath, patch 1.31, xp-lite, steam and vista :roll:

Well, five things actually, if i reinstall far Cry their 1.32 patch
(if you know FC you know how that one SUcK) wont be
in my registry either

thats MY 2 cents, or five cents if you will :wink:

Notice how idsoftware's site (and the doom 3 update system) says nothing about the new patch. I think thier waiting for that one moment to say "oh all teh mods is 1.3.1 now and all teh peoples having teh vista or updated stuffs" for them to acknowledge its exsistence.

vinnie_jones wrote:

then crahsboombang sorta

I was hoping for something a little more specific than that. Were you getting an actual crash like mac53 or just an error ("DLL API Error" is most common when using non-updated mods).

As for the lack of publicity on the patch, this is something I'm pursuing with id. If I hear anything further I'll post some news.

simulation wrote:

I was hoping for something a little more specific than that. Were you getting an actual crash like mac53 or just an error ("DLL API Error" is most common when using non-updated mods).

As for the lack of publicity on the patch, this is something I'm pursuing with id. If I hear anything further I'll post some news.

Your comment on the mods... now that I am not using the 1.3.1. patch, I have absolutely no problems with either playing Doom 3 itself or any mods,... none at all!

The only thing I can say here is, if you click here it will take you to the very first report of mine when I started to have these issues and trust me, there were numerous different types. Ranging from the crashing when I tried to play a mod, to numerous icons being locked in activate mode on my desktop. The date of this first post was 05/17!! and finally in June after walking away for about a week, someone helped with an idea that hit the target! I know I have re-installed the game atleast a dozen times within this time frame, not to mention that I even tried shutting down my anti-virus software and other background running processes down to just the os, and still had crashes and problems.

Here's what I think it is. 1.3.1. has been built with the 64 bit vista in mind and it's dumb-founded when ran on a 32 bit os. Doom 3 was built for 32 bits and so was all the patches up to 1.3.1. It's appearing to me, that it's a case of 'either, or'... not 'both' when it comes to software, especially in this case. Personally, I think that 1.3.1. is a beta and hasn't been tested properly. I'm not a pro here, nor do I claim to be a 'puter wiz', but there are times where it doesn't take a 'rocket scientist' to see what's going on, just one to explain it! I want to help with this and I'll do my best.

vinnie_jones wrote:

tried to run vanilla doom

What the hell is "Vanilla Doom"? I see it mentioned everywhere on forums, being used in different terms. Especially in the Doom 2 world. :oops:

for me "vanilla doom" means the original game, no roe and no mods whatsoever, just "pure"doom3.exe, i may be wrong on how others perceieve that use of "vanilla doom" but for me, thats the intent of the term

edit

I was hoping for something a little more specific than that. Were you getting an actual crash like mac53 or just an error ("DLL API Error" is most common when using non-updated mods). "

lil of both kinda, actually i have a hard time remembering EXACTLY
what happened, the term "seeing red" kicked in, sooooo ....

vinnie_jones wrote:

for me "vanilla doom" means the original game, no roe and no mods whatsoever, just "pure"doom3.exe, i may be wrong on how others perceieve that use of "vanilla doom" but for me, thats the intent of the term

That's it.

Anyway, as a general tip if anyone is having problems the first thing I would suggest is installing the game on a path without spaces. Sometimes they don't causes problems but other times they do, especially if you're into modding.

Mordenkainen wrote:

That's it.

Anyway, as a general tip if anyone is having problems the first thing I would suggest is installing the game on a path without spaces. Sometimes they don't causes problems but other times they do, especially if you're into modding.

You know... I thought about that and did this, first. Directory was
C:\Doom 3\... instead of the default in the program files, but the problem with that is that when the installer writes the program folder, it writes as Doom 3, [with space anyway]!

vinnie_jones wrote:

for me "vanilla doom" means the original game, no roe and no mods whatsoever, just "pure"doom3.exe, i may be wrong on how others perceieve that use of "vanilla doom" but for me, thats the intent of the term

Thanks "Vin"...

Youre welcome Mac53

lets form a "anti-patch 1.31 club" lol

Please report all (suspected) bugs related to the GAME here.

Make sure to also include your system specs as follows:

CPU
GPU (+used driver version)
RAM
Soundcard
OS
Overclocked anything - if yes, what if no then post: O/C no
Any special cvar settings you've made
FSAA - if yes, which setting

Server browser bug

I've noticed the ingame server browser has a few problems when attempting to sort or filter the list in any way, and actually misreports selected servers. If the server browser is left alone, each listed server is correct - but attempting to resort that list in any way, causes your client to connect to the wrong server.

For instance, I sort the servers by ping and attempt to join a local server with no players and an 80ms ping - I end up joining a server halfway across the world with players already in it, and an astronomical ping time.

This doesn't seem to be related to configuration or specific hardware settings, as I've seen this issue manifest on a wide number of systems. I suspect that it effects everyone, and have gotten lots of complaints about lag when on Australian servers by Americans who attempted to join more local servers. But for reference's sake, here's my specs:

CPU: Pentium 4 3GHz, 800FSB (Northwood).
MOBO: ASUS P4P800 Deluxe, 865PE chipset.
GPU: Sapphire branded Radeon 9800XT, 256MB model plus Catalyst 4.7's and beta 4.9's.
RAM: 1024MB (2x512MB) DDR400 Kingmax.
Sound: Creative Audigy 2 ZS Platinum Pro.
OS: Windows XP Pro SP1, up to date.

No overclockings. No real CVAR modifications. No FSAA used.

There's also the Snow bug? that may be a driver/overclocking issue, or whatever.
Here's a screenie of the problem:

Read this thread to find out more on that one:
http://www.doom3world.org/phpbb2/viewtopic.php?t=2851

eskimo roll wrote:

There's also the Snow bug? that may be a driver/overclocking issue, or whatever.

That looks like a video card problem. It can come from overclocking or overheating, but can also be a hardware fault with the card/chipset itself.

I have an issue which I originally reported as snow, but not like the screenshot above - it's more like static. Others are seeing this also, and from the limited knowledge about the issue, it appears at this stage to be an issue with the ATI OpenGL driver on certain cards.

ATI Radeon 9800 Pro (128Meg - currently using Cat 4.7 but tired many others, including Omega 2.5.88)
2.8GHz Pentium IV
1Gig DDR400 RAM
200Gig SATA Hard Drive
Gigabyte Motherboard (GA-8I series of some sort)
Windows XP SP1

Quote:

Basically, "use" in the PDA GUI is bound to "fire" instead of defaulting to the L-mouse button. Which is stupid and awkward, but not a game-breaker.

In other words, to click on something on the PDA screen, I have to move the mouse pointer to the right place, and then hit my "fire" key (which is "E" on the keyboard). In order to scroll through a PDA email, I need to hold down fire/E while moving the mouse.

They should have just had *all* mouse behavior revert to normal while using the PDA, but probably didn't anticipate/test with an unusual config. Bleh.

Thanks pjw for reporting this!

sizeDown command sizes viewport down, and moves it to the left lower corner, while it should be centered. This is obvious a bug.

Im using a:

ati radeon 9700 mobility 128 mb
512mb ram
sigmatel audio driver
2.8 ghz
windows xp
no overclocking
the only thing i tried was changing the cachemeg from 20 to 64 but i only got slightly longer gameplay (5-10 mins.)

constantly locking up at random points during gameplay.
i tried my standard drivers as well as the beta catalyst driver to no avail.
please HELP!!!

Link to Activision support page for Doom3

Link

_shank wrote:

Link to Activison support for Doom3

Should we consider that as a bug?
:lol:

BNA! wrote:

_shank wrote:

Link to Activison support for Doom3

Should we consider that as a bug?
:lol: