LOL Oh trust me I have been there before, for years and years of tweaking FSX and FS9 but I am pretty good. PMDG 747, ASE, REX textures, UTX, in bad weather. Sure my frames are only 15 but I can accept that.

David,I'm testing a new solution for the shader tweak which allows you to use ported FS2004 AC :) stand by.... I need to fully test it.

Not a buffer pools thing, but I switched pc's from a qx6700 to a I920 and noticed that...Creating a 1gig after compressed .rar file took longer on the I920 than it did on the QX6700..I found my 2nd level cache was not correct in the registry..[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Memory Management]"SecondLevelDataCache"=dword:00000100Now the I920 is faster than the qx6700 was....

I'm testing a new solution for the shader tweak which allows you to use ported FS2004 AC :) stand by.... I need to fully test it.

Hey *******, I've used your shader tweak just as an added precaution to the corrupted/missing textures issue but since I did it, aircraft on VATSIM become invisible with only the lights visible. Could this be the problem you've referred to? I'm using FSINN client. World of AI Planes.Thanks!

Not a buffer pools thing, but I switched pc's from a qx6700 to a I920 and noticed that...Creating a 1gig after compressed .rar file took longer on the I920 than it did on the QX6700..I found my 2nd level cache was not correct in the registry..[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Memory Management]"SecondLevelDataCache"=dword:00000100Now the I920 is faster than the qx6700 was....

Interesting.... how more 'fast' was it? that value is set to 0 by default in Win7, and I googled it and seems Vista and Win7 do NOT set L2 Cache properly... so. assuming is FP intensive, it should benefit from it.. I'll test later.

Hey *******, I've used your shader tweak just as an added precaution to the corrupted/missing textures issue but since I did it, aircraft on VATSIM become invisible with only the lights visible. Could this be the problem you've referred to? I'm using FSINN client. World of AI Planes.Thanks!

Yes, its possible... all 'ported' and/or old aircraft will show with missing textures

I followed this thread for the first 10-13 pages but I must admit haven't kept up with my studies. I do know that it was proven early on that it probably doesn't relate to my system.Nonetheless, have there been any breakthroughs with I7, W7, 64 bit, 1GB systems that are suffering from video corruption at the end of flights in the form of black screens and disappearing textures? If so, would anyone please summarize?

Not a buffer pools thing, but I switched pc's from a qx6700 to a I920 and noticed that...Creating a 1gig after compressed .rar file took longer on the I920 than it did on the QX6700..I found my 2nd level cache was not correct in the registry..[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Memory Management]"SecondLevelDataCache"=dword:00000100Now the I920 is faster than the qx6700 was....

Pure Myth, and a very old one.Since this has been passed around since about the time of King Arthur which if this was true surely would have been covered by an update by now...1.The default value of 0 tells Windows to auto-detect the correct value, many other settings in the registry work this way, however it is an old legacy key anyway.2.This setting also is for very old chips with off die type direct-mapped cache of which AMD or Intel have not made in a long time so unless your using a proccessor about a decade old (older than P-II) it is useless.http://support.microsoft.com/kb/183063Also from http://technet.microsoft.com/en-us/library/cc938581.aspx:Do not change the SecondLevelDataCache entry Some third-party sources have erroneously reported that modifying the SecondLevelDataCache registry entry in HKEY_LOCAL_MACHINE\System\CurrentControlSet \Control\Session Manager\Memory Management can enhance system performance. The second level (L2) cache is recognized by the operating system and is fully utilized regardless of the setting of this parameter.

I followed this thread for the first 10-13 pages but I must admit haven't kept up with my studies. I do know that it was proven early on that it probably doesn't relate to my system.Nonetheless, have there been any breakthroughs with I7, W7, 64 bit, 1GB systems that are suffering from video corruption at the end of flights in the form of black screens and disappearing textures? If so, would anyone please summarize?

