Weather not updating when using sim rate in historical live-weather

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

3 tags are required - add them in the tag section next to the title above:

  • One for iteration (msfs-2020 or msfs-2024)

  • One for platform (ms-store, steam, xbox , or xcloud)

  • One for aircraft if related (start typing in your aircraft name in the tag section and pick correct option)

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

Description of the issue: When I use sim rate, the clock accelerates correctly, so the time is correct. However the 24h-weather does not update accordingly with the in-sim clock. This is noticeable in the metars in the EFB - they will not be from the time the in-sim clock shows. When clicking the weather tab, it will move the time back.

What it SHOULD do:
Weather will advance in the same sim rate. So after 30 minutes of 4x sim rate, weather (and metars) should also be 2 hours later.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)? Always

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Set the clock to 0600 UTC (needs to be in the past, so not live and not future weather). Fly for 30 minutes in sim rate 4x. In-sim clock will now show 0800 UTC (4x 30 minutes later).

  2. Open the EFB and select the weather tab on any airport. The EFB metar will now show metars from around 0630 UTC (so the 1x time that has passed) and not from 0800 UTC.

  3. When you now click the weather toolbar tab, the in-sim time will instantly move back to 0630 UTC.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using: Joystick and Throttle and Rudder

[PC Only] Are you using Developer Mode or have you made any changes to it? No

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

[PC Only] What GPU (Graphics Card) do you use? 4070

[PC Only] What other relevant PC specs can you share?

MEDIA

Please add a screenshot or video of the issue occurring.

Title updated replacing “non-live weather” by “historical live-weatther” to avoid confusion with custom weather (presets).

1 Like

I have exactly the same issue. Is this logged as a bug?

Bump - could we get acknowledgement that this has been logged as a bug?

It’s incredibly easy to replicate - just use sim rate for a bit when flying with historic weather. Upon arrival, the METAR timestamp on the EFB will be hours behind the time indicated in the sim, as the weather/METAR time always progresses at 1x, even when using sim rate 8x.

No mention of this being fixed in the SU5 release notes.

Can we please at least get some kind of recognition that this is a logged bug? It’s incredibly easy to replicate and happens every single time when using sim rate with historical live-weather.

In case it’s not clear what the issue is - here’s a scenario:

Real time of flight: 13-Feb 2026, 21:00z to 22:00z using sim rate 8x on any aircraft

Departure time in sim: 13-Feb, 10:00z from EGLL

Arrival time in sim: 13-Feb, 18:00z at KMIA

Flight time was 8 hours in sim time, 1 hour in real time using 8x

Sim time correctly shows 18:00z when landing.

Metar shows 11:00z as it never synced to 8x and continued to move at 1x. Doesn’t matter how long one flies from that point onwards at 1x either, the Metar will now always remain 7 hours behind the sim time. This happens every single time when using sim rate. Either fix it so the Metar syncs to sim rate or do regular checks when using historic live-weather to sync it back to sim time. The way it’s now is really frustrating and broken - it defeats the whole purpose of this feature when flying at more than 1x.

I hope that makes sense. Would be wonderful to get this fixed.

Can replicate following OP steps.

1 Like