February 1Feb 1 Hi Nico, I am not getting collision avoidance in the air with live aircraft as per the manual 6.2. I have had many instances where a live aircraft was within "less than 4 miles, within an altitude difference of 1’000 feet" still being shown on TCAS and causing a TCAS RA; I cannot comment on the '“width” less than 700 ft' part of the rule, as I do not understand this. The option is selected in the UI and shows True in the parameters.xml file. Peter CPU: AMD Ryzen 7 9800X3D | GPU: NVIDIA GeForce RTX 4080 Super | MoBo: ASUS Prime X670-P WIFI | OS: Windows 11 Home 64bit| RAM: 64GB 6000 MHz DDR5 | HD: 2TB Samsung 990 PRO M.2 PCIe SSD, 1TB Samsung 990 PRO M.2 PCIe SSD | MSFS 2024
February 1Feb 1 Hi Peter, Yes that is because I forgot to update the collision function to the new altitude calculation method for RT aircraft (done to give correct values in your TCAS). I have to use indicated altitude for the user aircraft now instead of plane altitude, to calculate the altitude difference with the RT aircraft. Will fix that in the next version. Thx for letting me know. Nico Edited February 2Feb 2 by kiek
February 21Feb 21 Author Hi Nico, From my test flight this morning with v14.5.0, the airborne collision avoidance is not working. On approach to EGLL, I had a live aircraft just in front of me all the way down the approach to touchdown, when it was eventually removed. Peter CPU: AMD Ryzen 7 9800X3D | GPU: NVIDIA GeForce RTX 4080 Super | MoBo: ASUS Prime X670-P WIFI | OS: Windows 11 Home 64bit| RAM: 64GB 6000 MHz DDR5 | HD: 2TB Samsung 990 PRO M.2 PCIe SSD, 1TB Samsung 990 PRO M.2 PCIe SSD | MSFS 2024
February 21Feb 21 56 minutes ago, Harrier77 said: From my test flight this morning with v14.5.0, the airborne collision avoidance is not working. On approach to EGLL, I had a live aircraft just in front of me all the way down the approach to touchdown, when it was eventually removed. What makes you think it is not working? Did you collide? An aircraft in front of you is allowed. There is no 4 nm threshold. Manual: PSXT tries to prevent audible TCAS alerts without removing aircraft too early. For example, if the protection block is too wide, aircraft landing on a parallel runway may also be removed, which would break the immersion. PSXT removes/hides the live aircraft temporarily until it is safe to show it again. PSXT also removes a live aircraft when during a landing, starting from 500 ft above ground, it detects a live aircraft right in front (entering or already on the runway), within 1 nm. Edited February 21Feb 21 by kiek
February 21Feb 21 Author I have read the manual and the release notes. Having another aircraft literally just in front of me for the whole approach, and with a TCAS RA shouting at me most of the way down, was not what I was expecting with this update. I was hoping for a clear "bubble" around my aircraft, thereby enabling me to fit into a tight sequence without another aircraft close by, and without TCAS RAs. I suppose it is something that I will have to live with when going into a busy airport. CPU: AMD Ryzen 7 9800X3D | GPU: NVIDIA GeForce RTX 4080 Super | MoBo: ASUS Prime X670-P WIFI | OS: Windows 11 Home 64bit| RAM: 64GB 6000 MHz DDR5 | HD: 2TB Samsung 990 PRO M.2 PCIe SSD, 1TB Samsung 990 PRO M.2 PCIe SSD | MSFS 2024
February 21Feb 21 59 minutes ago, Harrier77 said: I have read the manual and the release notes. Having another aircraft literally just in front of me for the whole approach, and with a TCAS RA shouting at me most of the way down, was not what I was expecting with this update. I was hoping for a clear "bubble" around my aircraft, thereby enabling me to fit into a tight sequence without another aircraft close by, and without TCAS RAs. I suppose it is something that I will have to live with when going into a busy airport. I wrote in the Release Notes that it needs futher tuning... A "clear bubble" is not so easy to achieve. Like I wrote, I want to prevent TCAS from shouting, and also to prevent unnecessary removals. Seeing other aircraft is part of the fun.. If I have time I will run a lot of tests to fine tune the parameters, maybe in 14.5.1 it is better. @Harrier77EDIT: Maybe there is a difference in how TCAS TA reacts between aircrfat. I fly PMDG B736 and B738. What do you fly? How is that in the real world? Are there differences or is it strictly regulated. Edited February 21Feb 21 by kiek
March 3Mar 3 I am still seeing this issue. I know you were going to do some tests but just wanted to point out what others might being seeing. The plane ahead of me was actually much closer at one point. This is just when I remembered I should probably take a screenshot. This is with the Fenix Airbus. Had this TCAS alert going until I could figure out what flight it was and blocked it. I also flew right through an aircraft in the PMDG 777 on file to KMEM the other day. I confirmed the check box user air was checked under collision avoidance. David
March 3Mar 3 2 hours ago, DaveS said: I am still seeing this issue. I know you were going to do some tests but just wanted to point out what others might being seeing. The plane ahead of me was actually much closer at one point. This is just when I remembered I should probably take a screenshot. This is with the Fenix Airbus. Had this TCAS alert going until I could figure out what flight it was and blocked it. I also flew right through an aircraft in the PMDG 777 on file to KMEM the other day. I confirmed the check box user air was checked under collision avoidance. Please wait for version 14.6.0. This week, Harrier77 has tested three iterations of the new algorithm. It is now very close to perfect. New: PSXT detects near-collisions in the air only below 7,000 ft AGL. Above 7,000 ft AGL, you are expected to respond to TCAS warnings yourself. The logic is focused on arrivals and features two modes: VECTORS (below 7,000 ft AGL) FINAL (below 4,000 ft AGL) The objective is not ATC conflict resolution, but to prevent unrealistic close merges and nuisance TCAS alerts while preserving live traffic realism. Testing shows that you can now smoothly blend into heavy landing traffic, such as at EGLL.
March 4Mar 4 20 hours ago, kiek said: Testing shows that you can now smoothly blend into heavy landing traffic, such as at EGLL. This sounds great! thanks! David
March 16Mar 16 I got this on approach to EGLL this morning... https://ibb.co/g1z02Qq Any way this can be fixed? It used to remove aircraft on approach that were close in front AMD Ryzen™ 9 9900X3D, AM5, Zen 5, 12 Core, 24 Threads, 4.4GHz, 5.5GHz Turbo 64GB (2x32GB) DDR5 6000MHz Corsair Vengeance 32GB GeForce® RTX 5090 Graphics Card
March 16Mar 16 14 minutes ago, BWBriscoe said: Any way this can be fixed? As Nico said 2 posts above - wait for version 14.6.0 Cheers, Søren DissingIntel i9-13900K @5.6-5.8 Ghz | ASUS ROG RYUJIN III | ASUS ROG Astral RTX 5090 OC | ASUS ROG Maximus Z790 Hero | 64Gb DDR5 @5600 | 1Tb Samsung M.2 980 PRO (Win11), 1Tb Samsung M.2 980 PRO, | ASUS ROG Helios 601 | 32” ASUS PG32UCDM 240hz 4K | Chaseplane | TM TCA Captain's Edition, Winwing FCU + EFIS L/R, Tobii 5 | Win 11 Pro 64 | MSFS 2024 | BA Virtual | PSXT, RealTraffic w/ AIG models
March 28Mar 28 Any idea when this is being released? AMD Ryzen™ 9 9900X3D, AM5, Zen 5, 12 Core, 24 Threads, 4.4GHz, 5.5GHz Turbo 64GB (2x32GB) DDR5 6000MHz Corsair Vengeance 32GB GeForce® RTX 5090 Graphics Card
March 28Mar 28 28 minutes ago, BWBriscoe said: Any idea when this is being released? See my post at the top of this Forum...
March 28Mar 28 4 hours ago, kiek said: See my post at the top of this Forum... Doesn't give any idea of a release date. It's becoming very hard to fly into large airports AMD Ryzen™ 9 9900X3D, AM5, Zen 5, 12 Core, 24 Threads, 4.4GHz, 5.5GHz Turbo 64GB (2x32GB) DDR5 6000MHz Corsair Vengeance 32GB GeForce® RTX 5090 Graphics Card
March 28Mar 28 3 hours ago, BWBriscoe said: Doesn't give any idea of a release date. It's becoming very hard to fly into large airports It will be a piece of cake. Ask my tester Harrier77 😉 Most likely the release will be in the week starting with April 13. Edited March 28Mar 28 by kiek
Create an account or sign in to comment