20,741
edits
FlightGear Newsletter August 2015: Difference between revisions
Jump to navigation
Jump to search
FlightGear Newsletter August 2015 (view source)
Revision as of 20:25, 27 August 2015
, 27 August 2015→Tracking FlightGear RAM/VRAM Utilization
| Line 74: | Line 74: | ||
[[File:Sigar-memory.png|thumb|Screen shot showing the property browser running on Netbook in a patched version of FlightGear with [[Resource Tracking for FlightGear|resource tracking support]] using the cross platform SIGAR library.]] | [[File:Sigar-memory.png|thumb|Screen shot showing the property browser running on Netbook in a patched version of FlightGear with [[Resource Tracking for FlightGear|resource tracking support]] using the cross platform SIGAR library.]] | ||
[[File:Sigar-cpu-info.png|thumb|CPU information exposed to the property tree using the SIGAR library]] | |||
{{FGCquote|1= We've been resurrecting and extending an old patch to track FlightGear resource utiliation (primarily RAM and VRAM for the time being), and are hoping to extend the patch over time - currently, this is specific to Linux and has only been tested with NVIDIA GPUs. So we're now looking for people who are able to build from source (e.g. using the Superbuild and/or the fgbuild script), who are willing to help integrate/test and develop this for platforms to which we don't have access ourselves. | {{FGCquote|1= We've been resurrecting and extending an old patch to track FlightGear resource utiliation (primarily RAM and VRAM for the time being), and are hoping to extend the patch over time - currently, this is specific to Linux and has only been tested with NVIDIA GPUs. So we're now looking for people who are able to build from source (e.g. using the Superbuild and/or the fgbuild script), who are willing to help integrate/test and develop this for platforms to which we don't have access ourselves. | ||