59 minutes ago, Cpt_Piett said:

Good point. There are many reports of excellent DX12 performance for AMD users. Like the example I posted recently (can't remember which thread). I expect this will come to us nVidia users as well. We'll just have to wait a little bit longer. 

Wow, that's very negative Bob. I don't share that view. 

Well let's see, SU10 was supposed to be released weeks ago. Whenever the delayed release is mentioned, DX12 seems to be the problem. Now they are saying it is NVidia holding up the release. Then I guess  after Nvidia releases the new driver, the beta testers will have to see if it causes problems, so a further delay will probably be the result. 

I mostly sit back and observe just as I do as a check airman. I must say, people in flight sim get riled up easily and resort to torches and pitch forks quick! Funny thing is that we are not that way in real aviation and didn't see it to this extreme during my military aviation.🤔

5 hours ago, Bobsk8 said:

Well let's see, SU10 was supposed to be released weeks ago. Whenever the delayed release is mentioned, DX12 seems to be the problem. Now they are saying it is NVidia holding up the release. Then I guess  after Nvidia releases the new driver, the beta testers will have to see if it causes problems, so a further delay will probably be the result. 

They said they want to release SU10 at the same time as the driver. So the beta testers won't be able to test it before launch.

7 hours ago, ChaoticBeauty said:

If they keep posting them at 3:00 AM in my timezone (same as last week)

Which timezone? The MSFS twitter posted it at 8PM eastern, which I think is the normal time or close to it.

Edited September 16, 20223 yr by Tuskin38

7 hours ago, Bobsk8 said:

I suspect that this SU10 will be delayed forever until they figure out how to make DX12 work properly, which might be never. 

It’s all ready working perfect on AMD graphics cards. 
Just needs the nvidia drivers. 

54 minutes ago, Tuskin38 said:

Which timezone? The MSFS twitter posted it at 8PM eastern, which I think is the normal time or close to it.

GMT+2. The Twitter post announcing yesterday's update is showing me 3:06 AM.

Usually they are posted between 12:00 AM and 2:00 AM, but the last couple of months it's very often been later than that.

15 minutes ago, ChaoticBeauty said:

GMT+2.

Funny. Always thought you are US based. Maybe just because you were always posting the blog updates within minutes after they were published. So you are rather European based then?

35 minutes ago, DAD said:

Funny. Always thought you are US based. Maybe just because you were always posting the blog updates within minutes after they were published. So you are rather European based then?

That is correct! Usually my Fridays are not very busy so I can stay up to check out the updates and then post them here, but with these new times it becomes very difficult.

45 minutes ago, ChaoticBeauty said:

with these new times it becomes very difficult.

Fully understood and hats off then for staying up so late. Now just a proper handover to David and your blog post retirement can start 🙂

13 hours ago, Matchstick said:

The explanation for holding all the releases - "To align with SU10 dependencies" - seem to make absolutely no sense when don't appear to be able to commit to releasing SU10 next week.

There's no crazy conspiracy here; the majority (all?) of submissions for inclusion have been built with SU10 now and thus have a dependency version in the package of the SU10 minimum, and would not show for folks on the retail release.

Just now, MattNischan said:

There's no crazy conspiracy here; the majority (all?) of submissions for inclusion have been built with SU10 now and thus have a dependency version in the package of the SU10 minimum, and would not show for folks on the retail release.

And would be there released ready for them the moment SU10 was installed rather than having to wait for the next Thursday to come around.

Not seeing a problem really.

1 minute ago, Matchstick said:

And would be there released ready for them the moment SU10 was installed rather than having to wait for the next Thursday to come around.

It is not technically possible as it stands to do this given the way the beta environments are set up and pushing those into retail environments poses risks regarding version number changes and other package dependencies in the graph. If you've used things like NPM, apt, yum, etc, then you know what I'm talking about taking pre-release packages into your dependency tree and what issues that can cause if those get deprecated, moved, re-versioned, etc.

Just now, MattNischan said:

It is not technically possible as it stands to do this given the way the beta environments are set up and pushing those into retail environments poses risks regarding version number changes and other package dependencies in the graph. If you've used things like NPM, apt, yum, etc, then you know what I'm talking about taking pre-release packages into your dependency tree and what issues that can cause if those get deprecated, moved, re-versioned, etc.

Sorry not buying that at all - not least what's supposed to happen if SU10 can't release before next Thursday - are MS getting themselves into a state where they can't update the marketplace again until after SU10 comes out ?

1 minute ago, Matchstick said:

Sorry not buying that at all

As it turns out, that's somewhat immaterial if you buy it or not. 😉

The reality of package management, in any modern package manager, is that you don't want to release a bunch of packages that will then cement dependencies into pre-release package versions that may be volatile. Since stuff submitted has been presently built on SU10 (by the submitting developers, mind you, this isn't a MS-side thing), there aren't packages available to be updated against non-prerelease package dependencies at this time.

Just now, MattNischan said:

As it turns out, that's somewhat immaterial if you buy it or not. 😉

The reality of package management, in any modern package manager, is that you don't want to release a bunch of packages that will then cement dependencies into pre-release package versions that may be volatile. Since stuff submitted has been presently built on SU10 (by the submitting developers, mind you, this isn't a MS-side thing), there aren't packages available to be updated against non-prerelease package dependencies at this time.

Sorry, I'm a professional dev (Biztalk Middleware) and I'm not getting your point at all. 

The dev content that's not being release is already submitted and the dependencies were baked in (using current version of the SDK at that point in time) at the moment the packages were compiled and sent to MS.

Sure MS might be delaying release so they can finalise a new encryption layer but that not the explanation they've given us.