November 10, 20241 yr Hello, The above request is with respect to the release note for version 8.6.0 shown below. "Oct 16, 2024, version 8.6.0 • PSXT & PSXT_P3D: I made the traffic injection range more precise. Until now the latitude offset was correct but the longitude offset was often too big, resulting in more aircraft than wanted. " Is there any way the latitude and longitude offsets can be specified by the user (for instance up to 200 miles)? I follow live traffic in real time, do not mind the extra traffic, and have a devices which can handle the load. The extra latitude offset definitely worked for me and so would an extra longitude offset. Appreciate any clarification on the feasibility of this request.
November 10, 20241 yr 6 hours ago, busolavie said: Is there any way the latitude and longitude offsets can be specified by the user (for instance up to 200 miles)? The range is already selectable between 2 and 100 nm ... (see Manual 8.1) More is technically speaking not possible (SimConnect limits). I will add the word radius to the UI, to make clear that you can define a circle with a radius in Nm around the user aircraft. But why more then 100 nm? For a pilot flying the user aircraft anything above 40 nm is useless (TCAS). For an aircraft spotter, more then 10 nm is useless (visibility in the Sim). It is only interesting to see the traffic around you in programs such as LittleNavMap. If you want to follow an aircraft in spot view you must change your user aircraft to a position more closeby if the aircraft that you are following is reaching the 100 nm limit...
Create an account or sign in to comment