I just installed flightgear on a AMD64 system running Debian/Jessie. I ran it but before it did anything it took 13G of VM and 7G of resident (on a system with 8G of RAM) and the system swapped to death. Is there any way of setting it to use less RAM BEFORE it even gives it's main menu? Are there good options to the fgfs program to make it use less memory? -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
Not sure if that is the problem, but I am guessing you would have it configured to load all the maps and terrain for all regions into ram. You can tell it to only read map and terrain data as needed from disk. It may slow down the simulation though specially when flying across multiple regions. If you are only flying in one region (eg Australia region) it's fine. Its a while since I have used it though. Daniel. On 02/05/15 22:07, Russell Coker wrote:
I just installed flightgear on a AMD64 system running Debian/Jessie. I ran it but before it did anything it took 13G of VM and 7G of resident (on a system with 8G of RAM) and the system swapped to death.
Is there any way of setting it to use less RAM BEFORE it even gives it's main menu? Are there good options to the fgfs program to make it use less memory?
Hello Russell, On Sat, 2015-05-02 at 22:07 +1000, Russell Coker wrote:
I just installed flightgear on a AMD64 system running Debian/Jessie. I ran it but before it did anything it took 13G of VM and 7G of resident (on a system with 8G of RAM) and the system swapped to death.
Is there any way of setting it to use less RAM BEFORE it even gives it's main menu? Are there good options to the fgfs program to make it use less memory?
Used Google to find http://www.flightgear.org/ and subsequent pages. Did not find any direct mention of memory use and limiting, but there is a listing of command line options and other commentary that might be helpful. It might be possible to start in a relatively limited form, reduced resolution, minimal dash, and other options that might let you start to explore what is the memory hog. They also mention that the source code is to be considered authoritative. Regards, Mark Trickett
participants (3)
-
Daniel Jitnah -
Mark Trickett -
Russell Coker