Flight Time 1h 65m?

[Ray Proudfoot 8,954]

I started the clock on the transponder after engine start and noticed towards the end of my flight it was showing the elapsed time as 1h 65m. 

Did I do something wrong in starting the timer or is this a known bug?

[Bert Pieke 7,585]

My guess is that it is a bug.. I will have a look..

[Bert Pieke 7,585]

BTW.. this does sound vaguely familiar... did you cross a time zone boundary during your flight?

[Ray Proudfoot 8,954]

2 minutes ago, Bert Pieke said:

BTW.. this does sound vaguely familiar... did you cross a time zone boundary during your flight?

Hi Bert,

My flight was from LGTS to LIBD. (Thessalonika, Greece to Brindisi, Italy. Possible time zone change as Greece is 2h ahead of GMT and Italy 1hr.

[Ray Proudfoot 8,954]

Bert,

Crossing a time zone shouldn't affect it should it? Just count elapsed time. Perhaps I'm the only person who starts the flight timer.

[Bert Pieke 7,585]

Hi Ray, this was a problem in the FSX version, where I fixed it, and it has carried over to the P3D version, where I get to fix it once more.  Carenado are aware, but cannot be bothered..

The transponder uses the "local time variable" whereas the better way is to use UTC time...

I'll send you a replacement transponder, and roll it into my ongoing "mod package" as well..

[Ray Proudfoot 8,954]

Thanks Bert, much appreciated. I might raise a ticket with Carenado because to not fix such a basic error is shambolic.

[Bert Pieke 7,585]

39 minutes ago, Ray Proudfoot said:

Thanks Bert, much appreciated. I might raise a ticket with Carenado because to not fix such a basic error is shambolic.

Please do!

The more they hear this from their customers, the better

[scottb613 1,188]

1 hour ago, Ray Proudfoot said:

Thanks Bert, much appreciated. I might raise a ticket with Carenado because to not fix such a basic error is shambolic.

Hi Ray,

Just be aware of standard response number one: “Thanks for the report we’ll consider your suggestion in future updates.”

Regards,

Scott

[Ray Proudfoot 8,954]

4 minutes ago, scottb613 said:

Hi Ray,

Just be aware of standard response number one: “Thanks for the report we’ll consider your suggestion in future updates.”

Regards,

Scott

Well except it’s not a suggestion but a bug report. I’m not easily fobbed off. I shall mention this is my first Carenado product and possibly the last if there basic errors like this.

[Holdit 551]

7 minutes ago, Ray Proudfoot said:

Well except it’s not a suggestion but a bug report. I’m not easily fobbed off. I shall mention this is my first Carenado product and possibly the last if there basic errors like this.

It'll be the last, so.

[Gabriellc 4]

2 hours ago, Holdit said:

It'll be the last, so.

You are very right, lol

[FDEdev 955]

2 hours ago, Ray Proudfoot said:

Well except it’s not a suggestion but a bug report. I’m not easily fobbed off. I shall mention this is my first Carenado product and possibly the last if there basic errors like this.

If this 'basic/shambolic' issue is a no go for you I'd stay far away from any Alabeo/Carenado product in the future.

[Bert Pieke 7,585]

6 hours ago, Bert Pieke said:

 

The transponder uses the "local time variable" whereas the better way is to use UTC time...

 

As I look into the code, I see that they took some shortcuts as well...

The minutes are calculated as the seconds / 60.

That works until you go over one hour and get 61 minutes... as you found out.

A fixed version is in test - just waiting for 60 minutes to go by...

[Bert Pieke 7,585]

OK - tested and fixed in V5.6.

Luckily, not too many seem to be bothered by this