...only happens when I'm looking at "wing view" for more than 5 secs then switching back to VC. VC textures, including view of outside, seems to take a good 2-3 seconds to load and vice versa, when switching back to "wing view". any suggestions? mostly with payware planes. (Airbus X, NGX....)

Hi,

 

Have you followed Word Not Allowed's Software and Hardware Guide? If so, you shouldn't be experiencing these kind of issues, especially considering that you have a powerful SB OCed system.

yes i did follow it line by line, only thing i changed is my FFTF = 0.18 since I could see blurries when I use 0.1. I also use the windowed mode tweak because I often switch from full screen to windowed mode when opening programs during flight and without it, FSX crashes when I switch modes. I'm trying to think if there is anything that may be causing a bottleneck but I still cant think of one. Either than that, everything runs silky smooth and 95% of the time I always get 30FPS locked even on EGLL with the NGX and 40% AI.

 

...just tryin my luck maybe some of our members here experienced the same problem and can share their inputs. Thanks!! ^_^

 

 

(Re: affinity mask, I set it at 14 with HT off but when I opened task manager, I could see windows having it on all 4 cores instead of core 1-3. Is that normal?)

affinity mask, I set it at 14 with HT off but when I opened task manager, I could see windows having it on all 4 cores instead of core 1-3. Is that normal?)

 

Affinity mask setting done in fsx.cfg affects only FSX and nothing else. So it is normal that task manager shows you 4 windows for each of CPU's cores. But while FSX is running only three windows (core1, core2, core3) should show you high cpu load level as result of working FSX, on the first one (core0) you should see only cpu load beeing result of system and other than FSX applications running.

I am having the same issue switching views and like you have followed all the tweaking guides. My frame rates are good and performance isn't choppy at all, but I get a 3 to 3 second delay when going from outside views back to the VC ( http://i1045.photobucket.com/albums/b458/cherokeecruiser2002/FSX/SwitchingViews.jpg) . I didn't have this problem on my old system which had an ATI 5850 GPU. Now I switched back to Nvidia (GTX 660Ti) and I get this. Fresh install Windows 7 Home Premium x64 with 304.87 drivers and recommended Inspector settings. Problem is more pronounced using the PMDG 737 NGX.

too bad for us , but good to know im not alone on this. hope someone with similar experience would be able to shed light on this.

I understand why users sometimes like to question "the status quo". Unfortunately, sometimes this leads them to be skeptical of our reccomendations and end up on an AMD GPU. Then, later on down the road, we get complaints on the forums like "What AA do I use?" "Driver Crash" "Can't Clean Driver AMD" etc

 

Honestly, if you want to get an AMD GPU, fufill your heart's desire. But, don't get frustrated when you have issues while running within the FSX sim environment.

I get a 3 to 3 second delay when going from outside views back to the VC ( http://i1045.photobu...tchingViews.jpg) .

 

I had similar problem - after switching views (outside view > VC) I was getting such results:

Cessna VC - http://prologos.pl/fsx/cessna_vc.jpg

F/A-18 VC - http://prologos.pl/fsx/f18_vc_m.jpg

 

After some investigations I found that first core of CPU (core0), which is responsible for FSX scene "rendering" was overloaded (core0 load was over 95% or even equal 100%).

 

First solution was adding to fsx.cfg this parameter [JOBSCHEDULER] AffinityMask=14. It moves nearly all FSX core0 threads to core1, leaving only few fibers na core0. After that responsible for "rendering" was core1, which had little more space for working. As I fly mainly over photosceneries I was rather unhappy I had to exclude one core, loosing that way one of cores responsible for terrain texture synthesis, so I didn't stop my researches.

 

Second and better solution became moving FPS limitation (35FPS) from FSX settings (now it is left unlimited) and set this inside Nvidia Inspector (also 35FPS). Setting frame limitation inside NVI significantly reduce data flow in scene "rendering" responsible CPU core. I was able to get back to using all 4 cores for FSX (AffinityMask=15). Workload of Core0 decreased to ~50-60%.

 

So check CPU workload using Task manager > Performance tab. Reducing TEXTURE_MAX_LOAD = from 4096 or 2048 to 1024 also may help. But it may be completly different case.

I get the texture loading lag too, and consider it a normal part of FSX operation.

 

When you are looking at the outside scenery for a while, the VC textures get dropped out of the cache

and need to be re-loaded when you switch the view.

I get this 'VC not there for 2 sec' all the time. It seems to be related to how much load FSX is demanding of your system. Run a simple area and simple aircraft and VC is near instant. Load up tons of AI, heavy airports and a complex plane and you can chew up 2 bites out of your sandwich before the VC draws in fully.

 

FSX just has too hard a time moving the textures around quickly.

I understand why users sometimes like to question "the status quo". Unfortunately, sometimes this leads them to be skeptical of our reccomendations and end up on an AMD GPU. Then, later on down the road, we get complaints on the forums like "What AA do I use?" "Driver Crash" "Can't Clean Driver AMD" etc

 

Honestly, if you want to get an AMD GPU, fufill your heart's desire. But, don't get frustrated when you have issues while running within the FSX sim environment.

 

Guys... sorry about this... wrong thread :lol:

I get the texture loading lag too, and consider it a normal part of FSX operation. When you are looking at the outside scenery for a while, the VC textures get dropped out of the cache and need to be re-loaded when you switch the view.

 

It is true, but only in a half. Important is how long you need to wait for view refreshing. You have two different elements to talk about, first are VC textures and second are ground textures. I understand that "sharpening" of ground textures may take 2-3 seconds, but reloading VC textures should be immediate.

 

Ealier I had similar problem to this one described by pbagrat and after some work I completly eliminated it. With very demanding and densce scenery like Channel Isles - Guernsey from Earthsimulations and "Scenery complexity", "Autogen density" set to "extremely dense", "Mesh resolution" set to 1m, "Texture resolution" set to 30cm I don't have any issues with loading of VC textures - these are appearing instantly. The same is with other sceneries I own, listed in "My Simulator" - no problem with loading VC textures.

There are suggestions, or better said, solutions - they are called Samsung 830, Crucial M4, OCZ Revodrive...

There are suggestions, or better said, solutions - they are called Samsung 830, Crucial M4, OCZ Revodrive...

 

It won't help if CPU is overloaded. First, data flow must be matched to CPU abilities, then may be time to fine tuning performance of data storage units. SSD can't fix such problem like for example absence of PFS limitation or too high "TEXTURE_MAX_LOAD=" setting. It is even more important in case of flying demanding aircrafts like these from PMDG.

 

I don't have SDD and after some work don't have any problems with VC texture reloading while switching views. In my case installation of SSD didn't change anything, problem was with bottleneck in overloaded CPU. I know that this case may be different, just give suggestion what to check.

Problem solved for me! I posted my .cfg file here http://forum.avsim.net/topic/389591-ngx-performance/page__st__25#entry2509272

 

Incredible difference in image quality and performance...it just totally blew me away!