Losing connection with compositor

[Tedmax]

I have begun to experience losing connection with steamvr compositor. The Vive desktop window still shows green text and Ready. P3D v3.3 is still running in it's window. Sound is working etc but the headset is displaying grey/blue like the FI loading screen but without the clouds, floor grid etc. I am on the latest Nvidia driver for 1080, Win 10x64 home with all latest updates, 32GB ram, 500GB SSD, P3D v3.3. At the time I had GTN750 and VoxATC windows open but I wasn't interacting with them. I had been flying for about 25 mins and landed at a small regional airport and was taxing to the terminal when it happened. AS16 was not running because it happened the previous time while in flight and I suspected it might have been due to a weather update but apparently not. The FPS was ~48/90. Windows Defender is set to exclude C:\. P3D is installed into its own folder C:\Prepar3d V3

Any suggestions about fault finding this one?

[Tedmax]

Hmmm. Just did the same flight with AS16 VoxATC FI but this time Nvidia settings Power Management "Prefer max perf" Texture filtering quality "High perf" (for P3D) and the same for Steam.exe and SteamService.exe. Went OK. Maybe onto something here. More testing to come.

[admin]

Let me know your experience here please. The only time I've seen the grey/blue is when Vive loses tracking. I hold it up with clear view of light-house for a minute and it comes back. Please let me know if your issue ends up being different!

[Tedmax]

I am suspecting it is VoxATC that is not compatible. It is not certified for P3D v3.

I was in the middle of a 120mile flight. GTN750 being used for flight planner. VoxATC window was open but I hadn't clicked Enable. After about 70 miles into the flight, everything going smoothly I decided to click that Enable button to see what would happen. Within 20 seconds I lost the compositor. Now it could be co-incidence but...

[Tedmax]

With so many variables to check/eliminate it might be hard to point the finger at one app or setting I suspect. After posting my suspicion about VoxATC in the previous post, I uninstalled it. I flew like that for a few days - usually a few hours landing/taking off and trying to get a workflow for the avionics. Things are becoming more stable in that I am not having to reset the pc multiple times per session and I didn't loose the compositor. Two days ago I installed the latest driver for the 1080 and I updated Win10 to anniversary. Probably not such a good move to introduce more variables. Things are still stable but the new driver has introduced some frame noise (blocks of pixels with random colours) every 10 seconds or so - but it has improved the framerate by a large margin so I am sticking with it. Anyway, I haven't lost the compositor for a while. So to convince myself it really was VoxATC, I re-installed it and took a 60 minute flight with GTN750/VoxATC but no AS16. Under ATC control the whole way and landed at an uncontrolled airport no problems. OK back to square one. I am now using FSGRW in the mix and see how that goes.

[Tedmax]

Well it turns out this one was pretty easy to fix.

The headset was loosing sight to both of the lighthouses. It only dawned on me that I lost the compositor when I was learning forward to look at the gauges.

The lighthouses were in diagonal corners of the room but when I learned forward the shelf above my desk blocked the one to my left, and my head blocked the one behind me. I have moved one of the lighthouses so that I have one to my left and right at about 60 deg to where I am sitting.

Problem solved.

[admin]

That's too funny Glad you got it solved, I was trying to reproduce, but could only do so when I lost view of the light-house (just like you).