Strange Startup issues with UT3

Dec 21, 2006
169
0
0
Hey all. I recently downloaded the UT3 demo after hearing good things about it (namely that it is like UT99) and was looking forward to playing it. It installed perfectly, but when I try to play, it repeatedly and consistently gives me a "UT3Demo.exe has stopped working" notification.

My rig is as follows:
Sager NP2090
Core 2 Duo @ 1.8 Ghz (Stock)
2GB DDR2-667 RAM
8600M GT 512MB DDR2 Graphics Card

I am running Vista x64 Home Premium with 169.01 Forcewares (modded INF off laptopvideo2go.com).

I have tried updating .NET Framework 2.0 x64, updating audio drivers, and downloading some hotfixes as mentioned in the release notes.

By chance, I noticed this error message saved to my clipboard immediately after the program forcably closed:

Device does not support 1x32 FP render target format.

RaiseException() Address = 0x76353843 (filename not found) [in C:\Windows\syswow64\kernel32.dll]
CxxThrowException() Address = 0x73c88e69 (filename not found) [in C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8\MSVCR80.dll]
Address = 0xb22732 (filename not found) [in C:\Program Files (x86)\Unreal Tournament 3 Demo\Binaries\UT3Demo.exe]
Address = 0xe873ce4c (filename not found)

I have tried running it in compatibility mode for XP and as administrator, to no avail.

I'm willing to try any hotfixes, audio drivers, and updates as suggested. Also, the release notes mentioned adding -nosound to the command line when you run the program. I have no idea how to do this (I am primarily a Linux power-user, Windows confuses me). I tried adding it to the shortcut- after the "C:/Program Files(x86)/ ...." section, but either it did not work or this was not my issue.

Thanks in advance for any help.
 
Dec 21, 2006
169
0
0
This is my second reinstall. I'll give cleaning the registry a shot, though.

I would think it would just be a simple driver conflict; syswow64 sounds an awful lot like the WOW audio drivers I have installed. Still, can't hurt to clean out the registry...

Also, the "Device does not support 1x32 FP render target format" comment seems strange- I thought 32-bit precision FP was a feature of all modern graphics cards?

EDIT: Just wanted to let you guys know I fixed the problem. A simple driver cleaner run, plus an installation of 169.04 drivers cleared up a number of driver-related issues I've been having. Thanks for the suggestions, all.