Menu
▾
▴
#2560 FlightGear is becoming unplayable on Intel GPUs
Please top with the changes in the render stack.
FG is becoming ever more sluggish.
The shaders are been abused and are becoming more and more compute intensive.
Instead of streamlining and making things more efficient FG is going the opposite way.
Generic = 0 60+ FPS with close to no CPU use and almost no GPU use. Generic = 1 and nothing else changed < 14 FPS and everything feeling very sluggish, not only FG gets sluggish, but the whole system.
You are killing all intel players.
There's no significant visual improvements even. Just some lights and shadows, lights that can't even be disabled independently nor have their quality/view ranger adjustable.
If you are getting good results with Generic = 0, why do you want to use Generic = 1? Why do you think you should be able to use advanced graphics and shaders with an Intel video card?
I understand you are just trying to make noise here, but watch your tone because it gets annoying very fast.
It's also known that this might happen on older Intel machines. This is why 2020.3 LTS exists. I'd recommend you stick with 2020.3 until you decide to upgrade to a newer machine, since likely the non-shader code path will also go away in the next twelve months. We tried to communicate this: 2020.3 is the last release that will work on really old hardware: 'next' and future releases will need a more modern machine with an OpenGL 4 / DX12 class GPU.
Not too long ago we could get almost the same visual we have now, on Rembrand and ALS on much older hardware and with much better performance.
Now, apart from global shadows, FG requires a powerful GPU and even then it doesn't run with a decent FPS and without any sort of stability.
Just ask the FGUK guys on their last event, many of the pilots were experiecing dreadful FPS and frequent crashes.
Rembrandt was experimental and had a huge performance impact for almost everyone.
ALS is known to suffer from performance issues on integrated GPUs (note integrated GPUs, not older hardware), because its shaders are fairly arithmetically expensive, which is usually not a problem at all on discrete GPUs.
FG is currently undergoing a lot of huge changes. More importantly: moving to the OpenGL core profile, WS 3.0, osm2city buildings, photoscenery and Compositor shadows&lights.
2021.x won't come until later this year, so what you see now might not be what you see in the future. 2020.3 will be the LTS release for some time, so you should be using that version if it works alright for you. I don't know why you feel like you have to have the latest and greatest, people won't stop developing and moving FG forward because you own old hardware. Still, a lot of care and effort has gone into making FG as compatible as possible with less powerful hardware (and a lot of compromises have been made), but there is no magic solution to make FG run at 60 fps on a 5+ integrated GPU with max settings, sorry.
I personally also appreciate the testing done by FGUK, having people use 'next' is always nice. However, I wouldn't recommend using 'next' for big events or long flights, that must be frustrating.
We had a discussion about this last night, I wanted to summarise / repeat the key point: 'next' is work-in-progress: likely 12 or 18 months before it becomes a release. In that time the minimum system requirements, performance baseline and basically everything else are going to change (and keep changing). Of course we'll try to make it work on as wide a range of hardware as possible, but right now we don't know, and it would be incorrect to speculate or promise anything. (Eg, we cannot say 'an Intel 4000 will work but an Intel 3000 won't - we have no idea!)
If next works for someone, that is great, but if you want stability, stable FPS and comaptability with older hardware, there is an easy answer: use 2020.3. That's what we recommend for everyone who wants to fly and enjoy flying.