July 18, 20232 yr Just tried Pilot2ATC 2.7.0.0 Beta 3b Update and the plugin still doesn't show up in the Plugins manager.
July 18, 20232 yr Commercial Member You could copy the P2A_XPLink folder from the P2A installation folder to the X-Plane plugins folder. There will not be an entry in the Plugins menu of X-Plane. It will only be listed in the Plugins manager where all plugins are listed. Dave
July 18, 20232 yr Thanks for that hint, I copied both the xplink and xplink128 folder. Now it seems to work. Will verify tomorrow. I guess the 128 folder did the trick
July 18, 20232 yr Commercial Member When you test tomorrow, you should try testing with one version or the other in the plugins folder because otherwise, 2 instances of the plugin will run at once, possibly affecting performance and confusing P2A. Dave
July 18, 20232 yr Yes will do. What is the difference between those two? Is there any issue or disadvantage if the 128 folder only works?
July 18, 20232 yr Commercial Member The 128 folder only samples the data every 128 frames of XP. It was created to have an option if the regular one took up too much resources. The regular one does it every second, regardless of framerate. Dave
July 18, 20232 yr Hi, just tryed with beta 3b, no error with 128 but same error 126 with the normal. Alessandro
July 19, 20232 yr Commercial Member I found a problem with the P2A_XPLink plugin. The latest Beta 3c contains a new version that should work for those of you who were having problems. Please let us know how it does. Dave
July 21, 20232 yr Author On 7/19/2023 at 2:34 PM, Dave-Pilot2ATC said: I found a problem with the P2A_XPLink plugin. The latest Beta 3c contains a new version that should work for those of you who were having problems. Please let us know how it does. Dave brilliant thank you. have installed and about to play 🙂
July 23, 20232 yr Hey Dave, the latest fix seems to generally have fixed the issue but the original problem with xp12 and traffic global still exists. P2ATC does show traffic on the map when enabled but it ignores them at takeoff. Tested this and got a clear for take off immediately although there was a plane still on runway and another on short final. i have not heard „line up and wait“ „caution wake“ or number 2 for takeoff etc for ages… probably in msfs last time. so something still is wrong Edited July 23, 20232 yr by kuba_87
July 23, 20232 yr Commercial Member This ignoring of traffic should be fixed in the next Beta, along with a setting in config to control the number of seconds from the first aircraft on final is considered "clear". The current version has this set at 2.8 minutes which is too long for some who only fly out of GA airports and too short for others that want longer to lineup and takeoff. More importantly, if you have dense traffic and ever want to get takeoff clearance, you may have to shorten this and be very quick about getting on the RW and taking off...or better yet, turn the traffic volume down to something reasonable. Should have this out in a day or so.
July 23, 20232 yr That would be great! Very good idea to put in a time based clear parameter. I guess for me flying airliners about 120s should be sufficient. Looking forward to see some more interaction again with traffic 😊
July 24, 20232 yr Commercial Member Version 2.7.0.0 Beta 4 has been released and has the fixes for takeoff clearance and the option to adjust the On Final Takeoff Separation. Dave
July 25, 20232 yr Hi Dave, thanks for the update. I have just tried this. Set the timer to 120s and went off to EDDM Had an aircraft on the runway lining up in front and another one right at short final. Both aircraft got ignored and i got cleard for takeoff right away.. I was expecting to either wait for the departing aircraft to clear the runway or / and wait for the approaching aircraft. any helpful log or so i can provide? PS. since a few updates ago, p2atc somehow strangly changes com1 to com2 for no reason. No a big proble as i can change it back, its just irritating, didnt do this before
Archived
This topic is now archived and is closed to further replies.