Flight Clock Reset

[Richard Rodgers]

Evening guys.

 

When flying multiplayer my friends and I have the situation that out Flight Clocks all show different times. This is obviously due to the fact that if we have say a mission start time of 12:00:00, that is the time that the clock will start from once the sim is running. No matter when a player starts their sim.

 

For normal general flying this is not an issue, but when times are brought into a targeting equation eventhough we are all in the correct place at the correct time(according to our individual clocks) we are all over the place time wise in reality.

 

Is there any way that the sim clock can be reset once the aircraft is ready to taxi so that we could then all re-sync at the same time.

 

I know that the Sim clock can also be used as a stopwatch and in some ways that would solve our problems, but that then causes another issue in that eventhough I can change to stopwatch, it does not display this in the HUD. It still displays the flight clock.

 

Here's hoping that either there is a reste option for the clock or the HUD can be set to display the stopwatch instead of the clock.

[PFunk1606688187]

Hack time perhaps?

 

Its part of the aircrafts systems for a reason, and it displays on the HUD.

 

 

A-10C Manual, Page 254:

Time Hack (HACK). Depressing the HACK button enters the HACK mode and displays

the Hack Time-To-Target value boxed on the lower right side of the HUD. Depressing the

HACK key again returns the display to real-time mode. Hack time can be adjusted by using

the DATA rocker switch to adjust hack time and depressing the ENT key to accept. Hack

time may also be entered manually via the scratchpad and depressing ENT to accept.

Reference the HUD section for more detail on the HACK function.

[NoCarrier]

Here's hoping that either there is a reste option for the clock or the HUD can be set to display the stopwatch instead of the clock.

The UFC has a HACK function you could try. I suggest you take a look in the A-10C flight manual. As for the different multiplayer clock times, that's an issue that's been identified long ago. It's one of those things that's still in need of fixing, unfortunately.

 

EDIT: dagnabbit, P*Funk!

[Richard Rodgers]

Thanks for the quick replies guys. Awesome group of people on here!!!

 

Will have a play with the hack time thingie, but after a quick look at the manual it looks like it will only do one timing rather than being able to set timings for each waypoint as per the DTOT system.

 

I will just throw something out there if I may. when our group used to use FS9 we had multiplayer function via FSHost. This was running on a separate PC acting as a flight server. When a player joined the session, all weather, season, date and time data was pinged to his FS and his setup altered automatically to be insync with the server.

 

If we were to set up a dedicated DCS server rather than one of our group simply hosting a session on his PC, would each of us automatically sync to the server the same as we used to with FSHost?

 

My guess it that we would not as sadly nothing like this seems straight forward in DCS and multiplayer.

[NoCarrier]

If we were to set up a dedicated DCS server...

No such thing, unfortunately. Once again, something in dire need of fixing.

[Dejjvid]

I know time differs between Ka-50 and A-10C by one minute. But i've not noticed difference while in game. But then again, when we do serious missions we start at the same time.

 

HACK works like a charm.

[Thymo]

Tochange the flightclock go on the ufc: func -> nav then cdu -> time

[PFunk1606688187]

Hate to break it to everyone but more stuff MAY be broken.

 

#1 - HACK time: On the face of it it works fine, but it exhibits peculiar behavior. It appears as though the timer begins when you press HACK regardless of any other inputs, even if you enter no countdown time.

 

To replicate the behavior do the following:

-Press HACK

-Enter any time in the Scratchpad

-Press the Enter button on the UFC once to display the time to be counted down

-Press Enter again to begin the countdown

 

What you will see however is that your selected time has skipped ahead in the countdown by the number of seconds since you first pressed HACK, ie. if it has been 20 seconds since you pressed HACK a 60 second countdown will begin at 00:40 instead.

 

Its still functional, you just have to enter the desired time first, turn off the HACK timer, then only press HACK when you want to start the countdown, at which point pressing Enter will reveal the timer's true progress.

 

#2 - CDU Time Page: From the Nav page you can access the Time page. It has some limitations first of all. At LSK3 you can enter a time offset of 4 numbers that corresponds to HH:MM. There is no facility for altering the seconds. Default entry creates a positive time offset. Pressing the LSK again makes it a negative offset.

 

Here's the bug. Every input appears to be doubled. If you enter 0001, which should add 1 minute, it instead adds 2 minutes. If the time is 12:00 then the offset time is now 12:02. If you enter 0100, which ought to add 1 hour, the time is instead 14:00.

 

 

 

These are my quick observations, anyone feel free to prove them wrong. Its conceivable that this is how HACK is meant to function... though it doesn't rightly make a whole lot of sense to me right now, so I'll sleep on it. The CDU Time thing however can be nothing but a bug.

Edited March 3, 2014 by P*Funk

[Flagrum]

Hate to break it to everyone but more stuff MAY be broken.

 

#1 - HACK time (...)

 

#2 - CDU Time Page (...)

The behaviour of the HACK time function is correct the way it is. It helps to synchronize your timers between flights. This way you don't have to worry of how long each pilot needs to enter the time.

 

But the CDU LCL time adjust seems really broken. If you enter 0001, it adds 2 minutes, if you enter 0002 it adds 2*2 minutes, enter 0003 it adds 2*3 minutes ... and so on. We should post this in the bug section of the forum.

Edited March 3, 2014 by Flagrum