July 19, 201114 yr As my first 570 GTX striked working i took the change to upgrade the driver, too. With my setup of NI (second picture) the new driver 275.33 64bit results graphic issues (first picture), triggered by switching between VC and 2D panels.First i thought the second 570 card is dying, but this driver seems to be the causer.Went back to 258.96 WHQL and everything is fine again.Maybe this helps anyone when having issues like this.
July 23, 201114 yr Paul,Thanks for the info. This issue was raised in this thread http://forum.avsim.net/topic/337808-strange-graphics-issue/It effects my setup to. Maybe I'll revert to the older drivers, but the problem isn't that bothersome at the moment.Raoul Raoul La Rose
July 29, 201114 yr I had this issue with the MD11 and the LD767.I was told in another thread to put HIGHMEMFIX=1 in my FSX.CFG file. Please read: From the sticky post at the top of this forum:http://forums1.avsim...howtopic=281538[GRAPHICS]HIGHMEMFIX=1Fixes errors with texture addressing modes in WDDM1.0 and 1.1 when using a lot of video memoryThe HIGHMEMFIX=1 you see above, fixes a bug in the FSX engine on how it handles texture addressing modes (Wrap,Clamp) and initial render states on single pass shaders, it will completely prevent textures, buildings and entire cockpits from dissapearing! this 'bug' is triggered when there is a high video memory usage situation. so, enjoy :) this is my way of giving to a community that has given me so much over the years. I removed the UIAutomationcore.dll just in case as it too has been linked to this issue. "I am the Master of the Fist!" -Akuma
July 30, 201114 yr Author I had this issue with the MD11 and the LD767.I was told in another thread to put HIGHMEMFIX=1 in my FSX.CFG file. Please read: I removed the UIAutomationcore.dll just in case as it too has been linked to this issue. thx for your information, but i am familiar with this two neccessary stability tweaks for fsx, they are still on board and do not causing the above shown issues. It was the driver for sure. Since i have replaced the 277.33, it never happened again. (i didn't change my Nvidia Inspector settings meanwhile, so it should be clear what's causing this)
July 30, 201114 yr OK... Like I KNEW that as you had not posted that anywhere.This is why I'm never going to attempt to post any help again.These forums are starting to suck worse than WoW's. "I am the Master of the Fist!" -Akuma
July 30, 201114 yr Author OK... Like I KNEW that as you had not posted that anywhere. was not neccessary! Which part did you miss from that line?: self quote initial post: Went back to 258.96 WHQL and everything is fine again.
Create an account or sign in to comment