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

Laptops known to run FlightGear prior 2.0

From FlightGear wiki
Jump to: navigation, search

This page is intended to provide a reference for those looking to buy a notebook for running FlightGear <= 2.0. For more recent FlightGear versions, you'll want to see Notebooks known to run FlightGear.Unlike a desktop system, where you can just plug in a more or less recent NVidia card and expect things to work, laptops often don't have good OpenGL support. It is usually helpful, to specifically look out for so called "gaming" notebooks that come with hardware accelerated 3D support, as well as dedicated graphics memory.

You may also want to see Hardware Recommendations.

System for FlightGear 1.9.1

system 1d

  • same system as below, updated FlightGear 1.9.1 from [1]
  • average framerate for default startup situation (c172-3d @ KSFO,28R): 17 in 800x600x32 window, but once the plane starts moving (applied some throttle), even slightly, rises to 19-20 as before. Stays there even after applying break and throttle down; 16-17 in 1280x800x32 full screen, also raises to stable 18 after moving/stopping
  • other relevant comments:
    • It seems that the FPS measure is unstable again, and needs some "warming up"

System for FlightGear 1.9.0

system 1d

  • Type: Laptop
    • manufacturer: Apple
    • make/model: MacBook 3.1
  • specs
    • cpu: Intel Core 2 Duo 2GHz (T7300)
    • ram: 2GiB
    • opengl: 1.2 APPLE-1.5.36 on Intel GMA X3100
    • sound: on, build-in
  • required drivers, updates/upgrades (firmware/BIOS): stock configuration, plus rolling updates to OSX 10.5.6
  • supported OS (Win32, Linux, MacOS) & version: OSX 10.5.6
  • average framerate for default startup situation (c172-3d @ KSFO,28R): 19-20 in 800x600x32 window, 18-19 in 1280x800x32 full screen
  • possible optimization settings:
  • other relevant comments:
    • Same configuration as below, but with the updated OSX. It seems that driver revision 1.5.36 has some optimizations.
    • Using FlightGear 1.9.0 pre-compiled binaries from FlightGear for Mac OS X
    • Rendering options:
      • Show frame rate On
      • Show chat messages On
      • Sun/Moon horizon effect off
      • Use Point Sptites for Runway Light On
      • Enhanced runway lighting off
      • Runway light distance attenuation off
      • Specular reflections on objects off
      • Particles On
      • Precipitation off
      • Lightning off
      • Bump mapped clouds off
      • Random vegetation On
      • Enable 3d clouds off
      • Shadows/transparency: all off

system 1c

  • Type: Laptop
    • manufacturer: Apple
    • make/model: MacBook 3.1
  • specs
    • cpu: Intel Core 2 Duo 2GHz (T7300)
    • ram: 2GiB
    • opengl: 1.2 APPLE-1.5.30 on Intel GMA X3100
    • sound: on, build-in
  • required drivers, updates/upgrades (firmware/BIOS): stock configuration, plus rolling updates to OSX 10.5.5
  • supported OS (Win32, Linux, MacOS) & version: OSX 10.5.5
  • average framerate for default startup situation (c172-3d @ KSFO,28R): 16-17 in 800x600x32 window, 15-16 in 1280x800x32 full screen
  • possible optimization settings:
  • other relevant comments:
    • In windowed mode the measure seems unstable, as it will rise to 19-20 after a 2-3 minutes wait, and stay there
    • Using FlightGear 1.9.0 pre-compiled binaries from FlightGear for Mac OS X
    • Rendering options:
      • Show frame rate On
      • Show chat messages On
      • Sun/Moon horizon effect off
      • Use Point Sptites for Runway Light On
      • Enhanced runway lighting off
      • Runway light distance attenuation off
      • Specular reflections on objects off
      • Particles On
      • Precipitation off
      • Lightning off
      • Bump mapped clouds off
      • Random vegetation On
      • Enable 3d clouds off
      • Shadows/transparency: all off

