Discussion: Live dev Q&A January

I run a Ryzen 2700X, Gigabyte X470 board, 32GB RAM, NVMe SSD, Gigabyte RTX2080
He runs Ryzen 3700X, Gigabyte X570, 32GB , NVMe, Gigabyte GT1070.
We both have Premium Deluxe edition. He also had MSFS Standard on MS Game Pass initially. Now he has PD edition via Steam like I do.

He lives with me. We’re on the same home network / connection. We have identical data settings in game. We both use auto connect to the servers (USA East is our default). The only differences in the in-game configs are graphics settings (mine are higher) and peripherals.

We’ve also tried it from both his laptops (new late 2020 HP Spectre x360 and and older MSI gaming laptop). Also no issues there whatsoever with weather. As much as I try to break his weather, I can’t. It just works no mattery how much I switch it, turn it on and off, how I select it from the start screen (presets or custom weather). His live weather always works and always has.

So I KNOW the problem exists without a doubt for me (and many others). And I can’t get it to break and cause the issue on other computers. I can totally understand why the folks at Asobo can’t get it to break either. And they were skeptical and thinking this was user error. So I’m not holding it against them that they can’t reproduce it. Treating it as an issue with “dumb users” for months and not taking it seriously ■■■■■■ me off a bit, but not being able to reproduce it is another story.

I’ve tried with all the computers hard-wired to my router (desktops normally are hardwired to 1Gbit LAN), using wi-fi, bypassing my router and connecting directly to the cable modem, wi-fi via my phone’s hot spot. In all cases, I experience the problem on my computer, and can’t replicated with his 3 computers. I really don’t think it’s something on our end.

1 Like

In fact it can only be something on your end, triggering the failure in FS2020 somehow:

  • you do have different video cards but I doubt it has any impact unless there is a “Nvidia network layer” driver installed somewhere.
  • you do have different chipsets but I doubt it has any impact on this either, unless and related to the X570 Reverb G2 bug, there is something in the BIOS affecting the network adapter too.

In addition, you might have a few Win10 settings which are different, or some “updates” which are different between both, causing the difference at the root of this problem.

In any case, until Asobo implements a sound logging system or remote connect to your computer, I agree this is the kind of problem which will never be solved in a short time and only solved if there is a service bulletin from AMD/MS triggering a developer to reviewing his code, or if during a formal code review they spot something odd.

What leads me to that conclusion is that without actually making any changes to any of my settings, Live Weather suddenly started working last Friday night. It worked exactly as intended for all of 4 days. Then on Tuesday, it stopped working. I changed nothing. No Windows Updates or driver updates (I do those manually) occurred in that time. No in-sim settings were changed.

It went from not working for months to working perfectly to not working at all, all with zero changes on my end.

Exactly! This indicates a bug in the FS2020 code which might be just due because the lib/API they are using for the network layer is not the same between these 2 computers.

For example: they could have implemented the “try to connect” function in a way which is for example not retrying (bug/shortsighted), and the network card driver and/or Win10 config might often fail the first connect on 1 machine but never on the 2nd one.

In essence this is not in this case a FS2020 bug per-se, yet, if the FS2020 is not handling failures in the way you’re expecting, it is somewhat a FS2020 bug still. However the trigger for this bug might not be FS2020 bad code at all, but something servicing the resource from the computer to FS2020, like the network driver and/or Win10 registry setting and/or Win10 update etc…

It might have worked once or twice out of nowhere because this time, the entire software stack from the network driver to the FS2020 code was well aligned and didn’t fail 1st connection (sun eruption burst, surrounding electro magnetic fields, lower atmospheric pressure and snow storm whatever it is intrinsic or not).

In all cases, without a logging system there is not way to tell, you or Asobo neither.

And this is the point. I’ve done everything I could on my end to try to diagnose the issue without success. It’s a bug somewhere in their code. Probably a rare alignment of conditions that cause the sim to not be able to connect to the server and get the weather. In the end, it’s still a bug in the code, and not user error as Asobo had been assuming, nor is it something that users can fix. This is something they need to track down, find and fix.

1 Like

We definitely agree on this!

