Three times this occurred on the same SID from KORD to KMSP. My filed flight plan was to PMPKIN waypoint from KORD, KILLR3 arrival KAMMA transition. Filed altitude FL300, in the 738. At different altitudes the sim froze per say, you could still see the airplane turning if it froze in a turn but nothing in the flight deck worked, such as buttons or switches, nothing. I tried this same routing three different times, two in the 738, once in the Horizon 787-9 and the same issue occurred all three times. Twice I had FSTL traffic injector on, and once off. I also had the TCAS only on TA once and then once turned off to only transponder on. I do have the Flight beam pay ware ORD airport as well but have had that airport for a long while and I have never had this issue before.
Hi,
hard to say what the issue here is on your system. I have tried the same KORD next PMPKN with the default 787, but no freezing. The a/c continues the flight as expected.
Also, I’m not sure, why this should a navdata issue when you select and fly to a waypoint. Such issues are normally a combination of sceneries, sim version and used a/c.
Can you confirm, that this doesn’t happen with the stock navdata, or why do you mean that your issue is a navdata issue.
Possible someone else here in the forum can try this departure via PMPKN and can report back, if the same freezing happens too because I can’t reproduce it, sorry.
Cheers
Richard
The exact waypoints were as follows. KORD, PMPKN, NEATO, DLLAN, RONIC, KAMMA, KKILR3 arrival into KMSP. The issues would be random locations, the first was around 5000 feet inbound to PMPKN, the other was climbing inbound to RONIC before level off altitude. I do have the FSDreamteam payware KORD.
Hi,
have you tried the same without the 3rd party scenery as I have done? Because according your description, it doesn’t look that this is a navdata issue - more a conflict in the MSFS with your 3rd party scenery.
So, my suggestion is to remove the 3rd party scenery for testing and to try it with the stock MSFS KORD scenery to see it this happens here too.
Also, have you tested this without our data, means only with the stock navdata? When not, also worth to try.
Due the missing reports (excluding yours) and that I can’t reproduce it (at least with the stock MSFS scenery), I can’t really believe that this is a general issue - it looks more an isolated issue on your system, sorry.
Cheers
Richard