reported Timing Issue

[Moonshine]

found some things in some documents, sent a dm to @NineLine as i do not know if i can publicly post this here.

[GazAce]

I built a small air start mission with start time as 18:00 & yet in pit DED showing 15:00.

Short Track file attached 

AIR START VIPER MISSION TIME ISSUE b.trk

[Moonshine]

Yeah but take into account that the DED displays Zulu time and not local. So you have to calculate timezone deviation. Which after a cold start depending on how quick you are will be a difference in time of a couple seconds, maybe minutes if you take into account the difference between Zulu and local. the hour will be different, yet the minutes and seconds should be the same. on the marianas map Zulu to local is about +12h, so instead of 18.00 your plane shows 06.00. but after a finished cold start, mission time might be 18.05 and you jet will be at 06.02z or something. and thats the issue

 

Added track to demonstrate

In hot starts the time is synced as you get instant power on the jet when you start the mission. not so during cold start. you lose those seconds until the engine is running or ground power is connected, until then the watch does not tick and will not sync at all despite GPS turned on. also the mission date is in 2016, so GPS is available

 

F-16_GPS-Time_not_sync_3.trk

Edited May 4, 2022 by Moonshine

[GazAce]

1 hour ago, Moonshine said:

Yeah but take into account that the DED displays Zulu time and not local. So you have to calculate timezone deviation. Which after a cold start depending on how quick you are will be a difference in time of a couple seconds, maybe minutes if you take into account the difference between Zulu and local. the hour will be different, yet the minutes and seconds should be the same. on the marianas map Zulu to local is about +12h, so instead of 18.00 your plane shows 06.00. but after a finished cold start, mission time might be 18.05 and you jet will be at 06.02z or something. and thats the issue

 

Added track to demonstrate

In hot starts the time is synced as you get instant power on the jet when you start the mission. not so during cold start. you lose those seconds until the engine is running or ground power is connected, until then the watch does not tick and will not sync at all despite GPS turned on. also the mission date is in 2016, so GPS is available

 

F-16_GPS-Time_not_sync_3.trk 1.21 MB · 1 download

 

Ok but that wasn't Marianas, it was Syria map over Cyprus & my DED displayed 15:00 & my mission start time as I explained was 18:00. When I flew Hornet & Hog.. it didn't matter where you were or how you started.. mission start time always equaled to time in Pit.

Please kindly fix ED 

[Moonshine]

Syria is Zulu +3, that matches your description of 15.00 instead of 18.00. times are not wrong on hotstarts. and thats just the viper using Zulu time instead of local but thats correct as is.

However, if GPS time would actually be working and syncing, it would probably be like the hornet or hog. or at the very least show the correct Zulu time in sync

 

Edited May 4, 2022 by Moonshine

[TheBigTatanka]

Yes, the bug here is only on cold started jets that the GPS clock doesn't auto set the system time of the jet, as it should.

Sent from my Pixel 3 XL using Tapatalk

[RuskyV]

I wonder if the individual client systems sync from the the server and the latency or ping between clients is what is causing the discrepancy in time.

Dose this happen for single player missions too?

[_SteelFalcon_]

6 minutes ago, RuskyV said:

I wonder if the individual client systems sync from the the server and the latency or ping between clients is what is causing the discrepancy in time.

Dose this happen for single player missions too?

It‘s not the latency. Basically it is: mission running and jet cold with no power at all (no ground power, no battery etc) then the time will be off. The faster you start the jet after spawning, the smaller the deviation you have.

If you spawn cold, sit on the ground for 10 minutes and then start the jet, the clock will be horribly out of sync

[RuskyV]

Thanks for explaining @_SteelFalcon_

[Moonshine]

Any news on this?

[Frederf]

A little more info, when MMC is powered off the system time disappears from the TIME page as the system time is an MMC function. System time begins counting on MMC power so it should be possible to start UFC power first, watch DED TIME page, then turn MMC on and time will pop in the appropriate field.

[Moonshine]

that is true, however, with the GPS turned on and the MMC turned on, time should automatically sync to GPS time with no input needed from the pilot

