FlightGear and OpenGL Core Profile: Difference between revisions
(https://forum.flightgear.org/viewtopic.php?f=45&t=36922&p=364937#p364898) |
m (→Background) |
||
Line 13: | Line 13: | ||
In other words, if the right people were to team up to specifically such hardware, this could also mean significant performance improvements for people on powerful gaming rigs. | In other words, if the right people were to team up to specifically such hardware, this could also mean significant performance improvements for people on powerful gaming rigs. | ||
== Approach == | |||
For starters, we can try the [[FlightGear Headless]] option to build a fgfs version without any graphics at all. | |||
The next step will be excluding problematic sources by adding <code>#ifdef</code> to the sources in question, and updating CMakeLists.txt accordingly. | |||
== See also == | == See also == |
Revision as of 13:16, 5 April 2020
This article is a stub. You can help the wiki by expanding it. |
Objective
Some FG users are very interested in seeing how FlightGear runs on low end hardware - because they may have a collection of it :)
Probably to do it initially, gles1 would have to be used - I think gles2 has no fixed function - and simgear/flightgear would have to be patched to use only OSG calls (if possible)
I know OSG can have gles{1,2} support without windowing compiled in
Background
being able to run fgfs on such, comparatively low-powered, system is actually a good thing for fgfs as a whole - it can help us understand bottlenecks that are hardly visible on typical gaming rigs, but that may still show up over time (think leaking listeners/memory) - this sort of thing can also be considered the prerequisite for people wanting to target/build/run fgfs on other embedded hardware, such as thin clients with integrated GPUs or even mobile phones (think Android)
In other words, if the right people were to team up to specifically such hardware, this could also mean significant performance improvements for people on powerful gaming rigs.
Approach
For starters, we can try the FlightGear Headless option to build a fgfs version without any graphics at all.
The next step will be excluding problematic sources by adding #ifdef
to the sources in question, and updating CMakeLists.txt accordingly.
See also
- FlightGear Headless
- Howto:Optimizing FlightGear for mobile devices
- Graphics card profiles
- Canvas and OpenGL ES
- FlightGear and old Hardware
References
References
|