Hardware recommendations: Difference between revisions

Jump to navigation Jump to search
m
m (cleanup)
Line 19: Line 19:
*# Hardware prices will be expected to drop once the situation with the pandemic eases. Hardware is getting steadily faster. Hardware with the same performance is getting cheaper. You should never buy hardware for a ''future'' version of FlightGear or any other program. It's always better to wait until the application releases (and until the hardware purchase is justifiable as you have time to start using it properly).
*# Hardware prices will be expected to drop once the situation with the pandemic eases. Hardware is getting steadily faster. Hardware with the same performance is getting cheaper. You should never buy hardware for a ''future'' version of FlightGear or any other program. It's always better to wait until the application releases (and until the hardware purchase is justifiable as you have time to start using it properly).
*# There is a 1st rollout of buildings, roads, and objects for the world based on OSM data. Please don't buy hardware based on this rollout. The performance in future rollouts will improve drastically as objects are changed to a newer format.  See [[OSM2City 1st Worldbuild]] for details.
*# There is a 1st rollout of buildings, roads, and objects for the world based on OSM data. Please don't buy hardware based on this rollout. The performance in future rollouts will improve drastically as objects are changed to a newer format.  See [[OSM2City 1st Worldbuild]] for details.
* For current hardware performance (with the OSM2City world-build off): FlightGear 2020.3 is faster than the 2018.3 LTS. The 2018.3 hardware profile below is valid - but only one profile and hardware build is available in that section as of writing this.
* For current hardware requirements (with scenery layers containing the new OSM2City world-build disabled): FlightGear 2020.3 LTS is faster than the 2018.3 LTS. The 2018.3 LTS hardware profile below is valid - but only one profile and hardware build is available in the 2018.3 LTS section as of writing this.
* There is a new graphics profile system being developed for future FlightGear. This will at least have some named settings presets which can be associated with some hardware and performance categories.
* There is a new graphics profile system being developed for future FlightGear. This will at least have some named settings presets which can be associated with some hardware and performance categories.


Line 25: Line 25:
Only one target performance and settings profile has been written below. Other settings profiles are to-do. FlightGear can scale the quality to run on a huge range of hardware at different quality settings.
Only one target performance and settings profile has been written below. Other settings profiles are to-do. FlightGear can scale the quality to run on a huge range of hardware at different quality settings.


Before selecting GPU and CPU have a look at the benchmark lists in the [[Hardware recommendations#FlightGear settings tips:|tips section]] below for an approximate idea of performance. If you are choosing a laptop see the manufacturers website for that model to find out your GPU and CPU, and check the list. Remember the slowest component will be the limiting component. For example: if you want high graphics but your GPU is slow, having a very fast CPU will not help. If you run out of RAM then you cannot have really high visibility ranges or object densities even if your GPU and CPU is fast. The tips in the sections below about avoiding Intel integrated GPUs, mobile laptop GPUs, and low range NVIDIA GPUs (xx10, xx20, xx30, xx40) apply.
Before selecting a GPU and CPU have a look at the benchmark lists in the [[Hardware recommendations#Mostly high and Max settings with 2015.2B mid range GPU|profile]] below for an approximate idea of performance. If you are choosing a laptop see the manufacturers website for that model to find out your GPU and CPU, and check the list. Remember the slowest component will be the limiting component. For example: if you want high graphics but your GPU is slow, having a very fast CPU will not help. Higher resolutions needs faster GPUs, you can't run FlightGear at 4k woith a laptop if your manufacturer has not included a fast 3d card even if they have included a fast GPU - you need to run FlightGear at lower resolution or find a laptop with faster GPU. If you run out of RAM then you cannot have really high visibility ranges or object densities even if your GPU and CPU is fast. The tips in the sections below about avoiding Intel integrated GPUs, mobile laptop GPUs, and low range NVIDIA GPUs (xx10, xx20, xx30, xx40) apply.


''Note on hardware requirements''
''Note on hardware requirements''
1,746

edits

Navigation menu