cant publish the source here, but NL did not react to the DM i sent him yet. (probably too much in his inbox)

Edited May 10, 2022 by Moonshine

[WHOGX5]

On 5/10/2022 at 9:52 PM, Moonshine said:

that is true, however, with the GPS turned on and the MMC turned on, time should automatically sync to GPS time with no input needed from the pilot

cant publish the source here, but NL did not react to the DM i sent him yet. (probably too much in his inbox)

 

The clock in the F-16CM-50 will always resume where it left off when it was shut down. At a later point during the startup when a GPS signal has been acquired the time will be automatically set to GPS SYSTEM in the time page. If you don't want GPS SYSTEM time this has to be overridden manually on the time page.

[Moonshine]

Still does not explain why the clock wont set itself to actual GPS time with GPS turned on and it showing up as GPS on the time page

Edited May 13, 2022 by Moonshine

[WHOGX5]

12 hours ago, Moonshine said:

Still does not explain why the clock wont set itself to actual GPS time with GPS turned on and it showing up as GPS on the time page

Oh, you mean in DCS? Sorry, I was talking real life functionality. Yeah, it's obviously not properly implemented in DCS.

[Moonshine]

1 hour ago, WHOGX5 said:

Oh, you mean in DCS? Sorry, I was talking real life functionality. Yeah, it's obviously not properly implemented in DCS.

yeah, only referring to DCS as i know how it should be  sorry for the misunderstanding

[TEOMOOSE]

I recall F16s defaults to zulu, which you can convert to local times.

[Moonshine]

true as well. but even zulu time isnt correct after a cold start WITH GPS, see my tracks earlier in this post. 

[777coletrain]

On 5/13/2022 at 11:36 AM, WHOGX5 said:

The clock in the F-16CM-50 will always resume where it left off when it was shut down. At a later point during the startup when a GPS signal has been acquired the time will be automatically set to GPS SYSTEM in the time page. If you don't want GPS SYSTEM time this has to be overridden manually on the time page.

If this is the case, wouldn't it make more sense for the clock to just always show the correct time instead of simulating what it would do on start up and just always being wrong? Seems like showing the correct time when its not supposed to is the lesser evil of the two options. 

Edited June 19, 2022 by 777coletrain

[itn]

1 hour ago, 777coletrain said:

If this is the case, wouldn't it make more sense for the clock to just always show the correct time instead of simulating what it would do on start up and just always being wrong? Seems like showing the correct time when its not supposed to is the lesser evil of the two options. 

 

What makes most sense is to just implement GPS time functionality as it is on the jet IRL. In DCS missions with GPS available, I'd guess it would pretty much mean the same as "clock always correct (after some GPS acquisition delay on startup)". And without GPS in mission, you'd have to time hack as you should.

[777coletrain]

2 hours ago, itn said:

What makes most sense is to just implement GPS time functionality as it is on the jet IRL. In DCS missions with GPS available, I'd guess it would pretty much mean the same as "clock always correct (after some GPS acquisition delay on startup)". And without GPS in mission, you'd have to time hack as you should.

I agree, but I think until that stuff is implemented it would be nice to have the clock actually be useful. 

[Ignition]

Today I practiced TOS with a friend, he was on a F-18C and I had to manualy sync the clock time to his because there was 2 mintes of difference.

[_SteelFalcon_]

18 minutes ago, Ignition said:

Today I practiced TOS with a friend, he was on a F-18C and I had to manualy sync the clock time to his because there was 2 mintes of difference.

Yeah it‘s a pity. Even the same flight of F-16s. If you dont spaen in and power it on at the exact same time, your clocks are out of sync. For any actualy TOS you‘d have to do a manual sync of the clock or use the hack 

[777coletrain]

1 hour ago, _SteelFalcon_ said:

For any actualy TOS you‘d have to do a manual sync of the clock or use the hack 

Which is such a shame since it basically makes TOS useless for anything other than a ETE.

[BIGNEWY]

I have marked reported and merged with another related report. 

When we have news we will pass it on. 

thanks