Sartanius

Can you please show where they said this (bold text above)? They definitely said they disappear after landing on the runway, but didn't hear AI takes over after that.. Don't want to get in a food fight here... really. Just want to know if I indeed missed something they said. Thanks.

Yes, Niklas, it was said in one of the many videos or audios. I have watched so many that I can't direct you to the exact one. I definitely would not have said this if I hadn't heard it.

I couldn't agree more. After watching all the videos and reading all the first-hand accounts of the Asobo/Microsoft event, I am encouraged and firmly believe the developers want to go way beyond FSX - and visually they already have - so I will be patient and watch with great interest.

Chris: The developers mentioned there was "AI" in the pre-alpha builds, but that they represented current r/l flights. They can be seen from within the sim, but "you can't run into them" (no interaction). Upon landing they disappear while on the runways, IIRC. As for ATC, they have discussed it. They know it is a desire from the community, but it appears they were not planning for it to be included at launch. Because of the communities interest, they may reconsider for launch, but more likely will consider it for a future release. I'm sure others will weigh-in with additional details...

In my opinion, this is a excellent idea. Asobo didn't seem bullish to include ATC at this time, at least for launch, so I'd love to see them make a way for third parties to fully integrate a solution for both ATC and AI. For me, a solution that doesn't depend on others being online to be effective is optimal. A solution that is always there when you're in the sim providing you realistic guidance day or night. I realize this is a very complicated software challenge, but hope some enterprising developers see it as an opportunity. ATC is a vital part of nearly every flying experience... to not have it available reduces the overall benefits of an in-depth flight simulator.

That's a pretty confident position. Please link to the study supporting your conclusions.

Hi Steve. Windows 10 is excellent. I wouldn't expect any problems at all. As for your PC, updating from the GTX760 to a GTX1070 will be significant. Going from 2GB VRAM to 8GB VRAM should provide you with significantly more graphics power and performance. It will certainly make a difference for you if you move to Prepar3D.

Just a thought... should this item be renamed "AI" since there's no mention of Air Traffic Control in the description?

I'll repeat one item @Noooch said at the start and add a couple more ... Realistic ATC for all phases of flight, as well as ability to control AI (spacing especially). ATIS reception ~120 or so NM before airport. I always hated starting my descent at TOD only to find out half way down the actives were switched and I was 4000 ft. above the required descent profile. (I know ASP4 tries to predict the actives for us, but what it said was wrong 50% of the time here with my setup.) Historical weather mode so I can fly a flight from yesterday or last week with the weather that was active at the time.

Hey Rob - Just saw this post here at Avsim. Maybe, if accurate, the SDK will actually be out with the tech alpha release. Edit: Go to the 25:35 mark in the audio stream for MS's comment.

Superb write-up... thanks Hal!

Something dropping on 01:06 (Jan 6 2020)? Not likely since right after Christmas/New Year... but fun to speculate.

lol

Here’s a Navigraph news item from 2017 stating the change to Jeppesen.

Hey @ryanbatcund, did disabling Cockpit Tool-tips work for your issue?

For what it's worth, I just unchecked "Disabling full screen optimization", re-enabled Cockpit Tooltips, have triple buffering and Vsync enable inside P3Dv4.5 (my default anyway)... and the problem has completely disappeared! Not sure if one of the frequent 1903 updates corrected the issue, but my problem has now been eliminated in P3D. Running Win10 v1903 (Build 18362.175) and NVIDIA GeForce 430.86 (released 5/27/19). Latest 1903 cumulative update was KB4503293 (installed on 6/12). Update: Bummer, thought 1903 update had corrected the problem, but after a reboot, it returned.. So back to original solution... disable Cockpit Tool-tips. I always have triple buffering and Vsync enabled in P3D, so that solution doesn't work for me.

This is true. It is either 1903 itself, or the way the NVIDIA drivers play with 1903. In any event, glad there is a simple workaround.

The specific feature causing this for me was having cockpit tool-tips "enabled" in the VC. Disabling cockpit tool tips stopped the black flashes. As was mentioned above, checking [enabling the check-mark] next to "Disable fullscreen optimizations" in the Prepar3D.exe properties also did the trick.

Aircraft - FSLabs A3xx - PMDG 737 NGX - PMDG 747-8 Utilities - Chaseplane - ASP4/ASCA - Navigraph Airports/Regions Sceneries - FlightBeam KMSP - LatinVFR Miami v5 - FlightBeam KSFO Textures/Shaders - Orbx Global + OpenLC - Orbx Vector - ORBX Regions (ALL)

Completely understand. Looking forward to seeing what you create, my friend.

You covered what I was curious about. Never had access to 3DSMax but understand that's the tool of choice for P3D. What is VS2017/19 used to accomplish in scenery development?

Very intriguing, Rob. If you don't mind saying, what development tools have you settled on?

Still using it Raymond, or is it on a shelf like mine?

They had a Microsoft Sidewinder Force Feedback 2 joystick and it was excellent.

4.5.12.30293 (includes HF1) all the way. Works like a champ! Problem was resolved a month ago.