You could maybe use just the in game AA for now without using inhancer, or turn other settings down so as to not force the issue until a reliable solution is found.Many apps are suffering some of the same ills to various degrees from the WMMD version of win7-64 as well as Vista, effecting 3D creation, Audio creation, and other games as well. It is surprising the lack of attention to this.Might explain NV breaking the control of FSX filtering from the control panel and forcing in game only modes. I have passed my complaints on to MS and encourage everyone to do the same...this is killing our game.

Well... I'm not one for subjective measurements.. so I tested this one and am munching some crow :-)No real difference in performance... set to 0, 64, 256 ....I sure would have lost big in Vegas on this one... Back to the drawing board... I feel like Clyde Crashcup .... ( probably got that one wrong too )Windows 64 bit I920 ....

Pure Myth, and a very old one.Since this has been passed around since about the time of King Arthur which if this was true surely would have been covered by an update by now...1.The default value of 0 tells Windows to auto-detect the correct value, many other settings in the registry work this way, however it is an old legacy key anyway.2.This setting also is for very old chips with off die type direct-mapped cache of which AMD or Intel have not made in a long time so unless your using a proccessor about a decade old (older than P-II) it is useless.http://support.microsoft.com/kb/183063Also from http://technet.microsoft.com/en-us/library/cc938581.aspx:Do not change the SecondLevelDataCache entry Some third-party sources have erroneously reported that modifying the SecondLevelDataCache registry entry in HKEY_LOCAL_MACHINE\System\CurrentControlSet \Control\Session Manager\Memory Management can enhance system performance. The second level (L2) cache is recognized by the operating system and is fully utilized regardless of the setting of this parameter.

Well... I'm not one for subjective measurements.. so I tested this one and am munching some crow :-)No real difference in performance... set to 0, 64, 256 ....I sure would have lost big in Vegas on this one... Back to the drawing board... I feel like Clyde Crashcup .... ( probably got that one wrong too )Windows 64 bit I920 ....

Clyde Crashcup lol!I eat Crow from time to time. its not that bad, kinda taste like Chicken....

** DISSAPEARING TEXTURES/BLACK SCREEN PROBLEM FINAL SOLUTION **I was planning to write a new post, but due to Ryan being so kind to 'follow up' on the PMDG 'official' thread, I guess it was best to originally post it there. I'm 110% confident, that this proposed solution 'solves' the Dissapearing/Skeleton VC Textures.You can start by adding this in the [GRAPHICS] section of your fsx.cfg file. also, the 'theory' about sound being responsible, is partially correct, it was totally on track on what (part) of the problem was... :) the 'sound' plays a huge role here.. specially, the sampling rate.[GRAPHICS]SHADER_CACHE_VERSION=1 // it 're-builds' the Shader Cache (good to do on every fsx.cfg change) just enter a random number (versioning)HIGHMEMFIX=1STALE_BUFFER_THRESHOLD=2147483647 // (2048 megabytes)[Display]TEXTURE_BANDWIDTH_MULT=400 // Default is 40 (made 10x faster so we dont end up filling the stale buffer which is also used by the sound card)TextureMaxLoad=30 // Default is 3 (same as above, we need to make video texture transfers *fast* so it won't affect low latency devices)[sOUND]SOUND=1SOUND_QUALITY=2SOUND_LOD=0Also, make sure the sampling rate/quality, for your 'sound card' is set to the 44100 sampling rate (CD Quality) you change this in your Sound Control Panel. 44100Hz is the format used for most .wav files in FSX, when a 'wav' needs re-sampling it takes 'time' which you can't afford to loose in our case.I know some of you have never seen 'some' of the above settings ever, but if any of you guys (reading) are ex-MS employees or were involved with the development, you can confirm to the group what I'm saying ;)The root cause of the problem is a DPC latency issue + stale buffer saturation with the Video and Sound card in your system, the above settings 'balance' things so both play well together. (and for the record, I DID NOT USE DPC Latency Checker)For those that used my 'shader tweak' you can forget about it... you don't need it anymore after this, also ALL FS2004 ported A/C work with no problems. Thanks John, I used your Kyte for testing :)The only 'caveat' is that now, ANYTIME a texture object or building 'dissapears' you'll get an application crash in the FSX API.dll module when you switch windows, thats NOT bad, it just means, you have now a WARNING! I'll provide aditional info when enough people test this solution, this is ONLY TESTED on Windows 7 64-Bit and FSX with SP2 installed. (don't know if it works for acceleration, SP1 or RTM) have not yet tested under Vista or XPone more thing.. this is NOT the solution to the 'black screens' caused by Windows TDR (Timeout Detection & Recovery) that problem is caused for OTHER reasons I've mentioned in other posts that nobody seems to read or believe (its due to the command buffer being flushed, for excessive ammount of draw calls made to the D3D API and the video card not being able to keep up reading the ring buffer fast enough) also, this is NOT related to 'mouse clicking' the VC and getting and error, that is yet ANOTHER error... (the one people fix with UIAutomationCore.dll) Enjoy people... and remember, *IF* you get an API.dll crash, don't worry... this solution can be tweaked to your particular 'setup' and make it work... the HIGHMEMFIX=1 is what 'triggers' the API.dll error, by default this value is set to 0, so, FSX (very cleverly) doesn't crash!! but, starts making stuff dissapear and gets unstable (and eventually crashes later on) specially when on final flying VATSIM ;)As for the Black Screens caused by the Windows TDR (Timeout Detection & Recovery) I'll later post a solution to that as well... I have more than 3 weeks researching this, and I'm exhausted.... Sorry I posted this to the thread that refuses to die, but.. I 'think' its important :)

