What you are suggesting is rewriting half the engine, it is not doable

What do you mean? The detection radius cannot be less than vehicle precision, because of the path planning, it will plan path in chunks of the size of vehicle precision so it cannot be less. If you you think the precision is too rough, make a mod and change it, since it is config value it cannot be changed on per vehicle basis.

@BIS_fnc_KK
After some testing, I would appreciate the ability to influence the safety range. Maybe as an optional parameter to switch off safety distance.
As new, optional parameter it would not break the default setup and give the chance for existing missions to "react" to the new cirmustances with minimum effort.
An advantage of this would be, that the multplier can be introduced again for Non-PLaer AI groups

@mickeymen
I appreaciate your effort to find a solution. But to set the value for the completion radius to a value lower than a computated specific value for each type of vehicle would "override" this lower value by the "computated specific value". And here is the problem specially for that specific air vehicle:
The computated value is 10x higher as forseen by the value in the config. this means in numbers:
The minimum completion radius forseen for this air vehicle is 100m. This means, that all values between >0m and 1000m would be overriden by 1000m (the faulty computated minimum value for these air vehicle of 100m).
Caused by the bug it is 10x higher, so it is 1000m.
In other words: All values from 100m(this is after the introduced behavior of this ticket the minimum compl. rad for this vehicle) to 1000m are not reachable to set. And THAT is a problem. Not for me, but for some scripters and for all the missions out there, that maybe are abandon and have no support anymore to react to this.

@Tenshi
If you expand the older posts, you will find this post from jaj22:
"
Replicated this in the editor. It looks like when you give vehicles non-zero completion radius values, it caps them to a type-dependent minimum. However, this minimum seems to be 10x higher than the normal type completion radius for air vehicles. Tested cases:

@Tenshi
By way of explanation:
This ticket is not yet complete. In the performance build, this ticket was introduced with version v3. It turned out that this bugfix caused a new problem: The completion radius for at least one aircraft does not seem to work properly (for an explanation see comments by jaj22 and me here in the ticket).
In my opinion, this should be solved before this ticket is included in the stable version.

Hi,
I play "Dynamic Bulwarks Mission"
My server is 32bit Linux. Profiling branch.
https://github.com/Omnomios/DynamicBulwarks/tree/develop
In this mission, there is at the beginning of a round a airplane, that drops a box in the players zone. This is definitly broken since Profiling V5, but maybe earlier in V3. The Problem is I cannot say it with 100% because V3 and V4 has another bug that broke the mission entirly. So this is a little bit fuzzy.
Normal behavior is:

• Airplane spawns
• Airpane flys over player zone
• Airplane drops/spawn a box on a parachute inside the player zone
• Airplane exit playerzone and despawn

Tested with Linux 32bit 2.10 Profiling V6.
Bug is present.

In T166456#2338036, @dedmen wrote:

yes it is, most likely wont fix

I would suggest this function to be make optional and on per default for "normal" armies vs armies. But there are also other gamemodes and mods (hopefully), e.g. Lootshooter, Survival, etc.