March 21, 20251 yr Good morning, I think that the formula sum of wingspan divided by two leads to unrealistically close encounters of the user aircraft with live aircraft on the ground. Is there a way to increase it? Perhaps in the parmeters file? I would like to try without division by 2 and see if that helps. Best draci Edited March 21, 20251 yr by bmaik
March 21, 20251 yr Hi draci, That's tricky stuff, currently I take 1.1 * (half wingspan live + half wingspan user) as threshold. For live aircraft I could change that to 1.2 or 1.3... For static parked I do not want to change it, because they don't come back after removal, contrary to live aircraft. The problem with greater distances is that live aircraft that taxi in opposite direction from the user aircraft on a parallel taxiway may disappear too. Same when waiting in line for takeoff, you may loose the live aircraft that you are following. So what to do? Nico Edited March 21, 20251 yr by kiek
March 21, 20251 yr Author Ok, I didn't think of this problem, thank you for your quick reply. Maybe you could use the direction of travel (velcoity vector of the user aircraft) and only remove aircraft if they enter a certain increased threshold radius around the user aircraft directly from the front (with a certain small angular tolerance), since you obviously want to remove only aircraft that are taxiing on the same taxiway in opposite direction than the user or are parked in the user's direction of travel. This shouldn't be too hard to code or am I mistaken? Edited March 21, 20251 yr by bmaik
March 21, 20251 yr 1 hour ago, bmaik said: since you obviously want to remove only aircraft that are taxiing on the same taxiway in opposite direction than the user That cannot happen in real live unless you as a user drive on the taxiway in the wrong direction... Real live pilots don't do that, so AI aircraft representing these pilots don't do that either 😉
March 21, 20251 yr Author Yes, but ATC programs usually don't know the runway that it in use in reality (most frequently they decide according to the prevailing wind and have no clue about current runway closures or WIP and the like). Furthermore they don't respect real world taxiway directions and can't control the PSX Traffic at all. Then it can easily happen that you are directed to a (wrong) runway along a taxiway that is used in the other direction in real world. In this case opposite traffic should be deleted way ahead if the user wants to act according to the ATC clearance in order not to destroy the immersion... Edited March 21, 20251 yr by bmaik
March 21, 20251 yr 2 hours ago, bmaik said: Yes, but ATC programs ... you are not gonna tell me you are using ATC programs together with PSXT? 😉 I keep far from those programs. If you insist on using ATC, you better fly with VATSIM or IVAO. Edited March 21, 20251 yr by kiek
March 24, 20251 yr On 3/21/2025 at 12:45 PM, kiek said: That's tricky stuff, currently I take 1.1 * (half wingspan live + half wingspan user) as threshold. For live aircraft I could change that to 1.2 or 1.3... For static parked I do not want to change it, because they don't come back after removal, contrary to live aircraft. The problem with greater distances is that live aircraft that taxi in opposite direction from the user aircraft on a parallel taxiway may disappear too. Same when waiting in line for takeoff, you may loose the live aircraft that you are following. So what to do? I have changed it to 1.15 in version 10.7.10. Thats about 3,5 meters more for two B738's
Create an account or sign in to comment