Troubleshooting crashes: Difference between revisions

Troubleshooting crashes (view source)

310 bytes added , 13 September 2013

m

20,741

edits

@@ Line 40: / Line 40: @@
 === Performance targets ===
-Generally, try to optimize FlightGear for at least 30+ fps before changing to a regular aircraft and/or location!
+Generally, try to optimize FlightGear for at least 30+ fps before changing to a regular aircraft and/or location! Realistically, the ufo is not very representative - so that it would be better to aim for something in between 50-100 fps prior to switching to a more complex aircraft like the c172p for example. For instance, aircraft like the A380, IAR80, Concorde or 777 are known to require fairly powerful hardware.
-If you are not getting frame rates '''much''' higher than 100 fps with the minimal startup profile (without using frame throttling, i.e. locking the refresh rate at a certain frequency, obviously), then using complex aircraft (777,787) or scenery (KSFO, KLSV etc) will be next to impossible with your system.
+Thus, if you are not getting frame rates '''much''' higher than 100 fps with the minimal startup profile (without using frame throttling, i.e. locking the refresh rate at a certain frequency, obviously), then using complex aircraft (777,787) or scenery (KSFO, KLSV etc) will be next to impossible with your system.
 === Minimal Startup Profile ===