May 10, 201610 yr In P3D v3.2 last night from MCO to FLL, on approach to FLL approach (who didnt provide any STAR) handed me off to tower, (who didnt provide any runway/approach info). I checked active runway via the info tab in P2A which had only dashes. I contacted tower requesting active runway, which replied 10L. I requested landing on 10L and got an exception error and P2A crashed. I can see if I can duplicate this if needed. Chris DeGroat XP11 | MSFS i9 12900k | 32GB DDR5 RAM | 2TB Samsung EVO SSD (1TB x 2 in RAID 0) | MSI RTX 3090 | Reverb G2 | RealSimGear TBM900 Panel with Yoko+ TQ6+ & TM TPR Pedals
May 10, 201610 yr Commercial Member Hi Chris. I think I found the problem with the Active Runway not being displayed. To troubleshoot the ATC behavior, I need to know: What was your flight plan? What were your FltPln settings in the Config panel? Thanks, Dave
May 11, 201610 yr Author Hi Chris. I think I found the problem with the Active Runway not being displayed. To troubleshoot the ATC behavior, I need to know: What was your flight plan? What were your FltPln settings in the Config panel? Thanks, Dave Flight plan settings were everything checked except, Force pilot runway, ATC Ignores published speed limits, ATC gives vectors to IF. Alt change lead time (sec) is 30 and vector extended final distance is 2. Flight plan was: KMCO, TRV, JALOP, GISSH, FISEL, FLL. Chris DeGroat XP11 | MSFS i9 12900k | 32GB DDR5 RAM | 2TB Samsung EVO SSD (1TB x 2 in RAID 0) | MSI RTX 3090 | Reverb G2 | RealSimGear TBM900 Panel with Yoko+ TQ6+ & TM TPR Pedals
Create an account or sign in to comment