system 1b

  • Type: Laptop
    • manufacturer: Apple
    • make/model: MacBook 3.1
  • specs
    • cpu: Intel Core 2 Duo 2GHz (x86 family 6 Model 15 Stepping 10) T7300
    • ram: 2GiB
    • opengl: 1.2 on Intel GMA X3100
    • sound: on, build-in
  • required drivers, updates/upgrades (firmware/BIOS): Apple Software Update for Windows 2.1.1.116 (intel driver v6.14.10.4897)
  • supported OS (Win32, Linux, MacOS) & version: Windows XP* Professional, Service Pack 3 Boot Camp
  • average framerate for default startup situation (c172-3d @ KSFO,28R): 5-6 in both windowed 800x600x32 or full screen 1280x800x32
  • possible optimization settings:
  • other relevant comments:
    • Using FlightGear 1.9.0 pre-compiled binaries from FlightGear home
    • Command-line parameters used: --timeofday=noon --disable-save-on-exit
    • Rendering options:
      • Show frame rate On
      • Show chat messages On
      • Sun/Moon horizon effect off
      • Use Point Sptites for Runway Light On
      • Enhanced runway lighting off
      • Runway light distance attenuation off
      • Specular reflections on objects off
      • Particles On
      • Precipitation off
      • Lightning off
      • Bump mapped clouds off
      • Random vegetation On
      • Enable 3d clouds off
      • Shadows/transparency: all off

Systems for FlightGear 1.0

system 1

  • Type: Laptop
    • manufacturer: Apple
    • make/model: MacBook 3.1
  • specs
    • cpu: Intel Core 2 Duo 2GHz (T7300)
    • ram: 2GiB
    • opengl: 1.2 APPLE-1.5.28 on Intel GMA X3100
    • sound: on, build-in
  • required drivers, updates/upgrades (firmware/BIOS): stock configuration, plus update to OSX 10.5.4 via dmg package from Apple
  • supported OS (Win32, Linux, MacOS) & version: OSX 10.5.4
  • average framerate for default startup situation (c172-3d @ KSFO,28R): Starts at 25, then slowly drops to 18-19, probably due to AI traffic/chatter
  • possible optimization settings:
  • other relevant comments:
    • Using FlightGear 1.0.0-r154 pre-compiled binaries from FlightGear for Mac OS X
    • Command-line parameters used: --timeofday=noon --disable-save-on-exit

system 1a

  • Type: Laptop
    • manufacturer: Apple
    • make/model: MacBook 3.1
  • specs
    • cpu: Intel Core 2 Duo 2GHz (x86 family 6 Model 15 Stepping 10) T7300
    • ram: 2GiB
    • opengl: 1.2 on Intel GMA X3100
    • sound: on, build-in
  • required drivers, updates/upgrades (firmware/BIOS): Apple Software Update for Windows 2.1 (intel driver v6.14.10.4897)
  • supported OS (Win32, Linux, MacOS) & version: Windows XP* Professional, Service Pack 2 (5.1.2600) Boot Camp
  • average framerate for default startup situation (c172-3d @ KSFO,28R): Starts at 12-13, then drops to 9-10, probably due to AI traffic/chatter
  • possible optimization settings:
  • other relevant comments:
    • Using FlightGear 1.0.0 pre-compiled binaries from FlightGear home
    • Command-line parameters used: --timeofday=noon --disable-save-on-exit


system 2

  • Type: Laptop
    • manufacturer: HP
    • make/model: Pavillion dv9000 (dv9660eg)
  • specs
    • cpu: AMD Turion(tm) 64 X2 Mobile Technology TL-58
    • ram: 4GiB
    • opengl: 2.1.2 NVIDIA 177.13
    • sound: on, build-in
  • required drivers, updates/upgrades (firmware/BIOS): nvidia driver
  • supported OS (Win32, Linux, MacOS) & version: Ubuntu 8.04 (2.6.26.2-sigsiu #2 SMP x86_64 GNU/Linux)
  • average framerate for default startup situation (c172-3d @ KSFO,28R): Between 20 and 35 (resolution 1440x900)
  • possible optimization settings:
  • other relevant comments: