Hey guys, I have been having a weird thing happen to me once in a while. Thankfully it doesn't happen often or I would probably throw my computer off a bridge and start over, but it happens enough that I thought I would post here and see if anyone has ever had this happen and/or know a solution.Here's the scenario. I'm flying the LDS 767 with ASA weather running off a networked connection and using either WOAI or UT2 traffic. I will take off from say KFLL or KMIA and fly enroute to KDFW, after an unspecified amount of time, maybe an hour or so, if I change views from the VC to the Spot View once in a while or access the FSX drop down menu to access the Map, I will suddenly get a drop in FPS from around the high 20's to low 30's, to around 4 to 6 FPS. In the process I will lose most of my VC textures on the inside of the plane and the outside of the plane will turn into this:Then the harddrive will go crazy trying to load something, maybe textures, I don't know, but I hear it running the the light flashing. Also I will loose the weather and get the underlying visability but the clouds disappear. In the picture above, prior to the plane turning into a heap of metal, I had a pretty solid layer of clouds a few thousand feet below me.Then, if I exit the flight and return to the main FSX menu the plane is still visable but looks like this:If I start a new flight the plane is still a mess. The only way to get everything back to normal is to stop FSX and restart a new flight. Needlesss to say after completing an hour of a 2.5 hour flight, I am usually not in the mood to start over.The funny thing is, I never BSOD or CTD. Also I have complete a 20 hour run of Memtest and also run other tools to verify my temps and overclock are inline. Like I said this doesn't happen often, but seems to happen on this particular flight a lot in either direction KDFW to KMIA/KFLL or KMIA/KFLL to KDFW. The other day I did an 8.5 hour flight from KFLL to SBGL Brazil and no problems. Had ASA running the whole time, switched views often, etc.I am stumped. Could this be either:1. A driver issue2. An issue with Navagraph Airac FMC data3. ASA causing an interaction problemI know that heat is not an issue since I am well cooled and ventilated. My specs are below in my signature.I look forward to any insight of feed back anyone may have on this.Regards

Hey guys, I have been having a weird thing happen to me once in a while. Thankfully it doesn't happen often or I would probably throw my computer off a bridge and start over, but it happens enough that I thought I would post here and see if anyone has ever had this happen and/or know a solution.Here's the scenario. I'm flying the LDS 767 with ASA weather running off a networked connection and using either WOAI or UT2 traffic. I will take off from say KFLL or KMIA and fly enroute to KDFW, after an unspecified amount of time, maybe an hour or so, if I change views from the VC to the Spot View once in a while or access the FSX drop down menu to access the Map, I will suddenly get a drop in FPS from around the high 20's to low 30's, to around 4 to 6 FPS. In the process I will lose most of my VC textures on the inside of the plane and the outside of the plane will turn into this:Then the harddrive will go crazy trying to load something, maybe textures, I don't know, but I hear it running the the light flashing. Also I will loose the weather and get the underlying visability but the clouds disappear. In the picture above, prior to the plane turning into a heap of metal, I had a pretty solid layer of clouds a few thousand feet below me.Then, if I exit the flight and return to the main FSX menu the plane is still visable but looks like this:If I start a new flight the plane is still a mess. The only way to get everything back to normal is to stop FSX and restart a new flight. Needlesss to say after completing an hour of a 2.5 hour flight, I am usually not in the mood to start over.The funny thing is, I never BSOD or CTD. Also I have complete a 20 hour run of Memtest and also run other tools to verify my temps and overclock are inline. Like I said this doesn't happen often, but seems to happen on this particular flight a lot in either direction KDFW to KMIA/KFLL or KMIA/KFLL to KDFW. The other day I did an 8.5 hour flight from KFLL to SBGL Brazil and no problems. Had ASA running the whole time, switched views often, etc.I am stumped. Could this be either:1. A driver issue2. An issue with Navagraph Airac FMC data3. ASA causing an interaction problemI know that heat is not an issue since I am well cooled and ventilated. My specs are below in my signature.I look forward to any insight of feed back anyone may have on this.Regards

A few days ago I was very surprised when I started getting invisible textures with some addon HD liveries for the Cessna 172 combined with HD clouds, except i didn't get textures going up down and all over the place! I was also using 24bit sound at 192,000 kHz which was part of the problem. My solution was obvious but I totally forgot about it, and would have been hard to find. Because I was using Tileproxy I split up half of my CPU for Tileproxy, and the other half for FSX. Since the OS and most processes run on the first 2 cores, I made Tileproxy run on the first two since it would not get bogged down, since its not a graphics intense program. Then I used AffinityMask=12 in the FSX.CFG instead of using 15 to use all cores. 12 is (1100) in binary and you read it backwards, therefore, the first two cores are unused (00) and the last to are run on FSX (11). Since almost nothing uses the last two cores and the OS is run on the first core mainly, FSX had MUCH better performance in terms of FPS and loading than just using all 4 cores or not using the affinity mask tweak at all. After switching to AffinityMask=12 I had NO problems whatsoever, and much much better performance. Try this out and if it works, spread the word! If it doesn't work for you, you can always remove the line or revert to how it was before! It's also good to delete and backup the FSX.CFG and let it rebuild, I have removed all tweaks except the fiber frame time fraction tweak (which I set to 0.15), and bufferpools. All other are unnecessary and just cause more problems. It took me a while to realize that the other tweaks were just making things worse, but I finally came to reality!Good luck! :(

I have this same problem whenever I reload a "complex" aircraft without exiting the sim. For example it happened today when I wanted to change a parameter in my flight in the XP Learjet. I don't use activesky or the navigraph FMC data(the plane doesn't have one). My guess is the problem is within FSX itself.I do use UT2 traffic, but I had this problem a few times before I got that add-onThere's a free file available from flight one for loading up complex aircraft, maybe give that a tryhttp://www.flight1software.com/files/FSXSafeStartup.exeGood luck

Hi cmpbellsjc,If i go anywhere near the 10,000 islands area of western Florida my FPS hit single figures. This happens anywhere that there is a lot of 'coastline' detail.I found that it was the wave effects. Try setting special effects to low in the FSX display options.Another idea that comes to mind is to reduce your userva setting (bcdedit), if your using this.David.

This ONLY ever happens to me when I use the Bufferpool tweak and it is set too high.

I used to get this with PMDG, and according to some good guys on PMDg forum the solution was to turn your sound card settings down from 24bit to some moderate 16bit sound setting. This fixed the PMDG issue for me.So the solution could be to get your sound card control panel out and lower the sound settings to 16bit CD quality or similar.

There was a thread on this a while back. I can't remember the outcome. I had this happen to me with the default baron. I find I have to use the 3gb switch with my Vista 32 bit system(and 4 GBs of ram).Bob

