Fantastic update and the bug fix map looks great. 

Well they fixed the tall building problem or copy pasted the third party that fixed it.

43 minutes ago, bean_sprout said:

They are probably started but you don't know about it yet.

bs

There are *8 categories* so pretty sure we'd know about it. NOT STARTED see to be the recurring theme... 😞

 

• NOT STARTED – We have not started to investigate this issue yet.
• FIXED – This issue is fixed and ready to be implemented in an upcoming patch.
• WIP – This issue is a Work In Progress. This means the development team is actively working on fixing or building the bug/feature.
• UPDATE #X – The bug/issue will be released to the public in that patch version number.
• BACKLOG – A database of items we plan to work on in the future.
• TO BE INVESTIGATED – Work is needed on our end but we are planning on triaging the issue.
• STARTED – Work has already begun and we are looking at the issue.
• UNDER INVESTIGATION – Actively being triaged by the development team.

9 minutes ago, bean_sprout said:

CTD's are your computers problem - not FS2020's.

bs

Rest assured that with my better half I did not mean my computer. The missing r in Cash to Desktop was not a typo in the context of my previous post 😏

4 minutes ago, Flyfaster said:

This means the development team is actively working on fixing or building the bug/feature

Well, that may make some posters veeery  nervous 😬 

Edited October 8, 20205 yr by DAD

I find it rather impressive to have this much listening and transparency with the community. Usually development studios dont listen to much of the communities needs and wants or concerns. Usually have their own agenda. The least we can do is respect the process and understand that theres often no instant fix for issues, which leads to complex investigations and in turn the coding to fix without breaking something else. Thanks for the detailed roadmap and the continued work and progress.   Great to be a part of flight simulation in 2020

33 minutes ago, Frostbitexp said:

They literally said theyre improving live weather constantly. So yes.

I don't see it in the list of items they are working on

1 hour ago, bean_sprout said:

You may have noticed that there are many issues that are not started.  These represent to me things that are are not fixed to issues that will be fixed.  We are on the right path IMO.

Cheers

bs

I think the feedback is a bit ambiguous to be honest. If something is NOT STARTED / BACKLOG - what does that actually mean. It could be they have created a JIRA for it, but that JIRA could be nothing more than a spike which gets canned if they don't think there is any value in continuing effort. I'd like to know if something is acknowledged or have they just seen a post and created a backlog task?

Opinions great community...

Edited October 8, 20205 yr by dtrjones

Great update! Now to login to P3D forums for their weekly - oh wait

Edited October 8, 20205 yr by suncoastflyer

17 minutes ago, sd_flyer said:

I don't see it in the list of items they are working on

Quoted from a community manager at the MSFS forum:

do think it’s worth pointing out that Asobo is also hard at work on other fixes/updates outside the Feedback Snapshot. The FS does cover the community items but it is not an exhaustive list of -everything- they are working on. Of course we are slowly working towards being transparent about everything.

Why is it that some of the most discussed issues are not even mentioned?  Logbook issues and editing?  10° issue with flight controls.  Feature to change position airport without returning to Main Menu.  Missing RNAV approaches in the Garmin avionics (or database).  Are they not paying attention to where the energy has been to assemble mods to overcome native issues?

Today I completed two flights and the logbook shows no landings and the destinations are grass strips 25 to 30 miles from the airports I landed at.

Excellent update!

Edited October 8, 20205 yr by Schwarzgruber

3 minutes ago, fppilot said:

Why is it that some of the most discussed issues are not even mentioned?  Logbook issues and editing?  10° issue with flight controls.  Feature to change position airport without returning to Main Menu.  Missing RNAV approaches in the Garmin avionics (or database).  Are they not paying attention to where the energy has been to assemble mods to overcome native issues?

Today I completed two flights and the logbook shows no landings and the destinations are grass strips 25 to 30 miles from the airports I landed at.

Oh no! you may have to use an actual log book... 🙂

Per weather and that it has been under constant refinement?  I had live weather today that was representative, because the weather in my two routes was clear.  That is what I saw from the cockpit. One was a 2 1/2 hour west to east flight in the USA.

However I tuned in several ATIS/AWOS  freq's along the way and each was reporting a cloud layer at somewhere akin to 1,000 to 1,200 (varied from station to station perhaps due to airport elevation), another around 5,000, and another at 10,000 to 12,000.  Nothing like that in the metars or in view. 

I got altimeter settings that were representative of live metars from FltPlan Go, but the AP in the G36 leveled from all altitude transitions at altitudes based on 29.92 pressure, not based on my altimeter settings.  So I learned to leave the altimeter at standard pressure.

Embarrassing.

9 minutes ago, Flyfaster said:

Oh no! you may have to use an actual log book... 🙂

That is not the point.  SE!

Edited October 8, 20205 yr by fppilot