Page MenuHomeFeedback Tracker

[Experimental] Erroneous Mortar Ballistic Table Values
Awaiting internal Testing, NormalPublic

Description

Game Version number: 1.3.0.18 (Experimental Branch)
Modded?: No

Issue Description:
Currently, there is an issue where the Ballistic Table may provide incorrect data for the change of elevation (mil) for every 100m of barometric altitude change.
Going by the formula in game, where any altitude difference (m) is halved and added to the radius/ground distance (m), and the resulting elevation (mil) is rounded down to the greatest integer, it is quite easy to reproduce the values within the column as shown in the correct Ballistic Table.
However, there is currently a bug where the table provides erroneous values, which are seemingly random, and cause a large margin of error in the resulting shots if the wrong value is used in calculations. A solution to this is to calculate the whole thing manually (as shown in the formula above), but this defeats the purpose of having on hand the ∆ɸ value to adjust for ∆z.

Below is an example of the correct list of values (4th column).

Below is an incorrect example. (I could not replicate on a US mortar firing table, but I was (un)lucky enough to have it occur for a Soviet firing table.

Details

Severity
Major
Resolution
Open
Reproducibility
Random
Operating System
Windows 11 x64
Operating System Version
24H2
Category
General
Steps To Reproduce

Currently unaware of how to exactly reproduce, however, it seems to be client-based as the below screenshots are from 2 different users within a locally hosted game (not my own images).

In my own testing, it seemed to be completely random, as I could not reproduce it even by restarting, disabling or enabling the -forceUpdate startup parameter (which fixed many other cache related bugs), or loading GM saves, even if it has happened to me previously and will likely happen again, to which I will update this thread when that happens.

Event Timeline

I could not reproduce it. Tried two times in GM. I have only the correct ones.

Geez changed the task status from New to Awaiting internal Testing.Dec 17 2024, 8:24 PM

I haven't been able to reproduce this reliably but have noticed the 2 different tables.