Has anybody tried the affinitymaks tweak I posted? It only takes a few minutes, is removable, and it actually works. The reason why is Core 0 (1st Core) is used by FSX to process the physics of the aircraft (with AffinityMask = 15 or no affinty mask tweak, ) and it also has to process a significant amount of data since the scenery is processed on the last 3 cores, and after the scenery is processed, it has to be sent to the 1st core (Core 0) so it will load in FSX. Core 0 and Core 1 (2nd Core) are the cores used by the Windows O/S and other processes, which makes the 1st 2 cores already saturated with cycles, threads, processes, etc. I think this causes FSX to be overloaded in a way (since the physics and everything else have to be passed through the 1st core) since the onboard sound decoders, and graphics cards use the 1st cores mainly (and sometimes the last two) to process data. Using AffinityMask = 12, moves FSX to the last two cores, and I guarantee you, you will get MORE FPS, LESS stutters, and you will ENJOY FSX better than ever before. Try it out and see, I promise you. The reason why is there are very little processes that get left over to the last 2 cores, so the last 2 are always free, and in the end you get better performance because the 3rd core which is free is processing the physics, is not saturated, and you'll most likely never see those invisible textures and wierd glitches again. Also remember to lower your bufferpools if its set to high. Bufferpools can reduce your FPS, and I found that out after many tests. I recommend setting it only to 5MB, and everything will load quickly. If you set it too high things may actually load slower because data has to be rewritten the memory every time, and you taking a chunk of your VRAM for things that stay in memory most often. 5-10MB should be enough, even the default of 4MB is more than enough in my opinion.To the person with the sound problems, set your sound as high as you can, use the affinity mask = 12 tweak, and see how it goes! Like I said, if it doesn't go well (for anyone) you can always revert back to how the line was or remove it in a matter of seconds. :( (BTW, I am using 24 bit sound at 192000 kHz, and since the affinity mask tweak, all my problems have gone!)Good Luck everyone :(

Thanks for all the replies guys.Gman - I hadn't tried the Affinity Mask tweak. Does that tweak apply to dual cores? David - For me its not the wave effects because this usually happens to me inland over land. Plue the wave thing I fixed a while back with help from the UT guys.I will take a look at the sound settings today and see what I can do there as far as lowering the sounds to 16 bit.I have the 3gb switch installed and also I am not using any bufferpool tweaks. I tried those a while back and noticed no improvements since I am using only a 512mb video card.

Thanks for all the replies guys.Gman - I hadn't tried the Affinity Mask tweak. Does that tweak apply to dual cores? David - For me its not the wave effects because this usually happens to me inland over land. Plue the wave thing I fixed a while back with help from the UT guys.I will take a look at the sound settings today and see what I can do there as far as lowering the sounds to 16 bit.I have the 3gb switch installed and also I am not using any bufferpool tweaks. I tried those a while back and noticed no improvements since I am using only a 512mb video card.

I doubt that it will work since the binary is 1100 and you don't have 4 cores. You can still try AffinityMask=12 and see what happens, but also try AffinityMask=2 and see how well it goes for you :). If all else fails lower your sound settings to the lowest frequency and bits.

I experienced that once, and re-installing the video card driver got rid it.

Is this a similar problem?http://forums1.avsim.net/index.php?showtopic=263194

Is this a similar problem?http://forums1.avsim.net/index.php?showtopic=263194

Yes, kind of. I never lose textures at the airports though. Every now and then I will get a blue square ground texture, but the main problem is what happens to the plane like in the screen shots I posted. Seems like it happens when I switch views a lot from VC to Spot or access the menu. Maybe I should just stay in the cockpit like in real life, lol.I am also running at 1280 X 1024 with a 8800GTS 512.On a side note, I looked at my sound setting and didn't see any adjustments for changing to 16bit sound, or 24bit sound for that matter.

Has anybody tried the affinitymaks tweak I posted? It only takes a few minutes, is removable, and it actually works. The reason why is Core 0 (1st Core) is used by FSX to process the physics of the aircraft (with AffinityMask = 15 or no affinty mask tweak, ) and it also has to process a significant amount of data since the scenery is processed on the last 3 cores, and after the scenery is processed, it has to be sent to the 1st core (Core 0) so it will load in FSX. Core 0 and Core 1 (2nd Core) are the cores used by the Windows O/S and other processes, which makes the 1st 2 cores already saturated with cycles, threads, processes, etc. I think this causes FSX to be overloaded in a way (since the physics and everything else have to be passed through the 1st core) since the onboard sound decoders, and graphics cards use the 1st cores mainly (and sometimes the last two) to process data. Using AffinityMask = 12, moves FSX to the last two cores, and I guarantee you, you will get MORE FPS, LESS stutters, and you will ENJOY FSX better than ever before. Try it out and see, I promise you.

I don't mean to hijack this thread but,I'm using 15 and the micro stutters are completely gone. The only problem I still have is that if I set the Autogen above normal I get the stupid crackling sound or periodically I may lose sound altogether. I will try 12 and let you know, btw I have a Q6600 so it's a quad.

lower your texture bandwidth multiplier to 40-60get rid of the buffer pool sectionreinstall your video drivers and then directxuninstall nhancer and set 3d settings through the nvidia control panelIf none of that works you have an overheating video card that should be shipped back, or possibly a power supply not powerful enough