I believe this is enough to give an idea of how this package worked for me running XPS Home with the latest Nvidia driver and version of DX9

Flight Ace wrote on Dec 23^rd, 2007 at 12:06pm:

Fr. Bill wrote on Dec 23^rd, 2007 at 12:41pm:



Actually Bill, this does trickle into DX9 as well. The following are seen in DX9  

Flashing textures  
Black flashing spikes  
Crash when accessing the menus  
Screen WHITEOUT or Washout  
Intermittent poor performance under certain conditions  


In SP2 with new shader code


The menu crash has come around in the last month or so and really hits 7xxxx series cards more than anything else because Nvidia is changing the 8000 drivers to suit Crysis, their primary DX10 target, and in doing so they are making headaches for those on older cores, and with other titles.



There have been a few Class Action lawsuits started. One is still pending and one went away quietly, after which Nvidia addressed the timing issue in Windows Vista, but it took 3 months and the threat of a lawsuit to get them to do anything about it.  

Further, with the last one filed in August Nvidia has all of a sudden started releasing drivers every week, somtimes twice a week which is unheard of in the industry unless they are under serious pressure to correct something.  *clue*



I am in the hardware testing circuit and although I do some software testing as the request may come up, my side-gig is to look over new cards, motherboards, processors, memory, drivers, etc. I am networked into several large corps like that and from my days at Boeing so I get a good portion of the dirt as it is dug up from both the testing groups and my contacts.

I don’t post threads like this just to blow off steam, and yes the 8000 series core was developed with design flaws that can never be fixed with a BIOS or driver. Every time they release new drivers to try and keep the original 8000 core runs floating in Crysis, they have started breaking other games.  

Some people will see it and some people wont. It will depend on the motherboard chipset, the motherboard drivers being used, other devices in the system which set different chipset reg keys as they are installed, the drivers and the application (game) itself, but none the less IT IS a NVIDIA ISSUE and not FSX or the other game programming causing the problems. The issues are seen on the first 2-3 silicone runs of the G80 core more than any other. I am sure the newer slug runs are probably working better and I would assume Nvidia has corrected all this in their next release.

Also, Intel is in a flubber with Nvidia over SLi licensing. Since Nvidia refused, Intel has refused to allow the microcode use in 680i which is why next gen processors will not run on those motherboards, and, is a warning shot for future technology if Nvidia continues to refuse. That one will probably get very interesting as it unfolds because two can play at that game



At any rate, all someone has to do is ask and without the challenging dialogue. I do not like being questioned that way, as no one would.  If I saw someone else being questioned as I was, especially someone I knew was in the business or 'loop', I would have done the same thing I did in this thread and addressed that tone with a equivalent  response.

Nick,

Thanks for this information. When I upgraded several months ago I elected to stay with XP until things settled in for Vista and DX10. My choice of an 8800 GTX, although it performs well with XP, may have been the wrong decision for running with Vista/DX10. I do hope Nvidia pulls a miracle out of the bag and get their differences ironed out with Intel. If this doesn’t happen, I may have to invest in another video card when I upgrade for FS11. As for my response to your original post, I do apologize for its tone. There are better ways to express one’s self.

Happy Holidays,

Flight Ace