NotebookForums.com › Forums › Notebook Manufacturers › Alienware Notebook Forums › Alienware General › The "Doom3 Tech Support" Thread
New Posts  All Forums:Forum Nav:

The "Doom3 Tech Support" Thread - Page 2

post #21 of 39
Okay, the 4.7 catalyst (i.e., Omega 2558) fixed my random crash and/or freeze issues.

Problem is, Doom3 doesn't support joysticks, which is what I use for FPS gaming (I know, I know, but I own with it, always have). So, I have to use a keyboard/mouse emulator program to make it work. This is sad because id always was steadfast in their support of the minority joystick crowd; this is the first game they've released without support out of the box
post #22 of 39
Maybe in a future patch or update they will include joystick support... but I'm doubtful.
post #23 of 39

Help with drivers and Doom 3

Hey every1
Just got my lappie a week ago and got Doom 3
It randomly freezes and i don't know what to do
I tried the newest Omegas before and none of the games even fit the screen
Any help would be ........helpful
post #24 of 39
Quote:
Originally Posted by RADEARM
Hey every1
Just got my lappie a week ago and got Doom 3
It randomly freezes and i don't know what to do
I tried the newest Omegas before and none of the games even fit the screen
Any help would be ........helpful
So it sounds like the new Omegas are working for you, but the screen size is small. Easy fix (thanks to Craig):

right click desktop, properties, settings, advanced, displays, click panel, and check where it says, 'scale image to panel size.' That should fix it.
post #25 of 39
Terraform. Have you tried keyboard only? Using the a/z keys to look and arrow keys to move. It's the last resort. I don't like using the mouse either. Since you don't like the mouse, I thought you should try it.
post #26 of 39
m739pd: thanks for the info; I can use the k/m or variants of them, but I just don't like to. Thankfully, someone in the joystick community made a keyboard/mouse emulator program that I can use to bind the stick and its buttons to anything the k/m can do.

I changed 'seta image_cacheMegs "256"' to "512" and also changed 'seta image_useCache "0"' to "1" as I read somewhere the latter must be 1 for the former to work. Either or one of these caused a CTD so I switched them both back to 256 and 0. Anyone know for sure if we should change the 0 to 1 and/or make cacheMegs half your total RAM?
post #27 of 39
Quote:
Originally Posted by TerraFORM
So it sounds like the new Omegas are working for you, but the screen size is small. Easy fix (thanks to Craig):

right click desktop, properties, settings, advanced, displays, click panel, and check where it says, 'scale image to panel size.' That should fix it.
Thanks a lot TerraFORM for the reply
I'll try that out
post #28 of 39

Nvidia + Doom3 Problems?

I currently have the Omega 1.5672 drivers installed. I have tweaked the heck out of Doom 3 but I still can only get an average of 15 fps on the time demo. Anyone having the same issues? I have it on single display. I'm running out of options... It runs great in UT2k4... Off to install the original AW drivers...

post #29 of 39
What if my only problem is being brave enough to play it at night?
post #30 of 39
Anyone having issues with Nvidia 5600 and Doom 3? I can only get an average of 15FPS on the time demo. I currently have the Omega 1.5772 drivers installed and configured for a single display. Well I guess I can try the original AW Drivers...

Anyone have any other suggestions??

post #31 of 39

any luck with the nvidia 5600 ??

mine runs like crap, hello alienware, new drivers please, and make them signed by microsoft so i can play halo.
post #32 of 39
I don't know if it will help yall much, but us Sager users are using the Omega 4.5 drivers with much success. Our old default Sager ATI drivers aren't working and are causing BSOD's and other random crashes with Doom 3. We haven't moved up to 4.6 and 4.7 as those cause DVD playback glitches. Awaiting word on 4.9. As for the Nvidia card users, best of luck to yall, but the Omegas may be the only hope for you too.
post #33 of 39
Quote:
Originally Posted by TerraFORM
m739pd: thanks for the info; I can use the k/m or variants of them, but I just don't like to. Thankfully, someone in the joystick community made a keyboard/mouse emulator program that I can use to bind the stick and its buttons to anything the k/m can do.

I changed 'seta image_cacheMegs "256"' to "512" and also changed 'seta image_useCache "0"' to "1" as I read somewhere the latter must be 1 for the former to work. Either or one of these caused a CTD so I switched them both back to 256 and 0. Anyone know for sure if we should change the 0 to 1 and/or make cacheMegs half your total RAM?
I would not set the cacheMegs settings to anything higher than 1/4 of your RAM; this is because the cacheMegs setting just tells Doom 3 how much of your RAM it can use for compressed images and setting it to half of your RAM just leaves less space for the game itself. Also, the 'seta image_useCache' line must be set to 1 to enable the cacheMegs line.

BTW, does anyone know how to enable Triple Buffer in Doom 3?
post #34 of 39
Try this...

All of those who are experiencing crashes in Doom 3, turn your AGP setting down to X4 (I think this only applies to ATI owners). Not saying this will work, but I've had trouble with my ATI 9700 at agp X8. Seems there is a bug with the ati drivers and the agp drivers. Give it a whirl and see if it makes a difference (you shouldn't see any performance loss).
post #35 of 39
Does anyone from the aw forums know why this is? No one else seems to know. There is something wrong with this picture. I have a 128 meg ati 9600. It only shows 64. Why is this?

post #36 of 39
Quote:
Originally Posted by DELL-Spiike
Does anyone from the aw forums know why this is? No one else seems to know. There is something wrong with this picture. I have a 128 meg ati 9600. It only shows 64. Why is this?

Maybe it's showing the avalible memory?
post #37 of 39
Doom 3 has just detected your video RAM incorrectly(this happened to me too). Just type seta com_videoRam 128 into the console, your Doom.cfg file, or your AutoExec.cfg to fix this.
post #38 of 39
Thanks aliendude. Such a simple fix for an issue that has been bugging me for quite some time. It still says 64 in the console, but I'm assuming that command forces doom to see it as 128.
post #39 of 39

Doom 3 Timedemo Score

I was curious as to what everyone's scores are when you run the in-game benchmark. I ask, b/c I think mine sucks. At 800 X 600 I get a score of 21.5, the next higher setting it is like 15 which is unplayable. Post your scores!
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Alienware General
NotebookForums.com › Forums › Notebook Manufacturers › Alienware Notebook Forums › Alienware General › The "Doom3 Tech Support" Thread