Common - Fix CBA_missionTime in long missions (above 7 days)

[commy2]

When merged this pull request will:

• alt FIX: CBA_missionTime time leak #1320

I have no tested this yet, so there may be typos. It should all be as simple as this though, unless I am missing something.

[Vdauphin]

Definitely this PR simplify the CBA_missionTime update and resolve CBA_missionTime being stuck due to tiny add of value to a big number.

But, I feel it missing the opportunity to give support to do addition/subtraction/comparison of two big number without lost of precision or unintended results. I prefer the vector representation of the time for precision (math operation give us the necessary to deal with) and the classic number representation for backward compatibility. Also this representation give the possibility for mod to choose the time representation they need.

[Vdauphin]

Looks good otherwise
Looks like the CBA_missionTime is accurate around +-1s when time is above 1e7 (115 days)

[commy2]

@Vdauphin

        _elapsedTime = my_oldTimeString call CBA_fnc_missionTimeDelta;

        _deltaTime = [my_oldTimeString, my_newTimeString] call CBA_fnc_missionTimeDelta;

        _missionTime = [] call CBA_fnc_missionTimeDelta;

[Vdauphin]

Nice!
Do you plan to migrate CBA_fnc_waitAndExecute and PFH to this?

[commy2]

WAE and WUAE sure, but PFH uses tickTime, not missionTime (does not suspend or accelerate in SP, starts from game start, not mission start, is not synchronized).

[mharis001]

I think this is better written as:

Suggested change

	if ([GVAR(missionTimeSynchronized), time > 0, isGamePaused] isEqualTo [true, true, false]) then {
	if (GVAR(missionTimeSynchronized) && time > 0 && !isGamePaused) then {

[commy2]

Isn't that slower though? That shit runs every frame.

[mharis001]

It is slightly faster.

Result:
0.0028 ms

Cycles:
10000/10000

Code:
[cba_common_missionTimeSynchronized, time > 0, isGamePaused] isEqualTo [true, true, false]

Result:
0.0021 ms

Cycles:
10000/10000

Code:
cba_common_missionTimeSynchronized && {time > 0 && {!isGamePaused}}

[commy2]

What was cba_common_missionTimeSynchronized in your example? It will be true all mission long.

[mharis001]

It was true; the overall result for both statements was also true.

[dedmen]

hows the speed without the lazy eval?
creating array, calling "true" command 3 times, creating another array, calling isEqualTo command surely is a bit expensive.
But lazy eval is also expensive but in this case as commy said, we don't expect neither missionTimeSynchronized or the time check to ever be false, so why lazy eval?

[mharis001]

Yeah, no lazy eval is the fastest.

Result:
0.0017 ms

Cycles:
10000/10000

Code:
cba_common_missionTimeSynchronized && time > 0 && !isGamePaused

Updated the suggestion.

[jonpas]

Status?