Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

Minimal Startup Profile

From FlightGear wiki
Jump to: navigation, search
This article is a stub. You can help the wiki by expanding it.
Fg-3.2-minimal-settings.png
Cquote1.png it's important to come up with standard and small scale test-case for evaluating purposes, or at least pass these findings to other people.
— hamzaalloush (Oct 10th, 2015). Re: ALS vs. Rembrandt (forward vs. deferred rendering).
(powered by Instant-Cquotes)
Cquote2.png
Cquote1.png At least starting with a minimal profile should be trivial to implement: Define a property /sim/use-minimal-profile at startup, have a Nasal script check whether that property is set, and if yes, have it execute a batch of setprop() statements forcing all config options to minimal. No need to bother users with modern hardware, well-defined starting point for users with older hardware.
— Thorsten (Feb 8th, 2014). Re: fg3.0rc1 memory usage.
(powered by Instant-Cquotes)
Cquote2.png
Cquote1.png Being able to start up FG using a "safe" subset of enabled features would be great for people with older/underpowered hardware - but it would also be great for us, i.e. from a troubleshooting standpoint, but also from a benchmarking perspective, because we could dynamically scale up settings-based on what's available.
— Hooray (Feb 8th, 2014). Re: fg3.0rc1 memory usage.
(powered by Instant-Cquotes)
Cquote2.png
Cquote1.png What people have been contemplating to explore/do for a while is implementing a framework for doing dynamic "feature-scaling", i.e. where a safe subset of FlightGear would be booted (as per the minimal startup profile) and the rest (effects, shaders, ALS or Rembrandt, weather systems, visibility etc) would be dynamically determined after this subset of FG is up and running - e.g. using a PID controller that is hooked up to the corresponding PagedLOD (OSG machinery).
Cquote2.png


Note  The following FlightGear startup profile assumes that you have a $FG_ROOT environment variable set up, or that you are explicitly setting fg-root using the --fg-root command line argument, this startup profile is intended to be put into your Fgfsrc file or to be used when starting FlightGear from the command line.

The profile listed below is

  • name: minimal
  • version: 3.20
  • description: n/a
# --ignore-autosave # uncomment this for FlightGear versions >= 2.99
--disable-terrasync
--disable-splash-screen
--airport=ksfo
--offset-distance=4000
--offset-azimuth=90
--altitude=500
--heading=0
--model-hz=60
--disable-random-objects
--prop:/sim/rendering/texture-compression=off
--prop:/sim/rendering/quality-level=0
--prop:/sim/rendering/shaders/quality-level=0
--disable-ai-traffic
--prop:/sim/ai/enabled=0
--aircraft=ufo
--disable-sound
--prop:/sim/rendering/random-vegetation=0
--prop:/sim/rendering/random-buildings=0
--disable-specular-highlight
--disable-ai-models
--disable-clouds
--disable-clouds3d
# --disable-textures
--fog-fastest
--visibility=5000
--disable-distance-attenuation
--disable-real-weather-fetch
--prop:/sim/rendering/particles=0
--prop:/sim/rendering/multi-sample-buffers=1
--prop:/sim/rendering/multi-samples=2
--prop:/sim/rendering/draw-mask/clouds=false
--prop:/sim/rendering/draw-mask/aircraft=false
--prop:/sim/rendering/draw-mask/models=false
--prop:/sim/rendering/draw-mask/terrain=false

--disable-random-vegetation
--disable-random-buildings
--disable-rembrandt
--disable-horizon-effect