Heiko Schulz wrote: > I think that there are maybe some more causes than > only the setlistener. Agreed. I should have included the following from fgrun:
/usr/local/FlightGear-plib/data/bin/fgfs --fg-root=/usr/local/FlightGear-0.9/data --fg-scenery=/usr/local/FlightGear-0.9/data/Scenery:/usr/local/FlightGear-0.9/Scenery-0.9.10 --airport-id=KOTM --aircraft=pa28-161 --control=joystick --disable-random-objects --disable-ai-models [EMAIL PROTECTED] --geometry=1680x1050 --visibility-miles=15 --bpp=24 --fov=65 --nmea=socket,out,5,localhost,5500,udp --prop:/sim/frame-rate-throttle-hz=60 --nav1=111.6 --nav2=109.5 --adf=344 --dme=nav1 I did observe a stutter with the pa24-250 until I set --prop:/sim/frame-rate-throttle-hz=60 I just did the same rw 31 approach into KOTM with the pa28-161 (kap140 autopilot) and it also was smooth as silk with frame rate varying from 65 to 68, usually 67 fps. The nasal for this model is very similar to the pa24-250. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
