Discussion: March 4th, 2021 Development Update

This week’s development update has been released:

Use this thread for discussion of the latest Dev Update.


What are the 3 new aircraft? I have 21 now… Carenado Piper Arrow is a new one, so that’s 22… What are the other 2? Are we talking about Flying Iron’s release tomorrow as well as Just Flight’s Piper Arrow III?

1 Like

Is the glowing bug going to really fixed in the sim update 3? In the feedback snapshot states as “Started” which indicates they have just started working on it though. Or maybe the feedback snapshot is not updated?


The Garmin/autopilot item also continues to have the “Started” status after several months, so I guess it also means “not finished”. I sure hope both items will be ready in time for the update.

1 Like

Glad to see the Bleriot in the marketplace finally.


Is Sim Update 3 being released Tuesday, or did they intentionally not give a specific date today?

I though AI improvements would start with this update. Same about some minor effects (contrails and landing effects). One week and we will see what comes.

I have to voice my concern once more regarding “cloud textures pixelated and grainy” being marked as “Fixed” and not remaining as ongoing improvements.

I envy those who actually have the issue fixed but it the bug is still quite dramatic for myself, I have submitted several Zendesk reports and I get a message saying it is solved, quite frustrating!


This task is a ongoing improvement. I think every update bugs will be fixed and features added. It is done part by part.

1 Like

I just noticed that the relevant thread is also closed and moved to the Resolved Bugs section, not allowing for further discussion. This looks somewhat worrying indeed. @Jummivana Could you please take a look at this? Thanks.

It could be, but I’m not sure if they’ve said how deep they want to go with these default systems, especially now that they’re endorsing the community mods. I guess we’ll know more in the next Q&A.


Yes @Jummivana can you please acknowledge this issue, and please open back up the discussion so those experiencing the issue can potentially help each other out with mitigating it. It would really put many of us at ease to know Asobo hasn’t brushed off the issue, and it would be meaningful for it to be addressed again so us customers can know our concerns are actually being heard.


Where did you see Tuesday?

I can only see in their web friendly roadmap that its set for the 11th

Last week’s roadmap says that it’s coming on the 9th.

I think that if it were delayed then an announcement would be made in today’s update, so it’s probably just a small omission from the web-friendly roadmap.

1 Like

I see the hotfix corrected photogrammetry in the UK, but has now sporadically removed PG from all over the world. Denver is a big one for me. There are also now trees all over FSDreamTeam Chicago and FlightBeam Denver.

Why on Earth can they not just fix a bug without introducing new ones?? I’m tired of waiting for patches and fixes to fix patches and fixes that then need a patch and a fix and a workaround!



Where are these “wishes” coming from?

Screenshot of the VR bugs and issue 04MAR21 vs feedback snapshot VR

For example I can see this one in the list and I’m glad because it is paramount:

[BUG/FEATURE] Cockpit Size and World Scale in VR (217 votes)

TL;DR: The entire chain of IPD/ICD projection matrices must be cross checked with at least WMR OpenXR and SteamVR OpenXR drivers (the 2 most used) in addition to offering a user adjustable override (scale + bias factors).

But I don’t understand Martial’s answer about the “Brightness Slider”. I’m not certain he was joking or seriously not considering this an “important” feature. In my opinion (biased opinion being a developer too), what we really need in VR is not a “brightness” slider but something different:

[BUG/FEATURE] Implement a metering system better suited for VR (73 votes)

TL;DR: The Shader code behind the EyeAdaptation setting is fine in 2D but wrong in VR because of the difference between moving the head and moving the eyes.

Or maybe what is listed as a “brightness slider” in the snapshot is in fact the following, but in this case, it paramount to understand the community doesn’t want a brightness slider (well at least this is not what is voted for below).

Rather, they want a tone mapping scaler (gamma/white clipping), a color LUT adjustment in order to change the color space with similar values as XR_FB_color_space (Chromacity Primaries in CIE 1931 xy), and all the other “post processing” settings you’d find in UserCfg.opt being adjustable in the UI:

[BUG/FEATURE] Provide a Sharpen strength setting, and more post-processing effect controls in VR (127 votes)

TL;DR: Not all headsets gamut is the same and we need Tone Mapping Gama Slider + Tone Mapping Brightness Slider at a minimum (and more details in the topic)

And what about this one:

[BUG/FEATURE] FS2020 is breaking the VR golden rule: don’t move the camera, the user is (108 votes)

TL;DR: Nausea inducing and actually preventing a lot of customers flying in FS2020 in VR

And this one which is important for flying airliners or the future G3000/1000 improvements in VR:

[BUG/FEATURE] EFIS Screens Problems and Solutions for higher legibility (68 votes)

TL;DR: solutions for rendering EFIS screens with high resolution even if you don’t have a G2 and a 3090.

Or this one which is important in multi-player VR:

[BUG] Increase distance threshold to see other aircraft navigation and strobe lights at night (54 votes)

TL;DR: Bug where no other aircraft lights are displaying beyond about 5nm making an empty sky

PS: These VR topics I’ve listed above are prefixed with [BUG/FEATURE] because they are not only reporting a problem but they are also offering solutions which are readily implementable with minimal effort and time (all things considered of course).

This is at least the 3rd time the “Feedback Snapshot VR” is presenting the same items, but these are again not representative of the actual community votes as shown above.

Please note we’re still waiting for a proper VR Wishlist forum. Therefore many VR only wishlist items are listed only in the VR Bug forum instead. Therefore the snapshot is making me wondering:

  • Where were these items in the snapshot taken from?

  • Why is it the snapshot is containing entries with far less votes that those in the VR Bugs forum I’m showing above?

  • What about all the other wishlist requests listed in the VR Bugs forum?

Thank you for your hard work!

1 Like

So has anyone figured out what the other supposedly released aircraft are? We are two short.

It’s slated for the 11th of March: Development Roadmap - Microsoft Flight Simulator

1 Like

Regarding the pixilated clouds they have already said they will not be fully fixed until DX12. Until then they have reverted some of the changes they made (sharpening I think) that made it much worse. So it is kind of fixed and can’t really be improved on - until DX12.

If they don’t draw a line somewhere this list is going to become pretty unmanageable soon enough since there will always be someone not satisfied with a fix.