Suggestion: Automatic Traffic Radius during Approach

[airlinetycoon 22]

Hi Nico,
Thanks for the auto-range feature, works great. I just tested it on the approach to KSNA.
I discussed it with other PSXT users, and the idea came up whether you could possibly define the range yourself. Is this perhaps possible with the help of Parameter.xml?

[kiek 1,134]

16 minutes ago, airlinetycoon said:

I discussed it with other PSXT users, and the idea came up whether you could possibly define the range yourself. Is this perhaps possible with the help of Parameter.xml?

I thought about that too, the only problem is for how many users are we doing this ?

At the moment the schedule is

GND: 5
<= 10 nm:  8
<= 15 nm : 10
<= 20 nm : 15
<= 25 nm : 20
<= 30 nm : 25
<= 35 nm : 30
<= 40 nm : 35
> 40 nm : 40

 Do you want 9 parameters for 5,8,10, etc.. only, or  7 parameters for the conditions 10,15,20 etc too? The latter becomes a bit complicated and is prone to errors.

 

 

Edited October 14, 2022 by kiek

[airlinetycoon 22]

36 minutes ago, kiek said:

Do you want 9 parameters for 5,8,10, etc.. only, or  7 parameters for the conditions 10,15,20 etc too?

For me personally, it's fine the way it is. The discussion was about having a higher range on the ground or in the approach if needed.

[rafimai 1]

Hello @kiek,

I am one of those who Andre was speaking to.

For me personaly this kind of range would be perfect:

Ground 10nm
Below 10'000ft 20nm
Above 10'000ft 40nm

Thats it. I think if you make it open to define own altitudes with own ranges would be the best way. You will never make everyone happy with suggested of fixed altitudes and ranges.

On the other hand I don't know how "hard" it is to realise it.

 

Anyways, thanks for you effort and mega software.

[somiller 694]

During a couple of test flights I did in the PMDG 737 around freeware KDTW I didn't notice any difference with auto range on or off. The vast majority of live aircraft were either on the airport proper, or within close range, which I suspect is why I don't see any difference. I find AI traffic to be hard on my CPU, so I would have expected a big diff. between on and off, but it just wasn't so. Maybe PSXT has to be restarted after changing auto range on and off to see any difference in number of AI.

[kiek 1,134]

15 minutes ago, somiller said:

. Maybe PSXT has to be restarted after changing auto range on I.

No, it has not to be restarted, you can switch it on/off whenever you like.

If you see the range in the GUI change, you may conclude that auto range works 😉

 

 

 

[somiller 694]

8 hours ago, kiek said:

No, it has not to be restarted, you can switch it on/off whenever you like.

If you see the range in the GUI change, you may conclude that auto range works 😉

That's what I expected, but I was surprised to see no performance change with auto range on vs. off.

Anybody else see a difference?

[kiek 1,134]

2 hours ago, somiller said:

Anybody else see a difference?

Yes, I did one flight to EDDF and saw the number of live aircraft going down from 45 to 24. Have not looked at fps if you mean performance by that.

 

[somiller 694]

I should have been more specific...I was watching fps and frame times.

[kiek 1,134]

3 hours ago, somiller said:

I should have been more specific...I was watching fps and frame times.

You probably fly with AIG aircraft only and have low LOD settings. 

In my opinion that makes more sense then the number of aircraft.

 

 

 

Edited October 16, 2022 by kiek

[somiller 694]

12 hours ago, kiek said:

You probably fly with AIG aircraft only and have low LOD settings. 

In my opinion that makes more sense then the number of aircraft.

 

 

 

Yes and yes! LOD 100 with PMDG, but I can run LOD 300 with less demanding aircraft and airports and maintain MSFS Vsync 1/3 with 100 Hz refresh = 33 fps (hardware GSYNC is great!). I wish MSFS Vsync allowed 1/4 setting which would work great with my 144 Hz monitor.

[F737MAX 4,745]

1 hour ago, somiller said:

(hardware GSYNC is great!). I wish MSFS Vsync allowed 1/4 setting which would work great with my 144 Hz monitor

Sorry for O.T.
Rather than using MSFS' internal V-sync, why aren't you locking FPS at 36 using the 'Max frame rate' setting in Nvidia Control Panel?

[somiller 694]

16 minutes ago, F737MAX said:

Sorry for O.T.
Rather than using MSFS' internal V-sync, why aren't you locking FPS at 36 using the 'Max frame rate' setting in Nvidia Control Panel?

I've found MSFS Vsync to give me smoother (fewer stutters) performance than using NVCP fps lock. I used to lock with NVCP, actually from about day 1 of installing MSFS in Oct. 2020, but about 6 mo. ago I did some testing and ended up with my current config.