Is anyone else getting VC panel freezes on the NGX SP1, perhaps when combined with the FSDT KLAX 1.1 scenery? I can reproduce this almost every time, and it continues to this date - always tested with a SWA -800 (before and after SP1). Could a kind soul with similar addons attempt a comparative flight as described below - at dusk or night?I takeoff from FSDT's KLAS, starting from cold and dark, on a short filight to FSDT's KLAX (latest version) via the HEC transition in the early evening or night (heavy texture load). Landing at KLAX ILS Rwy 24R, I taxi toward the terminal A or B area and park at a gate - by this time, the VC displays have stopped updating but the 2D displays are still working. For instance, shuting down the engines at the gate, I can hear them spool down but N1 never decresses on the ND. I then switch back to the 2D panel and see that indeed, N1 guages did respond to the shutdown. Most if not all VC displays at this point are pretty much frozen like the last iceage, LOLFunny thing is, I don't get this panel freeze anywhere else, including other FSDT sceneries - which leads me to believe that this happens specifically at KLAX because it is the first of their add-ons to use the 4096 HD texture sets.I am running all the add-ons below across a wide-client/simconnect client network. I have also tried different overclocks from 4 to 4.8 with no difference noted - VC can still freeze by the time I taxi and park in the Termianl A or B area. For reference, I am running HiFi's ASE in DWC mode with 2048 REX textures and all the latest software versions including NaviGraph data. I also have the FSDT HD option enabled, whcih I think just forces 'max texture load' option to 4096. I also have Aerosoft's ASE running on the KLAS scenery but non is available yet for KLAX.Current FSX.cfg tweaks (off the top of my head):Affinity mask = 14 (Hyperthreading disabled)max texture load = 4096texture multi = 80HighMemoryFix enabledsticksensitivitymode = 0Lod Radius = 4.5 (always)

Try taking the affinity mask entry out of the fsx config, then try it again let me know m8im experimenting with it at the moment without any affinity mask in and the performance and stabilty is unrealaccording to a post i read somewhere if you have SP2 you don't need to ask fsx to run on all cores not sure how right it actually is though pal

I had this problem too 3 times on approach in 2d panel view. I think it is because of the complexity of the NGX + FSDT KLAX + the Default FSX LA area is very heavy on the FPS just like the Seattle area. The solution I found was to cut back on the graphics when flying into FSDT KLAX. Try using REX 1024x1024 clouds, cut the water back to 2x low, Autogen to Normal, Cloud Range to 60. If your flying on VATSIM and none of the above works also try flying in there offline and see if that makes a difference. KLAX is a very FPS unfriendly place on VATSIM when a lot of traffic is around. Add up everything above and it can be very demanding on your system.

Interesting about the affinity mask - I will try taking it out and see if it makes a difference but it does seem logically backwards. As for my setup, the scenery is set to extremely dense, autogen is dense, mesh is 100%, water is 2.x low, and textures at 7cm - nothing really out of place given the rig and is not an issue at other locations including Boston, NY, Atlanta, San Fransisco, all with heavy addon airports in these locations as well. It isn't a dll CTD related issue and I checked with ProcExp, the FSX.exe VAS (virtual size column) remains in the low 3GB range. With respect to the VC displays stop updating, it's almost as if there is something in the simconnect subsystem that dies - perhaps sensitive to the KLAX HD enviroment and/or FSDT manager engine, specific to this addon. I wouldn't expect KLAX to be problematic when FSDT KJFK is not.

I wouldn't expect KLAX to be problematic when FSDT KJFK is not.

You can't compare old FSDT scenery like KJFK with KLAX. If they were both built the same way then yeah I could see that reasoning, but they were not. In KLAX they used new techniques and enhancements that are not apart of any of their previous sceneries. So you need to look at KLAX as an ORBX type scenery and cut your graphics back accordingly. (Nobody is going to fly into ORBX maxed out). Otherwise your going to continue to have problems. Everyone I have talked to that had your issue was able to resolve it by being conservative with the graphics.This seems to be an issue for some people. They just assume cause they went out and spent a couple thousand on a Next Gen computer that it's gonna run everything maxed. It's a stubborn attitude to take and is not going to get you anywhere. Just follow the recommendations and be conservative and it will work. If you absolutely must have your graphics set so high then your only other alternative is to use a less complex plane when flying into KLAX, such as the Level-D for example.