Flight time differences?

[VonGuber 2]

(Sorry if this has already been discussed)

 

 

I've just noticed something that struck me as odd and was wondering about it. I've been using the "review flight" feature after a few of my missions and noticed that the mission time recorded doesn't always match the time reported in the flight log.

 

For example, I flew a mission yesterday that logged 59 minutes of flight time. When I ran through the review, it said the mission was +82 minutes. Since then, I've had at least one other flight like this. Has anyone else noticed something like this, is it just me, or am I missing something?

[VonGuber 2]

Ah, so no problem then. Good to know, thanks!

[Siggi 10]

It's always been like that. Never much bothered me, it's the CO knocking a bit of time off to account for dropping by the local establishment on the way back from a sortie.

[Bullethead 12]

Minutes seem like hours

Hours seem like days

I sho ' wish my baby'd

Change her evil ways

Einstein taught us about time dilation. It happens not only in deep gravity wells and when near the speed of light, but also in very stressful situaiton such as combat. If you go nearly the speed of light, you can circumnavigate the universe in a few decades as you seei it, but it will be billions of years to everybody esle. Same thing in combat

[VonGuber 2]

that must be it...was flying so fast my wrist watch slowed down.

[Waldemar Kurtz 1]

in Phase II the most common discrepency was because of warping. with Phase III the most common discrepency is because of mission objectives.

 

case in point: while flying a artillery spotting sortie with the DFW C.V everybody else in my flight got wiped out about 20 minutes into the mission. I got the purple words "mission objective failed". I found myself in the middle of a big fight and shot down an enemy fighter. I then flew off on my assigned patrol and shot down a pair of FE2b's. even though I was airborne for a good 50 minutes. it only counted the time from take-off until the "mission objective failed".

 

in the same manner when I was on a recon patrol I went through the whole mission successfully and after my patrol was given the purple words "mission objective complete" I figured I would go out and start looking for trouble. I shot down three FE2bs over the next 40 minutes. even after I factored in the warp-time, the 'live' flight time-- everything should have ended up at about 115 minutes. thing is, even though the mission briefing credited me for all of that flight time the FLIGHT LOG only credited me for about 45 minutes! because once I finished my mission the rest didn't count.

 

the worst example is, after successfully completing a ground-target attack with a Sopwith Camel late in the war, I found myself in a big dofgiht with D.VIIs. I got one fellow before my Sopwith Camel burst into flames and went into a flat spin at 5,000 ft. oddly enough, it jumped back to the campaign menu and it said "good job, keep up the good work". (more or less) so I deleted that pilot-- cuz he most certainly bought the farm!

 

it's a glitch in the game.

 

the flight log, for whatever reason, didn't count any of the time after you finished your main objective... and that was probably the time it took to get back home and land. my solution to this has (depending on my mood) been one of the following:

 

1. don't fullfill the mission objectives, thereby preventing the clock from stopping.

2. manually editing my pilot's log afterwards to reflect the actual flight time.

 

(the latter obviously relies heavily on 'honor' and honesty to be credible... but I find that if I'm going to be denied multiple aerial victories I should AT LEAST get the flight time!)

[77Scout 3]

Maybe in Phase 4, the OFF Manager could work with the time values from the 'mission review' data to avoid this problem.