November 21, 20178 yr Moderator 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? Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
November 21, 20178 yr BTW.. this does sound vaguely familiar... did you cross a time zone boundary during your flight? Bert
November 21, 20178 yr Author Moderator 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 (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
November 21, 20178 yr Author Moderator 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. Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
November 21, 20178 yr 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.. Bert
November 21, 20178 yr Author Moderator Thanks Bert, much appreciated. I might raise a ticket with Carenado because to not fix such a basic error is shambolic. Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
November 21, 20178 yr 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 Bert
November 21, 20178 yr 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
November 21, 20178 yr Author Moderator 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. Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
November 21, 20178 yr 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.
November 22, 20178 yr 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.
November 22, 20178 yr 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
November 22, 20178 yr OK - tested and fixed in V5.6. Luckily, not too many seem to be bothered by this Bert
.thumb.jpeg.70674dda83c26f38738b63be9b37943e.jpeg)
Archived
This topic is now archived and is closed to further replies.