January 12, 20251 yr For some time, I've noticed that P2ATC has been really flaky and intermittent when giving after-landing taxi instructions to a desired gate. It appears that the issue goes back to the Makerwys utility, which extracts gate data and creates the g5.csv file that enumerates all the gates in the user's scenery config. Makerwys is capturing the gate info for default airports, but it is *not* then replacing the default gate info when a third-party add-on airport is present--in both MSFS 2020 and 2024. From my perusal of the source code, I don't think it ever has gotten this correct in MSFS (but it is still working in the ESP sims--P3D, FSX, FS9). So getting good taxi directions to the gate from P2ATC in MSFS is apparently only happening when the default and add-on gates are at least close to coincident in name and location. Makerwys does still capture updated runway and other info...it looks like the gate data is the only outlier, at least until Asobo or LR change the data structures again. Pete Dowson has fully retired and his son John (who took over FSUIPC development) stated on the FSUIPC forums that he is also not intending to maintain the Makerwys utility--Pete has published the source code on the FSUIPC forums in case someone wants to take up the task of updating it. Similarly, the analog for Makerwys for XPlane also no longer works with XP12's new scenery data format. So...that said, what is P2ATC's path going forward without this tool? Bob Scott | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
January 13, 20251 yr Commercial Member While not ideal, P2A has the Taxi Mnt facility where you can fairly easily rename the gates at an airport. Of course this is a manual task, but would only need to be done for the 3rd Party airports you mentioned. I will try and have a look at the MakeRunways code at some point, but am currently 100% focused on getting bugs ironed out of P2A V3. There is an issue in the Gate Import function of P2A V3 that I've just fixed and will be out in the next update (0.0.30), but it will still rely on MakeRunways for the input data. If the data is not in the g5.csv file, the fix may not help, but it might be worth trying to import one of your custom airport gates to see what happens. Dave
Create an account or sign in to comment