Zinnertek

It's merely a test... if someone wants to fly from Europe to an FSDT airport then couatl.exe needs to be running by the time they arrive for the airport scenery to load.

I think we also need to consider that whilst couatl.exe is an external process, it is closely linked and communicates with P3D via bglmanx64.dll and SimConnect, therefore can play a role in crashing the simulator. I'm trying a transatlantic flight now, rather than killing couatl.exe I'm trying the restart method suggested by "B777ER". I think the key is restarting couatl.exe after you have your engines running or even after takeoff Will report back later.

For those who have the crash and those who don't, which FSDT products does everyone run? Specifically, it might be associated with GSX rather than the airports themselves

If you have the time, then try flying the exact same route again but don't close couatl and see if there is a crash.

I have been having this issue since P3D v3 too! The CTD always happens on a westbound flight from Europe towards America and around the area of reaching Canada. I have 16Gb of RAM and I use the PMDG auto time-acceleration feature. I don't use AI traffic. The most likely culprit for me has been FSDT couatl engine. If I ever try suggesting this as an error on their forums, I just expect a rude reply saying how it could never ever be their product. I have had some success by using task manager to close couatl.exe after I depart, and that tends to work. I haven't flown the route in a while so I'm not sure. Next time you fly the Europe-America route, try not restarting GSX after pushback and see if the CTD returns. Cheers

Does anyone get the problem where - in a scene which has many lights (e.g. at EGLL facing the terminal buildings whilst taxing) the aircraft taxi lights disappear? I assume because the hard limit of 250 DL is reached. Why can't it limit lights based on distance rather than number, and why would it start from the closest?

This is why I think there's more to it, and possibly a bug If I load the aircraft @ EGLL and sit in the virtual cockpit without touching anything. Even after a good 10 mins the fps is at rock bottom and GPU usage is 100%, and it will only resolve if I pan around. Its almost like panning helps clear the pipeline where something is stuck??

Does the fps not improve after giving it 2-3 mins and panning around for a while?

I have the same odd issue, at startup very low fps and GPU usage at 100%, pan around for a good 2-4 mins and eventually the fps shoot up to the normal range. Basically with aerosoft EGLL Pro and PMDG NGX I can depart in the night at 40fps and only ~60% GPU usage I am using a 7700k @ 5Ghz, ASUS Strix GTX 980 and 1080p monitor with MSAA x4 (thought some airports I can do 2x SSAA) Me thinks its a bug or poorly optimized code. Isn't there a way to disable AA on DL? Make it the last object rendered or something

I wonder if there are any plans to support this feature on the NGX?

I realized I have posted this on the FSX thread, whereas I use P3D so.... Please add an option to "Exclude Sleeping AI" rather than Ground AI, into the main data collection interface. It would really help with tracking AI planes Also would it be possible to add 'always slew' mode to taxing AI aswell? Mainly because although the other way is more realistic, sometimes in custom scenery airports the planes get stuck at tight bends and other places. Cheers, otherwise really useful tool. I use the FSUIPC traffic limiter to control AI numbers, but this tools helps them move about much better Thanks

Also would it be possible to add 'always slew' mode to taxing AI aswell? Mainly because although the other way is more realistic, sometimes in custom scenery airports the planes get stuck at tight bends and other places. Cheers, otherwise really useful tool. I use the FSUIPC traffic limiter to control AI numbers, but this tools helps them move about much better

Please add an option to "Exclude Sleeping AI" rather than Ground AI, into the main data collection interface It would really help with tracking AI planes Thanks

I know this is one of the leading features of V2, but is there any chance you could create an option for AI controller to use 'slew' mode exclusively (over fly mode), even for taxi and takeoff as well as landing. I prefer the precision over aesthetics. Also a few features that might help: - option to hide 'sleeping' aircraft from data collection window - option to also cull 'sleeping' aircraft to meet a AI traffic number target? Thanks, you have done a wonderful job of this.

I think you need to try a little housekeeping first. 1) check all drivers are up to date, and win 10 compatible 2) install DirectX runtime's 3) ensure you have necessary Visual Studio Redists etc 4) install p3d vanilla and see if it has problems first Lastly what are your specs? Have you overclocked?