FlightGear and OpenGL Core Profile: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
mNo edit summary
Line 11: Line 11:


== Background ==
== Background ==
{{Main article|Howto:Optimizing FlightGear for mobile devices}}
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)
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)



Revision as of 13:20, 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

1rightarrow.png See Howto:Optimizing FlightGear for mobile devices for the main article about this subject.

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 identifying and excluding problematic sources by adding #ifdef to the sources in question, and updating CMakeLists.txt accordingly, ideally in conjunction with a feature-specific build option to disable the corresponding feature (think PUI or the HUD).

See also

References

References