Chalnoth

This problem appears to have been fixed in the nVidia 84.20 drivers, available as beta drivers at nzone.com

Well, I think the real hope is that nVidia will fix this issue shortly in an upcoming driver release. But it would be great if it were an option that could be set within nVidia's application profiles, just in case this issue crops up later.

Haha, yes With the NV4x series of graphics cards (GeForce 6x00, GeForce 7x00), the identification numbers that are used to recognize the cards are actually smaller than those for any previous nVidia parts. Most game developers, when detecting the graphics hardware, would assume that later parts would always have higher identification numbers. So, the game is looking at the identification number for your card, not recognizing it, and saying that while it knows it's nVidia hardware, it looks like pre-TNT hardware. Pretty funny, I think. Just one more thing that should be patched in the game, but not that big of a deal. I mean, the game really shouldn't assume low performance on an id number it doesn't recognize: it should assume high performance (or, at least, say that it doesn't recognize it).

No, you weren't supposed to edit that entry. You're supposed to enter a new one within the 0000 directory. If you are using an SLI system, it is imperative that you set that registry entry back to the original value (I'd set it back anyway, just to be safe). Once you are within the 0000 subdirectory that includes these application profiles, right click, then click new->DWORD value. Name it OGL_ThreadControl (as noted above), and set the value to 2. Hexidecimal vs. decimal does not matter for this case (since the number is less than 10).

For those of us with dual-core, KoTOR and KoTOR2 are still two games that exhibit problems with nVidia's dual-core optimizations. So, in the 81.98 drivers, nVidia implemented an option to disable dual-core optimizations. Unfortunately, the setting is currently a registry hack, and it's not documented properly in the driver release notes, so I'll list my own instructions here. First, in the registry editor of your choice, go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Video Here should be one or more {CLSID} entries. The release notes file on nVidia's site suggests a way to find the correct one that led me to the wrong one, so here's the way I did it. Systematically go through each one until you find one with a sub-directory 0000 that contains lots of entries. The first entries should all be entries related to game .exe files (game profiles). In my system, there was only one of these (and I have an SLI system), so I suspect if you have more than one, it is due to an unclean driver uninstall at some point. All other {CLSID} entries only had a couple of configuration settings. Now to enter the new DWORD values. To do this, make sure you are in the 0000 subdirectory of the proper {CLSID}, then right-click and click new->DWORD value. For OpenGL, name the DWORD "OGL_ThreadControl" and set the value to 2 (KoTOR and KoTOR2 use OpenGL). For D3D, name the DWORD "WTD_ExecModel" and set the value to 0 (this won't do anything for KoTOR, but just in case you find a D3D game that has a similar issue). You can view the 21st page of the 81.98 release notes for the official instructions. (edited for clarity)

But it could have been the best RPG I've ever played, if only it was finished. Early in the game, I felt that if the bugs were fixed, it would have been the best RPG I've ever played. But after finishing I'd say it was decent at best. If Obsidian spends the time and money to finish this game, they could turn a 3-star title into a 5-star title. But I won't hold out hope that this will happen, as they're sure to have moved on to NWN2. I just hope that they are given the freedom to finish that game (and, perhaps, think more about ways they can hold back their development fervor so that if they are forced to release too soon, they can put out a game that is actually finished, if smaller in scope than they originally desired).