April 25, 2024 MSFS Development Update

[MarcG 3,033]

52 minutes ago, Krakin said:

Appeals to worse problems is actually an argumentative fallacy. You take every opportunity you can to bash MS/Asobo. I found it amusing when you suggested recently that they hire a head QA tester like iniBuilds just did, as if they don't have one already lol. I guess bashing them is the fun thing to do but they there's nothing wrong with them asking for David's cooperation even though their forum has issues.

@David Mills I'd suggest sharing this information with the mods here in case others try to do it anyway.

Likewise any chance to bow at the feet and kiss the ground Asobo walk on you can guarantee I'll see you there 😉 

We're all entitled to our opinions, when I see issues created by Asobo I'll speak up and not pretend everything's pretty flowers & unicorns thank you 🙂

[Krakin 5,850]

1 hour ago, MarcG said:

Likewise any chance to bow at the feet and kiss the ground Asobo walk on you can guarantee I'll see you there 😉 

We're all entitled to our opinions, when I see issues created by Asobo I'll speak up and not pretend everything's pretty flowers & unicorns thank you 🙂

I never said you weren't entitled to your opinion, I just commented on why I thought it didn't make any sense and I pointed out your proclivity to bash Asobo with evidence while you fired back with unsubstantiated hyperbole. When someone enquired about the land bar issue being fixed, you chimed in to say Asobo won't fix it, only for someone else to point out that they did in the SU15 beta (oops!). That is what I'm talking about. They never told you they weren't going to fix it but you chose to bash anyway with ZERO evidence. I give them props where it is due and when things need to be fixed, I give them hell about it too, like third party updates taking forever to hit the content manager, the current overly transparent cloud depiction and being one of those who led the charge on social media to make them aware of Biology's atmospheric lighting fix.

As myself and others have pointed out to you, it makes no sense trying to make this more than what it is. Why not stop and see the positives? It turns out they DO pay attention to what we say here on Avsim lol. I see nothing wrong with them wanting to have the most accurate information available to users.

[MarcG 3,033]

Alllllrighty then 

[bobcat999 8,509]

Yet the DX12 tiling issue persists after 18 months, and they were totally confused by it again on the last twitch session.  I don't get it. 
The 18 months worth of posts on their own forum are quite clear what the problem is, with photos and video.

[topcat_1952 24]

So, trying to find the latest release date for SU_15. Seems to be a deep, dark secret. Does anyone know? I thought it was supposed to be today (May 7th), but nothing.

[JRBarrett 3,128]

24 minutes ago, topcat_1952 said:

So, trying to find the latest release date for SU_15. Seems to be a deep, dark secret. Does anyone know? I thought it was supposed to be today (May 7th), but nothing.

They never said it was going to be today (May 7th). They said the week of May 7th, which could be as late as May 13th. And, that was always marked “tentative”, meaning it was not guaranteed. 

[Tuskin38 6,635]

1 hour ago, topcat_1952 said:

So, trying to find the latest release date for SU_15. Seems to be a deep, dark secret. Does anyone know? I thought it was supposed to be today (May 7th), but nothing.

https://forums.flightsimulator.com/t/sim-update-15-delayed/640816

[Krakin 5,850]

On 4/28/2024 at 2:21 PM, bobcat999 said:

Yet the DX12 tiling issue persists after 18 months, and they were totally confused by it again on the last twitch session.  I don't get it. 
The 18 months worth of posts on their own forum are quite clear what the problem is, with photos and video.

fixed now 🙂

[bobcat999 8,509]

52 minutes ago, Krakin said:

fixed now 🙂

Yes, great! 

I will probably switch to DX12 now.

Although I raised it again on the last twitch session (it was my question asking about the issue), I credit this finally getting fixed  to Jayne (the community manager), as they brushed the question aside again when it was first asked, with Martial even saying 'well, DX12 is still in beta'.  But Jayne wouldn't let it go as she seemed to realise they hadn't understood the issue properly, so they finally investigated further and have now fixed it.  Superb.

[MarcG 3,033]

13 minutes ago, bobcat999 said:

Yes, great! 

I will probably switch to DX12 now.

Although I raised it again on the last twitch session (it was my question asking about the issue), I credit this finally getting fixed  to Jayne (the community manager), as they brushed the question aside again when it was first asked, with Martial even saying 'well, DX12 is still in beta'.  But Jayne wouldn't let it go as she seemed to realise they hadn't understood the issue properly, so they finally investigated further and have now fixed it.  Superb.

A shame it's taken nearly two years and persistent badgering then if they managed to fix it so quickly, so either (A) they've been working on it for a while and it's just coincidence that it got fixed this week or (B) they sat on their hands with the issue since the first report, heard it mentioned again in a Q&A and decided to spend a couple hours looking into it before finding a cure.

No one will know for sure, but to keep repeating issues to the Q&A for them to take notice is not the way to go about fixing bugs, they simply must've known about this through the hundreds of reports on the official forum. Yet again they pose more questions about the way they deal with Bug Reports but hey at least it's fixed, that's something right!