I’ve been a software dev for the last 27 years (in information management). On a few occasions over the years I’ve struggled to reproduce bugs that users reported and was never able to reproduce. When I finally did manage to track down the causes, in every case, it was always a problem in hte software where in a very rare, specific set of circumstances that couldn’t possibly be planned for, the bug was triggered.

It was akin to only happening when “planets aligned on a Tuesday in March where it wasn’t cloudy, the user was wearing a flowered shirt and drinking decaf coffee before 10AM” kind of thing.


Things I learned (or read between the lines):

Memory is important and can be the bottleneck (Seb). Glad I got 32GB at 4000 and CL15. Again: Check your BIOS settings. That DDR3600 you paid extra for may be running at 2166. This was true for FSX also, and it’s worth repeating. As much as quantity, memory speed and latency is critical.

DLSS. His response to the question “DLSS??” was something like “um yeah” followed by a pause implying “next question”. Disappointing and a bit condescending. This tells me there are no plans to implement DLSS or enable it in the DX12 port. Consider putting someone else on the call with Seb and Jorg. That response was bad form and really bad marcom.

XBOX, XBOX, XBOX. Seems like “it’ll be there with the XBOX version” was the answer to many questions. This tells me they are crunching on the XBOX version and barely working on the PC version updating. I’m guessing it’s behind schedule and super high priority and needs minimum DX12 functionality to run well on the lower XBOX specs. In light of the disaster that was Cyberpunk, I’m sure they are under strict orders to not release an XBOX title that runs on PC and sucks on XBOX. Given the sorry state of optimization on PC coupled with the lower XBOX specs, they have their work cut out for them. Godspeed…

XBOX is totally team red. So looks like no team green optimizations likely any time soon (DLSS, RT, etc). This is unfortunate. Maybe when the XBOX release happens they can go back to fixing all the INTC/NVDA bugs. MSFT is a business, and I try to remember that there’s extra revenue to be had by releasing the XBOX version and not much incremental revenue to be had by fixing the PC version since most of the market with PC’s have already bought it.

Replay: They’ve evidently had this among the dev team since day 1. It’s required functionality so marketing can gen up all those beautiful videos and set them to music. If the codebase has been there for so long, how hard can it be to slap on a UI and release it to us? But then again, it would be a few FTE-days taken away from the XBOX release I guess.

Weather. They consider the weather engine to be core to the sim. They are not enthusiastic about 3rd party weather addons. In light of this, the live weather bug is all the more puzzling. It’s not rare. Every time I go on a group flight, some poor guy (or 3) has the problem and has to be tutored on how to work around it. While not complicated, many people to not live their lives for MSFS, nor spend all their waking hours cruising the forums learning all the bug workarounds. Point is, it’s very common and I was shocked that they can’t reproduce a common bug (common by my observations) on a system they consider to be core functionality.

Caution to the team: The XBOX gamers are going to expect to pay their hard earned money (or unearned stimmys) on this title and expect it to work properly. If the thinking is that us “simmer enthusiasts” are nitpicky complainers, wait till gamers get their hands on this and experience all these bugs. Expect the expressions of displeasure to be much more vocal and public about CyberFlightSimPunk2021. Yes it’s pretty, but pretty only gets you so far in life.


About the Xbox launch; don’t think you need to worry too much about this.
It is only confirmed on XBox Series S/X (Not the XBox One), and those new XBox variants are more powerful than most people on PC are running (and no I’m not talking about the 1% that spent 3-5K on a specific simming machine with 5950X/10900K (which are a waste of money btw) and a RTX3090).

All the optimizations they find for the XBox will directly translate to the PC as well.

Which many of us keep saying, and have said, since the alpha.


Were the questions / answers of this Q & A ever compiled and published here? Can´t seem to find them…

i have no idea about how Asobo works internally … but if they did it the way, you describe, that would explain a lot of their quality issues. If i had to lead a devolopment team, the people who introduce bugs would be exactly the same, who had to fix them.
(and i really think, Asobo does it that way)

Spliting your team into the (lucky) guys who develop fancy new stuff and the (poor) ones, who are responsible to “clean up the mess”? No better way to ensure bad Quality …

just my opinion though …


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