UT3 who's getting it? - Page 2

{DvT}JonahHex · 11-19-2007, 10:16 PM

hmmmmm

I've spent the last 10 months building/tweaking a new puter specifically for playing UT3.

Now I have to get the game too???

{DvT}Reckless · 11-20-2007, 08:38 PM

I will be installing this later tonight.

{OF}Erad · 11-20-2007, 08:47 PM

Tried UT3 in Win XP. 1920x1200. All settings maxed. Ran average of 84 fps. Colors seemed weird.

Loaded it on Vista: 1920x1200. All settings maxed. Ran average of 84 fps too, but it looked cleaner and smoother than XP did.

Haven't tried Internet play yet as my DSL is acting up, and they are moving me over to FIOS 7mbs service on the 27th. On the old DSL I can't find a server under 140 ping.

Soul · 11-21-2007, 08:07 AM

deja vu

{OF} achilles · 11-21-2007, 11:11 AM

Got it!
So right now I've got Cod4, Crysis and Ut3 all demanding time.

Crysis is gorgeous and the game ( imho) swings between boredom and heh! that is cool.

COD4> I love it. Nicely developed single player and the multi is very well done.

Like Barney I'm a Unreal fan. I think the Gui is horrid. My pings suck. Sure is pretty though and somehow reminds me of the first UTon first play.

{DvT}JonahHex · 11-21-2007, 04:34 PM

I spent most of yesterday afternoon fighting with drivers: BSODs, freeze-ups, reboots. Both sound-card and video drivers in both XP Home x32 and Vista Home Premium x64.

Finally uninstalled my SB X-Fi card (from Windoze, not physically from the box) and disabled it, then enabled the mobo onboard sound and tried it. I'm playing now altho I still get freeze-ups.

In Vista I keep getting the "nvlddmkm stopped responding" error. It recovers, then almost immediately errors out again - rebooting fixes it...until the next time. I'm probably getting the same problem in XP, it just doesn't report the error as such. The nVidia forum are rife with threads regarding this error in various games and Demos - Crysis and Bioshock to mention the two (demos) that I have. I have not had this problem prior to UT3.

Regardless, the game is awesome! I'll get the driver probs fixed sooner or later (or nVidia will). In meantime, running everything cranked up all the way, I haven't seen framerates less than 100 (after unlocking them) and when they said that the Demo used 1/2 textures, I believe it. The maps aren't bright and pretty, as many 2K4 maps were...they are more remenicient of U1 maps ... with 10x the detail. If you'll recall, the graphics in Unreal were unreal. I'm not sure that they have recaptured that ... I'm not sure it is possible to do ... but whereas I was somewhat concerned by the graphics in the UT3 Demo, the Retail is everything I was hoping for.

{OF}Erad · 11-21-2007, 04:47 PM

{DvT}JonahHex, try uninstalling the Video Drivers, run a driver cleaning program and then installing the latest BETA Drivers. I had the same issue with other games, and the only way I fixed it was completely uninstalling the nVidia Drivers, then loading the latest Beta Drivers. It had something to do with the left over files from the "OLD" nVidia Control Panel. Ever since I did that, no issues at all.

{OF}MillerTime · 11-21-2007, 05:53 PM

I'll prolly pick it up Friday nite or Sat. so beware

{DvT}JonahHex · 11-21-2007, 08:45 PM

Quote:

Originally Posted by {OF}Erad

{DvT}JonahHex, try uninstalling the Video Drivers, run a driver cleaning program and then installing the latest BETA Drivers. I had the same issue with other games, and the only way I fixed it was completely uninstalling the nVidia Drivers, then loading the latest Beta Drivers. It had something to do with the left over files from the "OLD" nVidia Control Panel. Ever since I did that, no issues at all.

Good suggestions. After posting above, I went to the nVidia forums and found this post, which tells how to manually implement your suggestion - I've used Driver Cleaner before and don't like it so the manual approach was good. Possibly equally important is the fact that I had checked for new Beta drivers earlier and there were none...just 169.09, which I was already using...but after cleaning the old drivers (169.09) out, I checked again for new ones and found 169.12...d/l'd and installed them.

Since doing this (in Vista x64, haven't done anything with XP yet), the "driver not responding" prob seems to have gone away --- or maybe not --- while I've played (campaign and instant action) since installing 169.12, there were a number of times (random it seemed, and not terribly often) that the game would freeze for a second or two, then resume from where it froze. Was this the "driver not responding and has recovered"? ...and it really did recover? I don't know. However, it was infrequent enough, and such an improvement over rebooting, I can live with it...at least for now.

It's getting better and better all the time.

{OF}Flying_Dutchman · 11-21-2007, 08:56 PM

I will be getting it just cuz. Demo didn't blow me away, but I have every darn Unreal game since the beginning.

Here's crossing my fingers