Dave Perry wrote:
2. The tower view doppler shift seems to be in the wrong direction.
I believe this is a known(?) problem with OpenAL for the Linux software
emulation layer. There has been some discussion about it on the openal
mailing list.
Erik
Two observations:
1. The last 2 days cvs have crashed when I move the ILS freq. to nav 1
for SFO 28R. This does not happen every time.
[EMAIL PROTECTED]:/usr/local/FlightGear ./bin/fgfs
--disable-specular-highlightInitializing OpenAL sound manager
Oops AL error in sample set_volume()! 1.15
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 is set,
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 assume some
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
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
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 the same
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 all
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]
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 list
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;
Ross Golder [EMAIL PROTECTED] said:
Also, if you got into a plane and the first thing you saw was the
following, what would you do?
http://www.golder.org/~rossg/tmp/2001_12_09_170213_shot.png
a) Request clearance to takeoff.
b) Go over the pre-flight checks again.
c) Call ahead to say
On Sunday 09 December 2001 4:23 pm, you wrote:
The CVS commit logs don't provide much info. Can they be made to send
the changes made, too, so people can see the actual detail of the change
(as a diff -u). Sometimes people will not understand the author's
description of the change, for
Ross Goldner wrote:
The CVS commit logs don't provide much info. Can they be made to send
the changes made, too, so people can see the actual detail of the change
(as a diff -u).
No need. Check out cvs diff. :)
Or maybe I'm misunderstanding what you want?
Andy
--
Andrew J. Ross
Ross Golder writes:
The CVS commit logs don't provide much info. Can they be made to send
the changes made, too, so people can see the actual detail of the change
(as a diff -u). Sometimes people will not understand the author's
description of the change, for whatever reason (e.g. may use
15 matches
Mail list logo
