John Wojnaroski writes:
Does fgGetdouble(/controls/flaps) return the value for the position of the
flaps or the value the flaps are commanded to? Same for gear and slats. Is
the code such that all setters work as directed and surfaces move to the
commanded postion so that actual=command?
John Wojnaroski wrote:
Also, does the gear still exhibit extention/retraction delays. Is
there a fgGetDouble(/controls/gear[n]-position') or something like
that which returns a value from 0 to 1?
Aerodynamically, yes. The gear is interpolated from all to none
over the retract-time
Aerodynamically, yes. The gear is interpolated from all to none
over the retract-time specified. But you can't see that in the
properties; all you get is the control position. David is right, we
need to decide on a set of output properties for the actual surface
positions.
Yes. kept
John Wojnaroski wrote:
both 747 and f15 seem to be underpowered. or possibly too much drag?
Can't hold a vertical climb in the f15 and can only get to mid
altitudes in
the teens with 747
This is the second time this has been reported, but I can't reproduce
it. Your note later on,
John Wojnaroski wrote:
New question. controls for teh gear and flaps? will the existinig
bindings for the keyboard work?
Are the gear and flap values now properties?
The gear is controlled by /controls/gear-down, a boolean. The flaps
are in /controls/flaps, a floating point number from
Andy wrote
The gear is controlled by /controls/gear-down, a boolean. The flaps
are in /controls/flaps, a floating point number from 0 (no deflection)
to 1. Also, the 747 has slats, which it looks for in /controls/slats,
with the same convention. There's no default keyboard mapping for
Andy wrote
Just need to get the turbine data across the
link (Assuming that YASIM is generating N1, N2, EGT, EPR, oil
pressure, fuel flow, etc)
Sure thing:
/engines/engine[n]/n1
/engines/engine[n]/n2
/engines/engine[n]/epr
/engines/engine[n]/egt-degf
Engine data is a little screwy. running jbsim for the c310 no data comes
across and for yasim-747 the zeroeth values are missing.
Not sure i've got this properties thing all figured out yet.
In opengc.cxx
data-n1_turbine[0] = fgGetDouble(/engines/engine[0]/n1);
Engine data is a little screwy. running jbsim for the c310 no data comes
across and for yasim-747 the zeroeth values are missing.
Not sure i've got this properties thing all figured out yet.
In opengc.cxx
data-n1_turbine[0] = fgGetDouble(/engines/engine[0]/n1);
data-n1_turbine[1]
Hi,
Believe there was a discussion while back regards
YASIM options, but can't find it.
Could someone tell me command line options for
running YASIM with the various models?
Thanks
John W.
John Wojnaroski writes:
Hi,
Believe there was a discussion while back regards YASIM options, but can't find it.
Could someone tell me command line options for running YASIM with the various models?
With the cvs version you should just have to look in
$(FG_ROOT)/Aircraft and find all the
John Wojnaroski wrote:
Believe there was a discussion while back regards YASIM options, but
can't find it.
Could someone tell me command line options for running YASIM with the
various models?
If you're just running it, then the aircraft files already take care
of everything for you.
John Wojnaroski wrote:
Actually using a set of glass displays I've developed that match the
747 flight deck. Runs on a seperate machine with a LAN interface and
has a full set of EICAS (Engine Instruments Crew Alerting System) and
Navigtion displays.
Oh yeah. Duh. I knew that. :) I
John Wojnaroski writes:
Could someone tell me command line options for running YASIM with
the various models?
fgfs --aircraft=c172-yasim
fgfs --aircraft=c310-yasim
fgfs --aircraft=dc3-yasim
etc.
All the best,
David
--
David Megginson
[EMAIL PROTECTED]
Andrew wrote:
Oh yeah. Duh. I knew that. :) I *will* try that someday, but I'm
lacking the required second machine at the moment.
Just need to get the turbine data across the
link (Assuming that YASIM is generating N1, N2, EGT, EPR, oil
pressure, fuel flow, etc)
Sure thing:
15 matches
Mail list logo
