On Tuesday, June 11, 2002, at 02:34 am, Jim Wilson wrote:
Not a problem...give me a day or two to get things together. Probably
there
won't be as much changed as there will be added, but some of the
settings
need to be exposed in the property tree.
yeah, this is basically what I was
Marcio Shimoda writes:
Does anybody is working on the weather effects?
If you mean the visual effects, no, not to my knowledge.
Thunderstorms are a very special case -- visuals aside, they'll
require fairly sophisticated weather modelling and good turbulence
support from the FDMs even just to
I've got a problem with an undefined reference. I've set up a function
template in one of my classes. The declaration is:
template class T
T IntegrateAB4(double delta_t, T vLast, T* vLastArray);
The definition is:
template class T
T FGState::IntegrateAB4(double delta_t, T vLast, T
James Turner [EMAIL PROTECTED] said:
yeah, this is basically what I was expecting, The current auto-pilot
code is a bit hard-coded to use the radio stack for NAV modes, for
example, we need a general course deviation or heading deviation (once
we decide which) input, and then a NAV/GPS
On Tuesday, June 11, 2002, at 02:27 pm, Jim Wilson wrote:
If I'm not mistaken (and I easily could be) the FMC would usually just
feed
the autopilot heading and speed data when using non-radio-stack NAV
modes.
The FMC monitors the course and the AP only needs to follow the
commands
fgfs --help
exits with an error message about 'options.xml' missing
Shouldn't this be in fgfsbase ??
Cheers
Norman
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Well, this is where it gets interesting :-) We really need to define the
auto-throttle property nodes, so that the FMC/MCDU can set (some of )
those. Or, on the 757/767, this is done via a physical panel, apparently
(if I understand Thomas' comments). (the 777 uses a THRUST LIM page).
And
Norman Vine [EMAIL PROTECTED] said:
fgfs --help
exits with an error message about 'options.xml' missing
Shouldn't this be in fgfsbase ??
Probably. One other thing though...what happens if your base package isn't in
the normal place and you fail to specify it's locaiton? Last I knew
On Tue, 11 Jun 2002 16:13:50 - Jim Wilson [EMAIL PROTECTED] wrote:
Norman Vine [EMAIL PROTECTED] said:
fgfs --help
exits with an error message about 'options.xml' missing
Shouldn't this be in fgfsbase ??
Probably. One other thing though...what happens if your base package
Yes ...
Norman Vine writes:
fgfs --help
exits with an error message about 'options.xml' missing
Shouldn't this be in fgfsbase ??
Cheers
Norman
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Jim Wilson wrote:
Probably. One other thing though...what happens if your base package isn't in
the normal place and you fail to specify it's locaiton? Last I knew fgfs
bailed out and would not process the --help directive. Now of course it
couldn't anyway, but a minimal help message
On Tuesday 11 June 2002 12:10 pm, Norman Vine wrote:
fgfs --help
exits with an error message about 'options.xml' missing
Shouldn't this be in fgfsbase ??
Cheers
Norman
Curt sent me the file to commit. Something is up on the server end.
Unfortunately, I'm on jury duty today and have
Was this a mistake?
Best,
Jim
[EMAIL PROTECTED] said:
Date: Tue Jun 11 13:06:29 EDT 2002
Author: cvsroot
Update of /home/cvsroot/FlightGear/FlightGear/Aircraft
In directory bitless:/tmp/cvslck/cvs-serv8782/Aircraft
Modified Files:
X15-set.xml
Log Message:
Command line help
Norman Vine wrote:
fgfs --help
exits with an error message about 'options.xml' missing
Shouldn't this be in fgfsbase ??
Apparently, it is in CVS. But the permissions on the file are
incorrect:
turban:/andy/src/fgfsbase$ cvs up options.xml
cvs server: cannot open
Jim Wilson has written a mini-howto for configuring views in
flightgear (i.e. cockpit view, tower view, chase view, etc.) These
are all dynamically configurable via an xml config file.
I have added this HOWTO to the flightgear docs page or you can find it
directly using the following URL:
On Tuesday 11 June 2002 1:32 pm, Andy Ross wrote:
Norman Vine wrote:
fgfs --help
exits with an error message about 'options.xml' missing
Shouldn't this be in fgfsbase ??
Apparently, it is in CVS. But the permissions on the file are
incorrect:
turban:/andy/src/fgfsbase$ cvs up
If this is a duplicate, my apologies; having a few minor email problems
today and not sure what was sent.
Well, this is where it gets interesting :-) We really need to define the
auto-throttle property nodes, so that the FMC/MCDU can set (some of )
those. Or, on the 757/767, this is done
On Tue, 2002-06-11 at 08:15, James Turner wrote:
On Tuesday, June 11, 2002, at 02:27 pm, Jim Wilson wrote:
If I'm not mistaken (and I easily could be) the FMC would usually just
feed
the autopilot heading and speed data when using non-radio-stack NAV
modes.
The FMC monitors the
Hi,
with regards the glitch with the new socket code.
When trying to connect with native_ctrls perror() returns
"transport end not connected" after the
sock.recv(..) call in the read routine.
Is something missing? Something OpenGC and/or FG
have to initialize?
Regards
John W.
19 matches
Mail list logo
