diff --git a/docs-mini/FlightGear-FAQ.html b/docs-mini/FlightGear-FAQ.html index 6ec3c5588..b6053487c 100644 --- a/docs-mini/FlightGear-FAQ.html +++ b/docs-mini/FlightGear-FAQ.html @@ -114,9 +114,6 @@
-First of all, one of the most common mistakes on SGI hardware is to - forget to specify --fog-fastest. On most SGI machines the EXP2 shading - model isn't hardware supported resulting in frame rates below 1 frame - per second (fps).
-FlightGear makes extensive use of the OpenGL z-buffer feature,which - on most older SGI hardware is only supported in software. This means - that the CPU has to do all the z-buffer calculations in addition to the - other tasks FlightGear involves (flight dynamics, scenery tracking, - pushing commands into the graphics queue, etc). The following features - are software rendered on low-end SGI machines (like Indy and - Indigo):
-This means that running FlightGear with the following options may not - even get the desired result:
-
- ./runfgfs --fog-disable --shading-flat --disable-skyblend \
-
- --disable-textures --disable-clouds --disable-sound \
-
- --disable-panel --enable-hud --disable-anti-alias-hud
-
I could even imagine that adding --enable-wireframe doesn't work on - these machines (I would be happy to be proven wrong though).
-On a machine like O2 the following options give an acceptable - result:
-./runfgfs --fog-fastest --disable-sound
- Since I don't have access to other SGI hardware I can't tell which - options would be appropriate for your situation.
-