Some years ago when I started flying FlightGear 2.0, I added --model-hz=480 to my startup aliases for reasons I no longer remember. I've continued to use these aliases through 2.4 and 2.6 with no real ill effect.
However, on a git build from June 13 I've noticed that using them really clobbers the framerate. Instead of getting 30 - 50 fps without this argument, I get more like 1-2 fps with it set. These frame rates are based on a default configuration, with the .fgfs directory erased immediately before starting. I'm not sure if this is a bug or just a change in the way that this flag functions, but at the very least we should note in the documentation that this command-line argument can create problems with 2.7. Even without this flag set, I'm getting extremely low frame rates of 1 - 4 fps on at least some aircraft (e.g., the Trimotor) until the aircraft breaks ground, then it suddenly jumps to 30+ fps. Landing and taking off again retains the 30+ fps frame rate. 8-core AMD machine, 8 G RAM, nVidia GTX 560, running Kubuntu Maverick. Cathy ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
