Bogotron
Members-
Content count
9 -
Joined
-
Last visited
Never
Everything posted by Bogotron
-
If you disable FMVs the game works fine in other resolution as well. I wonder when Eidos will fix this bug, its not like its the first time its appeared.
-
I've been looking for a solution to this problem as well, but nothing has come up yet. But cheer up, after about 20 hours of play you won't notice it anymore.
-
No SMP problems here either. Now I can let rc5 run all day.
-
Disabling rc5 sure worked, but its kinda lame way to fix a bug. But it'll have to do for the time being. Thanks.
-
You are far from alone. I've got the same problem om my BP6 and DDR GeForce. I also had the same problem with my old PCI TNT, so it is definetly a driver problem. I use dxdiag to test whenever I get my hands on a new w2k build og nvidia drivers. And so far it always locks up during the ddraw (fullscreen) and d3d (only fullscreen is tested). Now, since the non-fullscreen ddraw works, I'm beginning to suspect that it has problems with switching to fullscreen in SMP mode. Also the mediaplayer crashes quite often (almost always) when I fullscreen it, with just reinforces my suspicion. I want my second CPU back! ------------------ Paul Currie
-
Mine used to go belly-up if I skipped songs too quickly under build 2128, but I haven't been able to reproduce this under 2151. ------------------ Paul Currie
-
After trying Detonator 3.34, 3.52 and 3.53 under rc2 (2128) both with and without the newest DirectX 7.0, directDraw locks up (OLG and D3D works great). The screen goes blank and no input devices work at all (keyboard, mouse etc.). The computer is still reachable from the network and stuff but its kinda useless to me that way. I have dual 366 Celys at 523, but I've tried them at 366 with the same results. The only other source of the problem I can think of is my PCI TNT. Anybody have any ideas of what to do (except run older drivers)? ------------------ Paul Currie
-
My 366 Celys go all the way up to 605MHz under windows 98 (full stresstest etc.), but only up to 510MHz under W2K. When I overclock too much I get the bluescreen you mention. Also the most sensitive applications to overclocking on my machine is Aliens Vs Predator and misc. openGL screensavers (Q3test runs flawlessly at 550MHz, but the computer locks up after 10 minutes of screensaver ). Try clocking a little lower, or maybe better heatsinks. I'm waiting for Alphas, so hopefully I'll get all the way up to 550... ------------------ Paul Currie
-
Back in the good old days (one week ago) I had a P233 MMX... Lots of stuttering on the sound. With a 366 Celeron the stuttering was almost all gone, and with the same cely at 550, no stuttering at all. Not really much help if you are on a budget, but one solution at least. ------------------ Paul Currie