Career weather -- Departure airport not using recommended RWY

If someone know where this is already logged, let me know and I’ll move it.

ISSUE DESCRIPTION

Description of the issue:

See screenshot.

Tower assigned RWY with dangerous crosswind instead of RWY with almost direct head wind.

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?

No add-ons

FREQUENCY OF ISSUE

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

1st time it happened. Given the randomness of real weather I don’t know how often this happens.

REPRODUCTION STEPS

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

  1. Y’all really need to update this form to take into account random events based on using real weather.

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, if relevant:

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

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

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

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

MEDIA

Please add a screenshot or video of the issue occurring.

[END OF FIRST USER REPORT]


:loudspeaker: 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:

What was the scheduled mission time (you’d also see this as the UTC time in your aircraft)? And what real-world UTC time and day did you actually fly the mission? I have a hypothesis as to why it’s doing this based on some things I’ve seen and am trying to confirm it.

My hypothesis is that the mission start time was scheduled for around 22z (2:00pm local, PST). But the other half of this depends on what time it was when you actually flew the mission, which was likely between 22z on the 16th and now (18z on the 17th).

I don’t know of any way to check the scheduled time, but I accepted the mission around 0800 local (Los Angeles).

1 Like

Ok, well, I can almost guarantee your mission time was 22z, here was the real-world METAR for that time (would have been from the 16th, within the past 24h prior to the flight):

21012G22KT 7SM SCT017 BKN033 05/01 A3005

Whereas the METAR for your live session at 16z today (12/17) would have been:

00000KT 1/4SM FZFG OVC002 M04/M04 A3039

My hypothesis is that the sim uses the historic weather that existed at the scheduled mission start time - I’ve actually proven that to near certainty. However, the ATC and AI are not always synced to that and my corollary to that is they are possibly using the live METAR to give instructions/expectations, which in this case is 18 hours difference. This needs to be tested more - would be nice if the winds weren’t calm in one of them, haha.

1 Like

One other thing I noticed is that the EFB date was in August, whereas if I fly a real weather mission the EFB shows a correct date and (I think) time.

Our friend CharlieFox00 might be onto something.

Before starting a mission, I always review the route, SIDs, and STARs, making any necessary adjustments based on live weather conditions before submitting them to ATC. Another approach is to accept missions with the red dot in the corner of the icon.

1 Like

I made a much longer post about my findings regarding how the time slider and red dots seem to behave. It includes some additional related, but unverified observations about ATC/AI pathing.

Some caveats in there, too - we could use more testing outside the areas on which I focused, and it only applies to post-IFR cert and missions that don’t use presets.

This topic was automatically closed 360 days after the last reply. New replies are no longer allowed.