20,741
edits
Resource Tracking for FlightGear: Difference between revisions
Jump to navigation
Jump to search
Resource Tracking for FlightGear (view source)
Revision as of 14:27, 26 August 2015
, 26 August 2015no edit summary
m (→SIGAR) |
No edit summary |
||
| Line 122: | Line 122: | ||
Despite many FlightGear users now using FlightGear on 64 bit operating systems with sufficient RAM (8+ gb), since early 2010, we've been seeing an increasing number of end-user reports due to errors along the lines of '''Open GL - out of memory error''', '''Warning: detected OpenGL error 'out of memory' at after RenderBin::draw(..)''' as can be seen in countless forum discussions, mailing list postings and bug reports in the issue tracker. | Despite many FlightGear users now using FlightGear on 64 bit operating systems with sufficient RAM (8+ gb), since early 2010, we've been seeing an increasing number of end-user reports due to errors along the lines of '''Open GL - out of memory error''', '''Warning: detected OpenGL error 'out of memory' at after RenderBin::draw(..)''' as can be seen in countless forum discussions, mailing list postings and bug reports in the issue tracker. | ||
{{FGCquote|1= This is so useful, maybe people might want to apply this patch to the already supported platform(Linux and Nvidia), it's really is an eye opener, Just spawning in KSFO with the UFO will consume over 2 GB of RAM(never mind something like the triple 7), also as you can see in the picture GPU memory usage nearly at 1GB VRAM, which was this card's maximum, so maybe we can now establish minimum hardware requirements like with other sims :) People wanted with AMD hardware to help let this thing be the default in FG, no further need for using task manager to track resources.... We have direct access! Not even FSX does this if we're done|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=254968#p254968 | title = <nowiki>Re: Looking for people with ATI/AMD GPUs building from sourc</nowiki> | author = <nowiki>hamzaalloush</nowiki> | date = Aug 25th, 2015 }}}} | |||
{{FGCquote|1= we can now also begin tracking RAM/VRAM utiliation for each initialized subsystem (think reset/re-init), which will help identify "rogue" (broken) subsystems, so that these can either be fixed/optimized or made entirely optional. In addition, it would become possible to track complexity of different locations/aircraft using different startup/run-time profiles.Obviously, this could easily be the foundation for any kind of "benchmark", but also for actual feature-scaling, to dynamically adjust certain simulator settings based on things like RAM, VRAM, CPU or Nasal/GC load, while allowing content developers (those doing scenery/aircraft) to look "behind the scenes" (e.g. to help optimize aircraft like the 777 or extra500).|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=254970#p254970 | title = <nowiki>Re: Looking for people with ATI/AMD GPUs building from sourc</nowiki> | author = <nowiki>Hooray</nowiki> | date = Aug 25th, 2015 }}}} | |||
</ | |||
{{FGCquote|1= the idea is to track resource utiliation of different sub-systems as they are initialized in FG, (not just memory usage, but also Nasal statistics for tracking where Nasal scripts are affecting performance), this is meant to be used by developers and users who, for example want to adjust view LOD to where system memory allows, etc... maybe Hooray can clarify a bit.we also are entertaining the feature-scaling idea, ever played a game where you can use "automatic" settings for your system? well if we have all the system information we can use that to apply for optimal performance on your system,|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=255006#p255006 | title = <nowiki>Re: Looking for people with ATI/AMD GPUs building from sourc</nowiki> | author = <nowiki>hamzaalloush</nowiki> | date = Aug 25th, 2015 }}}} | |||
{{FGCquote | {{FGCquote|1= In its simplest form, it will merely tell you RAM/VRAM utiliation for different startup/run-time settings, so that the impact of -for example- using different aircraft/locations (or weather systems) can be compared in varying situations. Equally, this would allow us to grow a library of startup/run-time profiles and compare the memory footprint for different hardware (think graphics cards).Such a library of startup settings could be grown and maintained as part of $FG_ROOT - at some point, this could even include scripted flights (think route-manager driven, and/or replay/fgtape based).|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=255010#p255010 | title = <nowiki>Re: Looking for people with ATI/AMD GPUs building from sourc</nowiki> | author = <nowiki>Hooray</nowiki> | date = Aug 25th, 2015 }}}} | ||
}} | |||
== Problem == | == Problem == | ||
| Line 772: | Line 742: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
== History == | |||
Typical suggestions include: | |||
<pre>The error is related to your fgfs running out of memory (but not your gpu memory)! | |||
This will happen with detailed aircraft or detailed scenery. | |||
Custom scenery like the one from papillon81 repo will cause this happen realy quick. | |||
Using a detailed plane like the 787 from omega makes it worse. | |||
(will crash fg on startup at LOWI for example / or cause scnery and some textures to be not loaded and leads to a crash a couple of minutes later) | |||
This happens without any eyecandy activated! | |||
</pre> | |||
And we've even be seeing people reporting "memory issues" despite having 12+ gb of RAM [http://forum.flightgear.org/viewtopic.php?f=4&t=21870&p=199379#p199379]. | |||
* http://forum.flightgear.org/viewtopic.php?f=24&t=22325 | |||
* http://forum.flightgear.org/viewtopic.php?f=25&t=22288 | |||
* http://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/1393845386.3876.17.camel%40emma-work/#msg32050082 | |||
* http://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/CAFEVUtDsMgXKP6cLB6BBqsdCiC-ZPLLjz7PQraNca219gCfpeQ%40mail.gmail.com/#msg31998280 | |||
* http://forum.flightgear.org/viewtopic.php?f=5&t=22119 | |||
* http://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/E495A106FF5F31448739E79D34138C193C6C2EBD%40mbs2.ad.jyu.fi/#msg31981615 | |||
* http://sourceforge.net/p/flightgear/mailman/message/31920333/ | |||
* http://sourceforge.net/p/flightgear/mailman/message/31921008/ | |||
* http://sourceforge.net/p/flightgear/mailman/message/31920150/ | |||
* http://forum.flightgear.org/viewtopic.php?f=68&t=21984&p=199673#p199670 | |||
* http://forum.flightgear.org/viewtopic.php?f=4&t=21870&p=199554#p199550 | |||
* http://forum.flightgear.org/viewtopic.php?f=25&t=21970&p=199535#p199535 | |||
* http://forum.flightgear.org/viewtopic.php?f=68&t=17114 | |||
* http://forum.flightgear.org/viewtopic.php?f=37&p=171427 | |||
* http://forum.flightgear.org/viewtopic.php?f=4&t=21870&p=199379#p199379 | |||
{{FGCquote | |||
|Fast forward 2 years later, there are now several options available to query the OS/GPU driver and obtain GPU specific information, such as amount of dedicated VRAM and overall GPU/VRAM utilization - here's what I've found for nvidia, and I am willing to provide a corresponding patch to expose these stats to the property tree and update them, i.e. once or twice per second:<br/> | |||
<br/> | |||
[http://www.geeks3d.com/20100531/programming-tips-how-to-know-the-graphics-memory-size-and-usage-in-opengl/ http://www.geeks3d.com/20100531/program ... in-opengl/] | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=216763#p216763 | |||
|title=<nowiki>Re: Open GL - out of memory error.</nowiki> | |||
|author=<nowiki>Hooray</nowiki> | |||
|date=<nowiki>Sat Aug 16</nowiki> | |||
}} | |||
}} | |||
[[Category:Core development projects]] | [[Category:Core development projects]] | ||