i think you REALLY need to look at what say Unigine can do it HAS been used for other sims and in fact does a lot of what you want already out of the box and let LR focus on systems and not engine performance

https://developer.unigine.com/en/devlog/20181227-unigine-2.7.3#67381f70359bde91c53875a8fa510832

some thing to look at they are even working on full earth model out of the box in the next update and already has tools that people have been asking for for years like road and mesh editing

really all LR would need to plug there flight physics engine on top of Unigine and BAM X-Plane 12 with a modern engine letting LR work on things like the G1000 and maybe an LR 540/530 G5000 etc and improving flight physics
HELL Unigine supports DX10,11,12, OpenGL AND Vulkan out of box along with Win, Linux and osX so its not like you would lose any thing

This is in the category of “perf issues I’m not going to look at right now” I think. While 2.5 ms lost is a big deal, the sim’s perf above 60 fps is pretty random and semi-reliable right now, and the best thing we can do for that is to move to Vulkan, where we can analyze perf to a level of detail where this is something we can act on.

Yeah, I have to confirm Brett’s assertion. I just made a quick comparison between 11.25 and 11.30r1 on Linux with a GTX 1080. I made all the settings and scenery the same. Saw ~100 fps on 11.25 and ~80 fps on 11.31r1. So I imagine there are situations where the frame rate is even lower and it would be a genuine cause for concern.

No need to lecture about Outerra. 😉 That was a complete, tongue in cheek bit of dry humor since, just like whining for other render engines, the Outerra conversation is a non-starter. Outerra is great for the notion of a completely empty natural world, but it can’t compare to the complexity and genius that is the X-Plane plausible world.

After update to 11.31 release I am experiencing a serious crash due to syntax error in GLSL pixel shader code.
This occurs only when HDR is active.

Bug report has just been filed to Bug report tracker with subject “Crash due to syntax error in GLSL pixel shader code”

If you saw a _large_ reduction in frame rate, please file a bug….we have diagnostic tools to see what happened. We don’t nkow of anything that’d cause a 1080 or 2080 to slow down.

Between my own sim, and sims at work, we’ve got many different machines running Windows 10, motherboards in the z170 through z390, as well as X299 chipset families, using Intel I7-6600K, 7700K, 8700K, 9900K, and 7920X processors, using nVidia GTX 1080’s, 1080 Ti’s, and RTX 2080 Ti GPUs. All of these systems saw rather large reductions in frame rates with the update to 11.30, dropping some of them to 12fps.

While I fully understand keeping focus on Vulkan deployment, I will send my gratitude for your continuing to look for any low hanging fps shaped fruit in the OGL environment.

Many thanks,

Brett

I think the sun lighting have a problem with the earth when she goes down.

If it’s possible to fix that, it will be good 🙂

Best regards

Try this

Remove the file “Saitek Pro Flight X-55 Rhino Throttle – Windows.joy” from Resources/joystick configs/ and try configuring Again

I sent to LR what I think is a fixed config. But for now that is the best fix available.