20,741
edits
Hardware recommendations: Difference between revisions
Jump to navigation
Jump to search
http://flightgear.org/forums/viewtopic.php?f=24&t=20238&p=185569#p185569
No edit summary |
(http://flightgear.org/forums/viewtopic.php?f=24&t=20238&p=185569#p185569) |
||
| Line 15: | Line 15: | ||
* An optional [[joystick]]/yoke and/or pedals - Gameport or USB (HID compatible), see <tt>[[$FG_ROOT]]/Input</tt> for a list of input hardware known to work with FlightGear. | * An optional [[joystick]]/yoke and/or pedals - Gameport or USB (HID compatible), see <tt>[[$FG_ROOT]]/Input</tt> for a list of input hardware known to work with FlightGear. | ||
== NVIDIA == | |||
Stay away from nVidia GPUs with a low second digit (x20, x40). | |||
The number of CUDA cores matters much more than a few Mhz in frequency, since you can process more, in parallel. | |||
Also watch out for bus width, as that has a big impact on data throughput. | |||
In case of doubt, go for an older generation x60 (460, or 560), even a 260 would be much more of an improvement than the 620. Basically, Nvidia cards compile GLSL shaders and OpenCL kernels into CUDA kernels (sort of), so more CUDA kernels = more shader power. Higher 2nd digit means more CUDA cores. The more CUDA cores it has, the better. A GTX680 is lots and lots and lots more important than a CPU with a zillion cores. | |||
Whatever GPU (and other hardware) you get, first of all make sure that it is fully supported by your OS of choice. | |||
Thorsten mentioned in another thread that he purchased a computer with an NVIDIA GTX670 that ended up not being fully supported under Linux, so I'd suggest to be really careful here. | |||
== Notebooks == | == Notebooks == | ||
If you are interested in running FlightGear on a notebook, you may also want to check out [[Notebooks known to run FlightGear]]. | If you are interested in running FlightGear on a notebook, you may also want to check out [[Notebooks known to run FlightGear]]. | ||