Nico,

Is it possible to return an option to edit Auto-Range radiuses? 

TIA. 

I'll second that request - would really like to see the option to edit Auto-Range in .cfg

5 minutes ago, somiller said:

I'll second that request - would really like to see the option to edit Auto-Range in .cfg

Any ideas how to specify that?

 

3 hours ago, kiek said:

Any ideas how to specify that?

 

XXnm <=FL100
XXnn, between FL101 and FL250
40, after FL 250

14 hours ago, G-YMML1 said:

XXnm <=FL100
XXnn, between FL101 and FL250
40, after FL 250

And what would be your XXnm and XXnn?

No specific value for user aircraft at airport?

4 minutes ago, kiek said:

And what would be your XXnm and XXnn?

No specific value for user aircraft at airport?

That's I'm not sure. In the old versions I was able to put my own values into XX fields within parameters.xml, like 15mn - up to FL100, 25nm up to FL250, 40nm up to FL320, and then 100. 

And these values were common for all airports. If we can do this for individual airports, it would be better. For example, I'd like to have 15nm on the ground for KORD, but 40 for BIKF.

Edited January 23Jan 23 by G-YMML1

1 minute ago, G-YMML1 said:

That's I'm not sure. In the old versions I was able to put my own values into XX fields within parameters.xml, like 15mn - up to FL100, 25nm up to FL250, 40nm up to FL320, and then 100. 

So you should come up with a template that supports that, if you want to make it user configurable.
Would it not be better to make these flight levels als user configurable?
Like

Ground:           XX0
BelowFL: YY1  XX1
BelowFL: YY2 XX2
BelowFL : YY3 XX3
Above:             XX4

Assumpttion: YY3 > YY2 > YY1

1 minute ago, kiek said:

So you should come up with a template that supports that, if you want to make it user configurable.
Would it not be better to make these flight levels als user configurable?
Like

Ground:           XX0
BelowFL: YY1  XX1
BelowFL: YY2 XX2
BelowFL : YY3 XX3
Above:             XX4

Assumpttion: YY3 > YY2 > YY1

Yes, that's exactly what I'm saying. It would be great, Nico. Your template totally fits my expectations from this feature.

5 minutes ago, G-YMML1 said:

Yes, that's exactly what I'm saying. It would be great, Nico. Your template totally fits my expectations from this feature.

Good. A suggestion for the default values (8 parameters) ? (yours 😉 )

6 minutes ago, kiek said:

Good. A suggestion for the default values (8 parameters) ? (yours 😉 )

Actually, I have only two definitive suggestions.

15nm on the ground. With 10nm, PSXT 'eats" some of landing planes (I saw that on LNMAP many times) and they subsequently pops-up on the ground after landing. Not nice. With a range at 15 or greater there are no "eating" issues. 

And 100nm after FL320, however some users with weaker PC might protest. 

PSXT 14 has user configurable auto radius.

Very nice!!!

Running 14.0 now. Love 15nm on the ground 🙂