** DISSAPEARING TEXTURES/BLACK SCREEN PROBLEM FINAL SOLUTION **I was planning to write a new post, but due to Ryan being so kind to 'follow up' on the PMDG 'official' thread, I guess it was best to originally post it there. I'm 110% confident, that this proposed solution 'solves' the Dissapearing/Skeleton VC Textures.TextureMaxLoad=30 // Default is 3 (same as above, we need to make video texture transfers *fast* so it won't affect low latency devices)

Nice work and hope for success here!TML= is the max size of textures FSX will load, default max is 1024x1024, high rez 2048x and higher 4096, so what is 30? we are forcing a default lower res texture? rendering all the highres Clouds, VC, and other HD textures as low res for this to work?I read in the other thread that you are no longer using the FSDT JFK, is that still correct?Also what BP settings are you using and what Video card (just to clarify your new ATI or the old NV).Finally what screen res and filtering settings or it does not matter?

Hi,As far as the Timeout Detection and Recovery of GPUs through WDDM, the following Microsoft registry edit has worked for me.TDR Link: http://www.microsoft.com/whdc/device/displ...dm_timeout.mspx

As for the Black Screens caused by the Windows TDR (Timeout Detection & Recovery) I'll later post a solution to that as well... I have more than 3 weeks researching this, and I'm exhausted.... Sorry I posted this to the thread that refuses to die, but.. I 'think' its important :)

As far as the Timeout Detection and Recovery of GPUs through WDDM, the following Microsoft registry edit has worked for me.TDR Link: http://www.microsoft.com/whdc/device/displ...dm_timeout.mspx

Hi Mike; I looked at this, but it's only applicable for Vista users - not Win7 - and in fact the Win7 registry doesn't seem to have these keys at all.. did I miss something here?

Hi *******,Where do I find those "sound card" settings in order to follow the tuning recommendations you made? My sound section in the control panel is a lot more basic than that, and I can not find any other. Stephen

Hi *******,Where do I find those "sound card" settings in order to follow the tuning recommendations you made? My sound section in the control panel is a lot more basic than that, and I can not find any other. Stephen

Stephen, really quick to do:1) Right click the 'little' speaker next to the system date in the lower right corner of your screen and select the option 'Playback Devices'2) Select the 'device' you want to modify (I guess, it should say speakers or your sound card name) and right click it to see its properties3) You'll now see a series of 'tabs' depending on your 'sound card' but the most important ones are: Advanced & Effects/Enhancements.In Advanced, you can change the sampling rate.in effects you can 'disable' all sound card effects... this gives a little bit more CPU to FSX, so I suggest you disable ALL kind of 'special' sound effects there isan option that says: DISABLE ALL EFFECTS