Add projectile height apex on click

[Ferrariic]

Situation: The height barrier/skybox prevents some projectiles from reaching their intended destination.

Solution: Adding a height readout as described below, only on projectile examination click, this would allow users to determine valid targets based upon skybox height.

Example: As recently discovered and referred in issue #148, the MK19 and other projectiles may have a more limited maximum ranged depending upon the map used by virtue of colliding with the skybox.

Example: Valid target on move

Example: Invalid target at kropy, the other 1 star.

Benefits: This may allow for the mk19 to find true max ranges on each map, as the sky is the limit (literally). This would allow for additional future high velocity indirect fire projectiles to see their potential max range as well.

[sh4rkman]

Hm.. this is definitly not a skybox problem since weapons shooting at high angles (45-90°) can reach up to 1km high

110 velocity + 85° angle = 613m max height (classic mortars) 142 velocity + 85° angle = 1021m high (M121) 240 velocity + 210 angle = 378m high (your MK19 example)

[Ferrariic]

Hm.. this is definitly not a skybox problem since weapons shooting at high angles (45-90°) can reach up to 1km high

110 velocity + 85° angle = 613m max height (classic mortars) 142 velocity + 85° angle = 1021m high (M121) 240 velocity + 210 angle = 378m high (your MK19 example)

Tyvm for looking into this, let me retest some things.

[Ferrariic]

Okay, I was wrong. It seems like after 20s of flight time the explosion part of the projectile disappears. It puts the max range at ~4.2km in game practically. The limitation would be with projectile time, not vertical height. Feel free to close this issue, I will have to address this in #148 and #149.

This sdk value aligns with tests in-game.

Full panel:

Lmk if you want a separate issue for this in squad calc