It a shame Bob is seeing diffrent on his screen, as like you have seen in my screenshots tonight it look like it did pre SU5. No change for me.

Driver 471.41

Edited July 29, 20214 yr by Nyxx

1 minute ago, Nyxx said:

It a shame Bob is seeing diffrent on his screen, as like you have seen in my screenshot tonight it look like it did pre SU5. No change for me.

You all keep forgetting, Randazzo has complained to Asobo about this degradation of the VC. It is not just me, many on the PMDG forum, including the developer of PMDG are seeing what I am seeing. It looks good, you add the update, and no good. It's obvious to me what the problem is caused by. 

Edited July 29, 20214 yr by Bobsk8

4 minutes ago, Bobsk8 said:

You all keep forgetting, Randazzo has complained to Asobo about this degradation of the VC. It is not just me, many on the PMDG forum, including the developer of PMDG are seeing what I am seeing. It looks good, you add the update, and no good. It's obvious to me what the problem is caused by. 

We are not saying its just you Bob, but as you can see, some like myself dont see any diffrence from before you said yourself just now, it looks like it did pre patch for you. I took them tonight and tried to match yours. Also other here have said the same, theres looks like mine. So its effects some and not others it seems.

Edited July 29, 20214 yr by Nyxx

You guys haven't seen the beta and it's hard for you to understand how different the DC-6 felt before the 1.18.13 release. It's 100% on the money on his assessment. 

Edited July 29, 20214 yr by fogboundturtle

Just now, fogboundturtle said:

You guys haven't seen the beta and it's hard for you to understand how different the DC-6 felt before the 1.18.13 release. It's 100% on the money on his assessment. 

That is really odd, though. What could they have done? I know Aerosoft spoke about "last minute changes" being the thing behind the delay of the CRJ patch. 

5 minutes ago, Nyxx said:

We are not saying its just you Bob, but as you can see, some like myself dont see any diffrence from before you said yourself just now, it looks like it did pre patch for you. I took them tonight and tried to match yours. Also other here have said the same, theres looks like mine. So its effects some and not others it seems.

I wonder if it has anything to do with the resolution that users are running. I am using 2K.  Maybe in 4 K it looks OK after the update, but not in 2K With the VC exception and a few bugs that are now in the DC6, everything else in the update seems to work OK except that blasted blue arrow which I hate. 

 

Edited July 29, 20214 yr by Bobsk8

5 minutes ago, Bobsk8 said:

Maybe in 4 K it looks OK after the update, but not in 2K With the VC exception and a few bugs that are now in the DC6, everything else in the update seems to work OK except that blasted blue arrow which I hate. 

I am using 1440p with 27inch screen, I dont see any issues here. How is your textures settings by the way? Maybe something there we can try and see if it helps.

My brother is a games developer, as I'm sure I've mentioned before. One of the games had issues that got him scratching his head for a while -- until they realised one of the dev team had accidentally uploaded an old build of their bit of code at the last minute instead of the new code. Just saying, sometimes a sudden change from a good state in beta testing to a buggy version in release can be a simple error (which isn't necessarily quick to trace). Not saying that has happened here, but someone said they were seeing a better version in beta before the update was released, so it's a possibility. Asobo will be on it, either way.

1 minute ago, omarsmak30 said:

I am using 1440p with 27inch screen, I dont see any issues here. How is your textures settings by the way? Maybe something there we can try and see if it helps.

Same settings I have been using since day one. most on high or ultra. haven't changed anything in 400 hours of flying. 

I ca definitely see the blurriness in Bob’s shots. Also experience it myself in default cockpits.

1 hour ago, Swe_Richard said:

That is really odd, though. What could they have done? I know Aerosoft spoke about "last minute changes" being the thing behind the delay of the CRJ patch. 

EDITED:

The explanation is on page 1 of the thread.  At the last minute they Reverted back to the old method of culling objects without a defined level of detail set.  The new method (on the Xbox build & early beta) culls any object without a LOD set (basically a set of progressively lower res versions of an onbject) and doesn’t draw it all of its smaller than 5% of the screen size (eg the size of the popping taxiway signs in that leaked takeoff video).  The old version (which they reverted back to) culled at 0.5%

Up to this point there have been a lot of addons that didn’t make LOD sets for some or all of their objects - it is a lot of work and takes time.  Thus this change can cause a lot of geo to not render - which obviously increases FPS.  Going forward if we want to reap back some of the improved frame rates of the Xbox version and beta, devs have to start making this a common practice, esp in the freeware that we all have tons of.

As a result, Asobo was worried about the negative feedback from the beta forums and feared breaking a ton of addons (which Xbox could have had far fewer of) so they kept the old scheme for the pc release.  Thus we don’t get as big an FPS bump as they had through most of the beta.

6 minutes ago, VFXSimmer said:

The explanation is on page 1 of the thread.  At the last minute they Reverted back to the old method of culling objects without a defined level of detail set.  The new method (on the Xbox build & early beta) culls any object without a LOD set (basically a set of progressively lower res versions of an onbject) and doesn’t draw it all of its smaller than 5% of the screen size (eg the size of the popping taxiway signs in that leaked takeoff video).  The old version (which they reverted back to) culled at 0.5%
 

They we’re worried about the negative feedback from the beta forums and feared breaking a ton of addons (which Xbox could have had far fewer of) so they kept the old scheme for the pc release.  Thus we don’t get as big an FPS bump as they had through most of the beta.

Yep. 10000000% that. 

So we went through a 10 + hour update for nothing?....lol

1 hour ago, Bobsk8 said:

I wonder if it has anything to do with the resolution that users are running. I am using 2K.  Maybe in 4 K it looks OK after the update, but not in 2K With the VC exception and a few bugs that are now in the DC6, everything else in the update seems to work OK except that blasted blue arrow which I hate. 

 

I am using 2k too, texture resolution "ultra".

1 minute ago, Jeff Nielsen said:

So we went through a 10 + hour update for nothing?....lol

Not nothing - this was only one of the performance changes.  The rest stayed, Thus we still do have some fps improvement (15-20%). Just not all that could have been aparently.