2,561
edits
m (→Visuals) |
m (→Running) |
||
Line 80: | Line 80: | ||
=== Running === | === Running === | ||
* lacking performance | * lacking performance: as of 03/2009 FG OSG is generally still frequently reported as being significantly slower on systems that were previously able to run fgfs with much better framerates | ||
* does not work well on lower end hardware | * does not work well on lower end hardware, this boils down to a lack of dynamic feature-scaling support as discussed on the forums on 03/2009 | ||
* starting FG takes a while and FG seems to have crashed, the window (splash screen) is not redrawn-unresponsive until finally started up | * <del>starting FG takes a while</del> and FG may seems to have crashed, the window (splash screen) is not redrawn-unresponsive until finally started up | ||
* warnings and error messages are only rarely informative | * warnings and error messages are only rarely informative, i.e. "unknown exception in the mainloop" | ||
* excessive logging (console output) may severely affect simulator performance, up to an unusable state | * excessive logging (console output) may severely affect simulator performance, up to an unusable state: this is due to logging being executed in the main loop [http://sourceforge.net/tracker/index.php?func=detail&aid=1910344&group_id=5 | ||
83&atid=350583] (also frequently discussed on the forums due to the recent issues with [http://wiki.flightgear.org/index.php/Showstoppers Qnan/triangleIntersect warning messages flooding the console])- this has been brought up several times already and the effect of logging on overall simulator performance was recently (03/2009) also discussed on the jsbsim mailing list where it lead to a discussion about potential alternatives for implementing logging support [http://sourceforge.net/tracker/index.php?func=detail&aid=1910344&group_id=5 | |||
83&atid=3505839] | |||
=== Realism === | === Realism === |
edits