pytteros

I have found the problem!

I was inspecting VAS consumption with Process Explorer as I was flying from ESSA to LDSP. Blackout happened over Poland. I noticed in the Process Explorer that "commit charge" was at 99,97%. I closed all other programs quickly and blackout went away as Commit Charge dropped to 96.something %. I flew for a minute, black out came back and CTD happened. Free VAS vas >1,5 Gb.

https://en.wikipedia.org/wiki/Commit_charge

I started to wonder what caused the increase in Commit Charge. I flew same time with my friend, who uses FSX, and he reported that his Commit Charge rarely exceeded 40% on his machine.

I started a new flight, same fligthplan and everything. I kept my eye on Commit Charge all the time, and I found out that when I cycled view "S" through 2D cockpit, Commit Charge jumpted up a little. I continued to press "S": 2D -> Wingview -> Spot -> 2D -> Wingview -> Spot -> 2D.... and so on. After doing this for a minute, Commit Charge went to 100% and everything went black.

I tested this with Majestic Dash Q400 and default F22 Raptor. Majestic has a 2D panel and I was able to recreate the blackout with it. Default Raptor doesn't have a 2D panel, but I was able to recreate the blackout with it too.


All this makes sense now
- I love using NGX 2D panels. During my flight I change views multiple times between 2D, 3D and spot view. This slowly builds up Commit Charge and when it his 100%, blackout happens.
- All my blackout experiences have happened with NGX, because I use the 2D panels (In 2D view). With Majestic Q400, I never use the 2D panels, so I never cycle views through 2D cockpit. That's why blackout never occured with Q400, until I maliciously caused it with cycling views.
- Black out doesn't require plane to have physical 2D panels, only changing to 2D view causes jump in Commit Charge. That's why also Raptor can cause the blackout.
- I added CycleHidden=Yes to cameras.cfg cockpit-section and flew ESSA-LDSP again and guess what= Commit Charge never exceeded 50%, VAS remaining at Split was >1.0 Gb and I was able to fly from point A to point B!
- By disabling cockpit view, view cycling goes: 3D -> wingview -> Spot -> 3D and so on... This way Commit Charge does not build up, even when cycling with "S" for a minute.

It looks like there is problems with 2D view in terms of memory usage. Possibly just on my machine, or in P3D itself. I have had this same problem before and after fresh install of Windows.

Can some of you try to replicate this and report results? I can capture a video from this phenomenon to visually demonstrate what I've said in the text above.