Re: [Flightgear-devel] Observations on latest cvs flightgear

2002-02-13 Thread D Luff
David Megginson writes: > Andy Ross writes: > > > The startup stuff, though, should be really simple. What do I do, > > check the cranking flag and add some delay before it turns over? > > It would be better to have a cutoff RPM where the engine stops > running. As long as the cranking flag

Re: [Flightgear-devel] Observations on latest cvs flightgear

2002-02-08 Thread D Luff
Curtis L. Olson writes: > > > I'm not seeing this at all on my end. The controls all start out > > > centered for me. Are you running with keyboard input, or joystick for > > > the yoke? > > > > This is with keyboard. > > You are the only one who I've heard report such a thing. > OK, I'll

Re: [Flightgear-devel] Observations on latest cvs flightgear

2002-02-07 Thread Curtis L. Olson
D Luff writes: > Curtis L. Olson writes: > > > If you configure --without-logging, then all this SG_LOG() output will > > be disabled. > > In that case may I suggest that the Windows binary be configured > without logging? If you are building it, you can configure it this way if you like. As

Re: [Flightgear-devel] Observations on latest cvs flightgear

2002-02-07 Thread D Luff
Curtis L. Olson writes: > If you configure --without-logging, then all this SG_LOG() output will > be disabled. In that case may I suggest that the Windows binary be configured without logging? > > It might be a problem for view points/aircraft that sit lower to the > ground. What kind of vi

Re: [Flightgear-devel] Observations on latest cvs flightgear

2002-02-07 Thread John Wojnaroski
> > > > The output from SG_INFO to the console (Event states, mouse in > > > view/pointer mode, lighting updates and tile updates) can cause > > > nasty pauses on Windows 98 even with the console window > > > minimised, far worse than on NT on the same hardware. May I > > > suggest that we t

Re: [Flightgear-devel] Observations on latest cvs flightgear

2002-02-07 Thread David Megginson
Andy Ross writes: > The startup stuff, though, should be really simple. What do I do, > check the cranking flag and add some delay before it turns over? It would be better to have a cutoff RPM where the engine stops running. As long as the cranking flag is set, keep incrementing RPM slightly

Re: [Flightgear-devel] Observations on latest cvs flightgear

2002-02-07 Thread Andy Ross
Curtis L. Olson wrote: > D Luff wrote: > > YASim initialised at about 40 knots charging down the runway, > > with the engines running and the magnetos off. Due to the > > aformentioned full left aileron I didn't get very far. > > Yes, YASim engine start procedures need to be on the todo lis

Re: [Flightgear-devel] Observations on latest cvs flightgear

2002-02-07 Thread Curtis L. Olson
Cameron Moore writes: > I've got a Feature Request item[1] for this on SF. I seriously doubt > I'll have free time to hack on this before the feature freeze, so if > it's going to get into 0.7.9, someone else is going to have to do it. > Thanks > > [1] http://sf.net/tracker/index.php?func=detail

Re: [Flightgear-devel] Observations on latest cvs flightgear

2002-02-07 Thread Curtis L. Olson
D Luff writes: > The output from SG_INFO to the console (Event states, mouse in > view/pointer mode, lighting updates and tile updates) can cause > nasty pauses on Windows 98 even with the console window > minimised, far worse than on NT on the same hardware. May I > suggest that we turn off

Re: [Flightgear-devel] Observations on latest cvs flightgear

2002-02-07 Thread Bernie Bright
David Megginson wrote: > > Cameron Moore writes: > > > > The output from SG_INFO to the console (Event states, mouse in > > > view/pointer mode, lighting updates and tile updates) can cause > > > nasty pauses on Windows 98 even with the console window > > > minimised, far worse than on NT on

RE: [Flightgear-devel] Observations on latest cvs flightgear

2002-02-07 Thread BERNDT, JON S. (JON) (JSC-EX) (LM)
> One of the problems is that JSBSim does its own output outside of the > SG_LOG infrastructure. We'll need to modify JSBSim to allow custom > logging interfaces, and that might be a bit of a tedious chore. No really. If we want JSBSim to have no output log, simply set JSBSIM_DEBUG=0 I don't th

Re: [Flightgear-devel] Observations on latest cvs flightgear

2002-02-07 Thread David Megginson
Cameron Moore writes: > > The output from SG_INFO to the console (Event states, mouse in > > view/pointer mode, lighting updates and tile updates) can cause > > nasty pauses on Windows 98 even with the console window > > minimised, far worse than on NT on the same hardware. May I > > su

Re: [Flightgear-devel] Observations on latest cvs flightgear

2002-02-07 Thread Cameron Moore
* [EMAIL PROTECTED] (D Luff) [2002.02.07 06:12]: > The output from SG_INFO to the console (Event states, mouse in > view/pointer mode, lighting updates and tile updates) can cause > nasty pauses on Windows 98 even with the console window > minimised, far worse than on NT on the same hardware.

[Flightgear-devel] Observations on latest cvs flightgear

2002-02-07 Thread D Luff
Here's my observations from testing the latest cvs flightgear/simgear/base: The fixed turn co-ordinater in JSBSim is great, unfortunately it doesn't work (freezes) after a reset. Its quite literally 'fixed' then ;-) The output from SG_INFO to the console (Event states, mouse in view/pointer