1,746
edits
Hardware recommendations: Difference between revisions
Jump to navigation
Jump to search
m
cleanup
m (→Recommended hardware for FlightGear 2018.3 LTS: cleanup) |
m (cleanup) |
||
| Line 77: | Line 77: | ||
* CPU: Aircraft that are heavier on CPU than than the C172P can drag down performance more if you are CPU limited. | * CPU: Aircraft that are heavier on CPU than than the C172P can drag down performance more if you are CPU limited. | ||
* RAM & GPU: Trees at ultra consume a lot of RAM. They need GPU power too. | * RAM & GPU: Trees at ultra consume a lot of RAM. They need GPU power too. | ||
* RAM: If you run into RAM issues try turning down [[Level Of Detail (LOD) Ranges#Scenery ranges|LoD:Rough]] (in <code>View menu > Adjust LOD range | * RAM: If you run into RAM issues try turning down : [[Level Of Detail (LOD) Ranges#Scenery ranges|LoD:Rough]] (in <code>View menu > Adjust LOD range</code>), tree density, and LoD: bare. | ||
* CPU & RAM: Using OSM2City scenery can also use up RAM and CPU. OSM2City version 2017.2 is compatible with FlightGear 2018.3 LTS. Try turning off roads and pylons if you are CPU limited. Try turning down LoD:rough if you are RAM/CPU limited. Random scenery objects can be heavy on CPU, try turning them off. | * CPU & RAM: Using OSM2City scenery can also use up RAM and CPU. OSM2City version 2017.2 is compatible with FlightGear 2018.3 LTS. Try turning off roads and pylons if you are CPU limited. Try turning down LoD:rough if you are RAM/CPU limited. Random scenery objects can be heavy on CPU, try turning them off. | ||
* GPU: ALS shaders sliders can be maxed in a lot dedicated GPUs, even quite old ones provided they are dedicated GPUs (and not integrated/mobile GPUs). It's mostly the scenery layer settings including tree density and LoD ranges that can be intensive. | * GPU: ALS shaders sliders can be maxed in a lot dedicated GPUs, even quite old ones provided they are dedicated GPUs (and not integrated/mobile GPUs). It's mostly the scenery layer settings including tree density and LoD ranges that can be intensive. | ||
| Line 105: | Line 105: | ||
== NVIDIA == | == NVIDIA == | ||
''April 2021 note:'' Check a GPU benchmark list like this for a '''rough''' idea of performance: [https://benchmarks.ul.com/compare/best-gpus Direct link] ([http://web.archive.org/web/20210412095421/https://benchmarks.ul.com/compare/best-gpus April 2021 archive]). If you are selecting a laptop find out what your GPU is - ask or check the manufacturers website page for the model of the laptop. Laptop GPUs: Laptops with NVIDIA 9xx series GPUs often have the mobile "M" variant. | ''April 2021 note:'' Check a GPU benchmark list like this for a '''rough''' idea of performance: [https://benchmarks.ul.com/compare/best-gpus Direct link] ([http://web.archive.org/web/20210412095421/https://benchmarks.ul.com/compare/best-gpus April 2021 archive]). If you are selecting a laptop find out what your GPU is - ask or check the manufacturers website page for the model of the laptop. Laptop GPUs: Laptops with NVIDIA 9xx and earlier series GPUs often have the mobile "M" variant. These are a lot slower than the normal version e.g. a GTX 960M is slower than a GTX 960. NVIDIA 10xx series and later use desktop equivalents in all laptops, or close to it. This is due to recent GPU technology using less power making it easier on laptop batteries. There are also Q-MAX variants that are only slightly slower than normal versions but use less battery - e.g. a GTX 1060 Q-MAX is only slightly slower than a GTX 1060 - see benchmarks. (April 2021) | ||
Stay away from nVidia GPUs with a low second digit (x20, x40). Higher 2nd digit means more CUDA cores. | Stay away from nVidia GPUs with a low second digit (x20, x40). Higher 2nd digit means more CUDA cores. | ||