2 minutes ago, Bobsk8 said:

Can you explain to me why Robert from PMDG is aware of this texture problem in the DC6 cockpit is trying to get Asobo to tell him how to fix it, but you don't see it? 

It obviously does not affect all systems the same way. For you, there is a definite difference, for me there is not. I have no idea why. It could be related to specific GPU or drivers, specific MSFS settings, etc.

With the X-Box, every system is absolutely identical in terms of hardware and software, so it is reasonable to say “if it happens on my system, it happens on all”, but that is definitely not the case with a PC.

37 minutes ago, Noel said:

My update failed (due to Process Lasso) so I ended up uninstalling then doing a reinstall and haven't had a chance to run it yet.  

Just for the record: I'm using Process Lasso as well, always active before, during and after the update. No issues. Maybe it's not PL as such but a certain setting?

Kind regards, Michael

3 minutes ago, Alpine Scenery said:

They may not have changed LOD culling specifically, or their definition of LOD culling, but they did change the renderer. Above post not fully accurate, it is a response to a specific issue and is using wordplay.

They also didn't "change the broken terrain files" in that update, that's not the first time I've seen wordology used. 

As far as not the right place to voice concerns, who made you moderator?

I think as many people voice concerns, I can too, thank you for your offer, but I will wait until the next patch, not a  sadomasochist.

 

Nevermind.

Edited July 29, 20214 yr by Fiorentoni

4 minutes ago, simbol said:

Is just a piece of advice, you are more than welcome to continue. Have a good day.

S.

Sorry, I gauged my rudeness to be an equal response in the amount of rudeness.
Seriously wasn't trying to be that rude.

Edited July 29, 20214 yr by Alpine Scenery

Just now, Fiorentoni said:

Your attitude is really misplaced. He was being helpful and understanding to you. And no, one does not have to be a moderator to pronounce that.

I guess, I've never told anyone where or where not is the right place for something, so to me it sounds like something a moderator would say to be honest, but to each their own. I do apologize if it came off that rudely though.

Just now, Alpine Scenery said:

I guess, I've never told anyone where or where not is the right place for something, so to me it sounds like something a moderator would say to be honest, but to each their own. I do apologize if it came off that rudely though.

No worries, I think we are all a bit "warmed up" those days, including myself 🙂

1 hour ago, JRBarrett said:

I don’t doubt that you are having this issue. Others have reported it as well, and even PMDG have acknowledged it, but for whatever reason, on my particular installation, there is absolutely zero difference in the VC of the DC-6 SU4 vs. SU5. I have a set of 9 pre-set camera views that I use when flying, and there is no difference whatsoever.

FWIW, I have a 1080Ti GPU (11GB) running the 471.22 drivers, 4K monitor, render scaling at 70, and the two LOD sliders at 140. 

I use the same preset camera views. If Randazzo can't figure out how to fix this issue which many are complaining about, I probably have a slim chance of coming up with a solution. I just have to zoom in and out now, where 3 days ago I didn't have to do that. 

I couldn't read more after the first couple of pages, so sorry if it has already been brought up.

 

The performance drop that PMDG saw when 1.18.13 was release only affected the DC-6. I still have great performance in the other planes.

I think this is somehow related to some specific technique that PMDG uses. I am sure it will be figured out and we get back to the awesomeness we had earlier. 

Maybe PMDG is not yet ready for this new platform...

They need skills, and they probably didn't have the time to gather it...  Others are doing great, like the FBW A320, even the supposedly complex Fenix A320 described as having good performace with SU5, actually better than the default A320 as they mentioned in their Discord channel...

My experience so far is smooth as silk ! I tested the FBW and the Flinside Bell 47 G2 and they both performed great.

I'm glad I didn't jump on the DC6 without first getting performance feedback feedback ... I will wait and see how PMDG is able to deal with their first MFS experience. Maybe I'll buy it in the future, maybe not...

 

 

Edited July 29, 20214 yr by jcomm

5 minutes ago, simbol said:

Right time to put things on perspective here.

LODs culling haven't changed at all for the PC version, this is confirmed by ASOBO here: https://devsupport.flightsimulator.com/questions/1417/small-objects-disappear-on-long-distance.html

I quote:

 

As you can appreciate LODs culling algorithms remain the same for the PC version, and they have been implemented more aggressive for XBOX... therefore it is important to see the intention here, ASOBO is not making both platforms to behave the same, they understand people on PCs want to see better graphics.

