4 hours ago, ChaoticBeauty said:

We are planning on a brightness slider for an upcoming Sim Update to allow visual customization of your sim.

Happy to see this, as for me the brightness is a big plus. If they can accommodate more tastes with sliders, all the better.

There were plenty doing it, but I don't think he was one. 

8 minutes ago, Mikeingreen said:

I tell this story to show that A/MS won't have an easy time eliminating CTD's and to show that some, if not most CTD's do in fact start t the User level. No matter how much we want to think that they don't.

A lot of them start at the addon layer and dev layer, but there are some in other places. I wouldn't say most of them are user related, we don't have that data. Some of them are.

 

1 minute ago, scotchegg said:

Happy to see this, as for me the brightness is a big plus. If they can accommodate more tastes with sliders, all the better.

Totally agree. Contrast and Saturation are also welcome.

I have just eliminated a lot of the shimmering around my plane in VR using this:- 

 

Just now, Alpine Scenery said:

There were plenty doing it, but I don't think he was one. 

A lot of them start at the addon layer and dev layer, but there are some in other places. I wouldn't say most of them are user related, we don't have that data. Some of them are.

 

I can only speak from my experience. I have been running MSFS since last August. In that time I have had 2 series of CTD's and both of them after changing from a Vega64 card to a 6800XT. 1st batch was cured by going to an older driver and disabling Freesync. I just explained how I cured the 2nd series. So for me, both instances were caused by the user, not MSFS. But they can be a word not allowed to chase down. I don't envy A/MS in their quest to fix them.

7 minutes ago, scotchegg said:

No, lots of us were saying we didn’t experience the bugs, or were able to get around the bugs. Unless you can show us a bunch of posts where people are saying ‘these bugs don’t exist’?

Saying the bugs were not experienced is fine - it helps other users and the developers in tracing the bugs. I am referring to those who threw abuse at others for discussing it.

57 minutes ago, MrBitstFlyer said:

If you want to use only one simulator, fine, but why the comment to others that fly more than one - it isn't a crime!

Good point and agreed. I almost went back to reinstalling fsx myself (for the nostalgia of doing the San Juan Island Run mission and flying the Digital Aviation Do27), till this news on HF2 hit. If this new fix also bombs (hope not!) , I surely will do just that and come back to msfs once it's all sorted out. 

Just now, Mikeingreen said:

I can only speak from my experience. I have been running MSFS since last August. In that time I have had 2 series of CTD's and both of them after changing from a Vega64 card to a 6800XT. 1st batch was cured by going to an older driver and disabling Freesync. I just explained how I cured the 2nd series. So for me, both instances were caused by the user, not MSFS. But they can be a word not allowed to chase down. I don't envy A/MS in their quest to fix them.

Most people have had a lot more CTD's than that, consider yourself lucky, but the older driver issue is a PITA to figure out.

Great, this finally puts an end to the endless beating of the dead horse, and many thought Asobo was just going to concentrate on xbox. LOL.

I do hope with the hotfix they will also resolve issues in the with some of the popular mods having been broken by the SU5 release - especially the FBW A32NX and the TBM930 Improvement, and the Cessnas without engine startup (starting on a runway with the engine running is currently the only option).  I didn't see any mention of those issues.

Looking forward to this hotfix.  I swore not to tweak anything as everything was fine before SU5 but it was so bad I went through the forums and tried every tweak I could find.  They all made differences but none of them better, just different.  So, I'll put everything back as it was tomorrow and hope the hotfix makes everything right again. 

Just now, saifs said:

Good point and agreed. I almost went back to reinstalling fsx myself (for the nostalgia of doing the San Juan Island Run mission and flying the Digital Aviation Do27), till this news on HF2 hit. If this new fix also bombs (hope not!) , I surely will do just that and come back to msfs once it's all sorted out. 

I currently still fly X-Plane because I have many aircraft I Love in that sim that are not available in MSFS.  However, If MSFS returns to its early glory, it will be enough for X-Plane to not get much use 🙂

1 hour ago, fppilot said:

How about a solid, issue free, fresh iteration of this product from the ground up instead of layers of updates and hotfixes?    

Sure if you want to wait 5 years.

Just now, MrBitstFlyer said:

I currently still fly X-Plane because I have many aircraft I Love in that sim that are not available in MSFS.  However, If MSFS returns to its early glory, it will be enough for X-Plane to not get much use 🙂

I agree we need more aircraft, need more medium sized props like a Dash-q400 kind of thing, but I guess for some the DC-6 is where its at. I have not yet tried the DC-6 yet.

1 hour ago, MrBitstFlyer said:

The bugs you were denying you mean?

I didn't deny any bugs. I even reported some myself.

I never denied anything that's in the opening post.

Edited August 4, 20214 yr by Tuskin38