XX: that's about what it looks like for me, too.

 

-----signature-----

Ok, who took control of my computer!!!!


Just kidding Same thing for me XX. Looks identical.


DtB


Edit:


Display Devices

---------------

Card name: NVIDIA GeForce 9500 GS

Manufacturer: NVIDIA

Chip type: GeForce 9500 GS

DAC type: Integrated RAMDAC

Device Key: Enum\PCI\VEN_10DE&DEV_0644&SUBSYS_13301462&REV_A1

Display Memory: 2539 MB

Dedicated Memory: 493 MB

Shared Memory: 2046 MB

Current Mode: 1600 x 900 (32 bit) (60Hz)

Monitor: Generic PnP Monitor

Driver Name: nvd3dumx.dll,nvd3dum,nvwgf2umx.dll, nvwgf2um

Driver Version: 7.15.0011.7740 (English)

 

-----signature-----

Does everyone having this problem run under windows XP? Anyone get it under Vista?

 

-----signature-----

I was able to reproduce the bug in Vista 32.

Vista 64x


DtB

 

-----signature-----

Interesting that it did not appear until the 9xxx series of cards. My GT 7800 had not artifacts.


Looks like a couple things changed between the 7xxx and 8xxx series of cards:





http://en.wikipedia.org/wiki/Unified_Shader_Architecture


I could almost see the problem being the new shader architecture, as it dynamically allocates computational units based on work load type. If AC expects the shaders to always be available, but the hardware is switching them between tasks...

 

-----signature-----

Xeon - it started with the 8 series... but unified shaders... intresting...


Not something I had considered, but this could be a very intresting clue..


edited bits....


I've passed this on to Frelorn to pass to tech at Turbine to look at... cross fingers...


Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie! Fyrie!


I need your expertise!

Do the Wine/*nix Nvidia drivers talk about using the unified shader?

 

-----signature-----

http://www.winehq.org/site/status_directx

http://wiki.winehq.org/DirectX-ToDo


I'll try to dig a little more, but WINE implements directX9 which only includes up to shader model 3. Shader model 4 (Unified Shader Model) is directX 10 only, and even then the developer has to opt into that shader model. The unified Shader Architecture is something that happens behind the scenes in hardware if I understand it correctly, but I could be wrong. It is important to note that new ATI cards use unified shader model as well. Someone correct me if I am wrong, but a game running under DirectX 9 in XP or Vista would not be promoted to run full blown Unified Shader Model/Architecture.


I'll report back if I can figure out any peculiarities as far as nvidia *nix drivers + wined3d go. If anyone else knows something, please jump on in. I'm more of a software than hardware guy.


Another thing to throw out there again if it hasn't been explicitly stated before. The 8000+ series cards are not very compatible with 8bit and 16bit operations/rendering. The cards typically substitute 32 bit implementations for these older operations. This is why Thief 1+2 won't work with the 8000+ series without a fan made patch which redirects function calls to older versions of the function.


Someone who is still playing the game may want to make a plea to this person to take a look at the issue:

http://timeslip.chorrol.com/ddfix.html

Fyrie - I'm wondering if the unified thingy was so cool that Nvidia just dumped everything thru it. I mean we all are chomping at the bit to run Vista... *blink* so DX10 isn't that important in the real world...


But they made a change towards the unified shader... and ATI uses a unified shader. how much you wanna bet they aren't the same


Once upon a time I talked about it might just be some calls that got thrown out or it was a "backdoor" way to make something happen that someone removed because "no one should use it".


The simple fact they put the unified shader in more than likely means they are coding their drivers to just use it, translating older calls on the fly, it does make some sense as Nvidia is well known for bad long term support of games. They get old and Nvidia drivers suddenly make them worse or not work at all. I patch a machine at work for WoW and with newer drivers the video card flipped out over and over. A little digging and something like 15 revisions of the driver backwards you get a stable driver for that card in WoW. We got an upgraded card for the machine and I put it in and XP flipped out. The screen got funky and I ended up heading here http://www.overclock.net/faqs/12466-info-nvidia-driver-cleaning-guide.html I followed the directions and even found some ATI drivers that were still lingering in the machine as well as various bits and pieces of Nvidia drivers.... I disabled the Nvidia control panel and tray icon stuff from loading and stripped it way down. Got it rebooted and installed newer drivers and no problems. I wonder how many are seen to be game problems that are problems from Nvidia not being able to cleanly remove their product when you update...


So I sometimes wonder when we've tried newer drivers if we really are trying the newer drivers as Nvidia likes to leave bits and pieces everywhere. There are setting buried in the trayicon files that are specific to a card and might result in a new card having issues...


but now my mind is wandering...


unifed shaders... anyone know anything or know someone who knows anything?

 

-----signature-----

Hmm, I'll try that NVidia driver cleaner when I get a chance and report if it makes any difference.

 

-----signature-----