ISSUE DESCRIPTION
Description of the issue:
During a flight, the elapsed time shown in the EFB and in the Garmin Display slowly drift apart. The longer the flight, the greater the variation between the two clocks.
[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
No 3rd-Party or Community Addons (default installation) / Yes
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every time
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
- Start a flight cold-n-dark at any airport (daytime preferred just for visibility), any weather (not important for this test) in the Cirrus SR22 (this was the aircraft in use at the time, but this issue likely will be noticed in others too).
- Start the engines & enable the avionics.
- Open the EFB & start the timer
- On the Garmin display, click on the Tmr/Ref button & start the time - try to do this as quickly as possible after starting the timer in the EFB
- Fly for an hour (or perhaps just let the aircraft sit at the parking spot for an hour - Flying the aircraft may not be a requirement to test this). Note the time variation between the two timers.
- Fly for another hour (or perhaps just let the aircraft sit at the parking spot for another hour). Note the time variation between the two timers has increased even more.
In the screenshots below, #1 shows the Garmin at 55 mins 17 secs, the EFB at 56 mins 59 secs. Allowing for 5 seconds to move the mouse between the two timers when I started them, that gives a variation between the two timers of 1 minute 37 seconds.
In Screenshot 2, the Garmin is now at 2hrs, 9 mins 5 secs, the EFB at 2 hrs, 13 mins 10 secs - a variation between the two timers of 4 minutes.
This makes VFR navigation using the timers unreliable - a 4 minute difference at, say 175 knots will put you about ~11 NM away from where you actually are, if my math is correct. (I’m not sure which timer is correct, if indeed one is actually correct - I have not tested by running the timer in the Windows Clock App to see if that matches either of the two in-game timers).
YOUR SETTINGS
What peripherals are you using, if relevant:
N/A
[PC Only] Are you using Developer Mode or have you made any changes to it?
Developer Mode is Off / No changes
[PC, MSFS 2020 Only] Are you using DX11 or DX12?
N/A
[PC Only] What GPU (Graphics Card) do you use?
Intel Arc 770 (16GB, v32.0.101.6314)
[PC Only] What other relevant PC specs can you share?
Build: v1.3.13.0 (Although this is an SU1 Beta Build, I do not think this issue is specific to the Beta)
Hardware: i7-12700K (No overclocking or undervolting), 32 GB 5200 MHz DDR5 CL40
Online Tab: Photogrammetry, Live Weather - On, Air Traffic Type, Air Traffic in Career, Multiplayer - Off, MP Servers - West USA, Show MP proximity - On, Rolling Cache - On @ 16GB, Bandwidth - Unlimited.
Flight configuration: Weather: Live, Traffic: Off, Multiplayer: Off
MSFS Version: MS-Store, Premium Deluxe
Graphics Tab: Display: Full Screen; HDR10: On; Full Screen Res: 3840 x 2160; AA: TAA; Render scaling: 65 (Resolution: 2496 x 1404); AMD FidelityFX: 150; VSync: Off; FRL: N/A; Dynamic FRT: Off; TLOD: 400; OST Pre-Cache: Ultra; Disp. Map: On; Buildings, Rocks: High; Trees, Plants, Grass: Medium; OLD: 200; V. Clouds: Ultra; Texture Res: Medium; AF: 4x; Water: Medium; RayTracing: On; SM: 2048; TS: 512; CS: High; WE: Medium, AO: High; CR: 256; RR: Medium; LS: High; DoF, MB: Off, GCRR: High; CQ, TAQ, AT, RT, ST: Medium, Fauna: Off.
MEDIA
Please add a screenshot or video of the issue occurring.
[END OF FIRST USER REPORT]
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
•
Provide extra information to complete the original description of the issue:
•
If relevant, provide additional screenshots/video:
•