August 6, 20241 yr Nico, I just want to confirm that PSXT is intentionally blocking traffic that has only partial info on RT radar, such as WIF163_(Q300 or NOZ54K_(B738. I'm looking at ENGM now and and it appears that while RT recognize those flight, PSXT does not inject them into sim. 9950X3D, X870E ROG CROSSHAIR HERO, Corsair Dominator Titanium 64GB DDR5-6000 PC5-48000, ASUS RTX 5070Ti 16GB, 9100 PRO 4TB Samsung ,990 PRO 4TB Samsung, AX1600i 1600 Watt 80 Plus Titanium ATX, ASUS 360 ARGB EXTREME 360mm Liquid CPU Cooling Kit.
August 6, 20241 yr 1 hour ago, G-YMML1 said: I just want to confirm that PSXT is intentionally blocking traffic that has only partial info on RT radar, such as WIF163_(Q300 or NOZ54K_(B738. I'm looking at ENGM now and and it appears that while RT recognize those flight, PSXT does not inject them into sim. Are you sure they are in your lateral range? Is it of a category you want? Another possibility could be that their data are at too big intervals (not once in say 9 seconds). Or another possibility that an aircraft with these callsigns without the trailing underscore is already in the Sim. You see, it is not so obvious 😉 BTW, why are you still using PSXTraffic? PSXT is much better. Edited August 6, 20241 yr by kiek
August 6, 20241 yr Author I use PSXT exclusively. I usually check traffic movements on RT at specific time-frame, then compare it with PSXT/MSFS. I will continue to test and let you know more details. 9950X3D, X870E ROG CROSSHAIR HERO, Corsair Dominator Titanium 64GB DDR5-6000 PC5-48000, ASUS RTX 5070Ti 16GB, 9100 PRO 4TB Samsung ,990 PRO 4TB Samsung, AX1600i 1600 Watt 80 Plus Titanium ATX, ASUS 360 ARGB EXTREME 360mm Liquid CPU Cooling Kit.
Create an account or sign in to comment