'time' script command is wrong during JIP, for first few seconds
Assigned, WishlistPublic
Actions

Description

For JIP clients the 'time' script command value will start off counting from 0.0, not the real mission 'time' value.

After several seconds (about 2.5 seconds on average), it will then jump to a high value and synchronise with the real 'time' value, which could be 5600, for example.

Therefore, it is unreliable for any time dependent processes, like timeouts, etc, since you have no way of knowing which is the real time.

Details

Legacy ID: 2216109912
Severity: None
Resolution: Open
Reproducibility: Always
Category: Scripting

Steps To Reproduce

Use diag_log to continuously output 'time' value to RPT log while joining a running mission and observe jump in value after several seconds.

Additional Information

It's odd that it doesn't synchronise at the same time as public variables, before scripts start to run.

Event Timeline

Bohemia added a project: Arma 3.May 7 2016, 5:16 PM

Dr_Eyeball edited Steps To Reproduce. (Show Details)Oct 30 2013, 1:39 AM

Dr_Eyeball edited Additional Information. (Show Details)

Dr_Eyeball set Category to Scripting.

Dr_Eyeball set Reproducibility to Always.

Dr_Eyeball set Severity to None.

Dr_Eyeball set Resolution to Open.

Dr_Eyeball set Legacy ID to 2216109912.May 7 2016, 5:16 PM

Bohemia added subscribers: AD2001, Dr_Eyeball.Oct 30 2013, 1:39 AM

Killzone_Kid added a subscriber: Killzone_Kid.May 7 2016, 5:16 PM

does it count 0,1,2,5600 or 0,0,0,5600?

0,1,2,5600
(or more like 0.1,0.2,0.3,...,1.0,1.1,...,2.0,...,2.5,5600.1)

'time' script command is wrong during JIP, for first few secondsAssigned, WishlistPublicActions

Description

Details

Event Timeline

'time' script command is wrong during JIP, for first few seconds
Assigned, WishlistPublic
Actions