There are 2 things happening here, 1 is LODs enforcement which on PC remain the same as before the SU5 update. And textures being cut our of the scene when you are not looking (what people call pop in / out), which it seems it has been implemented for both versions PC / Xbox. I asked Asobo more information on that link to understand what changed.

On that basis, I think people are seeing degradation on their VCs due to other reasons, not LOD culling. So perhaps with few tweaks on their settings things will return to what they used to see before.

@Alpine Scenery I understand what you are saying, I totally get why and how much you are frustrated.. But I learned long time ago (the hard way) this is not the space to express development frustrations, technology limitations, or even development criticism for the base platform. Simply put most people will not be able to understand your point of view because as customers they are, they can only judge by the results they can see and they can measure right now.  Better to put your energy somewhere else, chill and come back re-charged later when you can provide solutions that you are happy with. If you need someone to talk about your frustrations and that would be able to understand you, send me a PM and I will be more than happy to listen to you, maybe even able to help you with some of your issues.

All the best as usual,

Simbol
 

Thanks Simbol this is very useful info.  It sounds like this is a good stopgap for pay ware developers on the PC side in that it maintains the status quo (just talking LODs here).

It SHOULD, however, serve as a wake up call that developer’s best practices going forward should be to give much more serious consideration for implementing and tuning a level of detail set for every object.  Robert’s (and others) statements about the beta build performance proves that there is more headroom to be gained if LODs are implemented well.  To be sure, the 70% gains are a bit fictional because a probable large subset of geo simply wasn’t drawn at all, but if efficient geo is used in the difference we would AT LEAST see a improvement somewhere in the middle of this build and that of the beta.

As far as popping is concerned, that is totally up to the skill set of the developer.  We’ll designed and tested LOD steps can look close to seamless - they are used all the time in AAA titles now.  A developer really SHOULD use them no matter how well their addon works without them.  Their product is not an island and users should have as much headroom as possible to combine multiple addons together if there is a design path that will allow it.  Unless you are making an addon for yourself only, its something every responsible dev should strive for (esp for payware).

Much criticism can be leveled towards MS/Asobo for not giving people a clearer heads up about what was coming (and thus more time to prep) - that could have made this a much smoother and less controversial update.  But I think I’m the long run this will prove to be a welcome “ripping off of the bandaid” on inefficient developer practices that will ultimately help all with a better experience.

4 minutes ago, espent said:

I couldn't read more after the first couple of pages, so sorry if it has already been brought up.

 

The performance drop that PMDG saw when 1.18.13 was release only affected the DC-6. I still have great performance in the other planes.

I think this is somehow related to some specific technique that PMDG uses. I am sure it will be figured out and we get back to the awesomeness we had earlier. 

no pmdg is right. The very first beta we got, the performance was amazing. As soon as asobo decided to cater to the lazy devs complaining about redoing LOD (which they should've done in the beginning), they went and changed it back. So while performance did increase it was much more in the first beta build we got

16 minutes ago, JRBarrett said:

It obviously does not affect all systems the same way. For you, there is a definite difference, for me there is not. I have no idea why. It could be related to specific GPU or drivers, specific MSFS settings, etc.

With the X-Box, every system is absolutely identical in terms of hardware and software, so it is reasonable to say “if it happens on my system, it happens on all”, but that is definitely not the case with a PC.

Oddly enough, the 6 cockpit textures which were a little degraded just after SU5, are this afternoon back to normal ... 

1 minute ago, jcomm said:

Maybe PMDG is not yet ready for this new platform...

They need skills, and they probably didn't have the time to gather it...  Others are doing great, like the FBW A320, even the supposedly complex Fenix A320 described as having good performace with SU5, actually better than the default A320 as they mentioned in their Discord chanel...

PMDG has more ground to cover starting from basically a scratch model. 

1 minute ago, devgrp said:

no pmdg is right. The very first beta we got, the performance was amazing. As soon as asobo decided to cater to the lazy devs complaining about redoing LOD (which they should've done in the beginning), they went and changed it back. So while performance did increase it was much more in the first beta build we got

So why did it hit the DC-6 so much harder that other airplanes?

 

Just now, espent said:

So why did it hit the DC-6 so much harder that other airplanes?

 

I dont know, maybe because its a more complex plane? I still get good performance with that plane, but the performance was better in the first beta build