I got a boost with threaded optimization as well! Ryzen 1800X, GTX 1080.

Hi Mario,

We have _not_ been able to reproduce this in 11.30r3, despite spending significant time trying to do so. If you want us to continue to investigate this, we need a _new_ bug report that compares 11.26 to 11.30r3, with the _exact_ same view and the _exact_ same settings. A good way to get the view to be the same is to set up a 3 or 10 mile final and then pause the sim. You can also pause the sim in forward-no-HUD and save a situation in 11.26, then use it in 11.30.

If you’re not sure how to do this, please contact Jennifer – she can help you with the details on a better bug report, but at this point we just don’t see a rendering difference between 11.30 and 11.26.

Hi Ben,

I have submitted a bug report but please read the following as it may help. I installed a new copy of xplane11.30rc3 vanilla with nothing else and the problem is still the same and really shows in VR. A simple test is to go to CYOW and go a few hundred feet in the air facing north and look for the city skyline. In 11.26 upto 11.30b6 it is visible in the distance, but as of 11.30b7 the skyline is not there until you fly closer. It is even more obvious in VR. Reading another post somewhere it was mentioned that if you increase the world objects setting to maximum it will give same result as earlier version but this kills the fps. Did some tests and this is true. But world objects setting needs to stay at high as setting it to maximum causes the sim to stutter and lowers fps too much (especially in VR). Regardless there is a difference in view distance of the city skyline and many other scenery objects like houses and cars. Not sure how not many others have noticed this. Thanks for all the hard work!

Mind blown.

Good idea Dellanie!!! I have an idea close to this which i will bring up in the next blog. It has to do with functions.

Saw a lot of issues on bug reports and information not getting through to laminar. Perhaps it would be more productive if the bug reporter was actually built into X-Plane. I drew a mockup of it and posted on imgur.

https://imgur.com/a/TKo4G6A

In theory, it would more likely catch bugs “as they occur” and it would be easier to upload information (since version number, OS and log files would be automatically posted,) and it would be easier for the end user to attach recordings/images to bug reports.

On the rolling topic of UI improvements, could we also see an option for the X-Plane installer to output the overriding changes to keep/discard as a list… rather than as a sequential checkbox?

Cheers

Thank you for your background info, Sidney. Still we users see people on the forums who have really strange things going on and after a manual delete of the shader cache are happy.
I had this once myself, Win10 and Nvidia.