JSBSim (def), YASim and 'magic' - zlib
Note: JSBSim config files allow the user to specify a log file to be
generated
Wow! Yes, when I looked around after the
'flight' I saw this abt 6 MB csv file,
and wondered - 'where did that come
from?'. I had a quick peek inside and
deleted that first one
Tony Peden writes:
IMO, the logging options should be moved off to a separate file and
no version of that file should be committed to base CVS.
That way, no user will ever get logging when they don't want it and
developers can set things up the way they like for *all* JSBSim
aircraft.
Has anyone ever tried incorporating a sub window into flightgear? If so, is
there some sort of trick?
I have a sub window running with flightgear, but it appears that something
in FG is overriding what happens inside the
sub window.
Please excuse my posting to the wrong list.
Thanks,
Dawn
You can 'see' that it took some 2 minutes -
130.792 secs to be exact - before i got the
engine rolling ... so that's some 1310
lines (@ 10 HZ) of csv that yield little ...
One can be puzzled why the last column,
very largely labeled engine[?].RPM starts
at 1071.807 RPM, but over the next 10-15
IMO, the logging options should be moved off to a separate file and
no version of that file should be committed to base CVS.
That way, no user will ever get logging when they don't want it and
developers can set things up the way they like for *all* JSBSim
aircraft.
This is probably true, but
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]
In an effort to learn 3-D modeling, I've been tinkering with a DC-3
model in Blender -- so far, it's been much easier than I expected.
The model is just roughed in -- it's untextured and far from complete
(no propeller, hub, exhaust, ailerons, flaps, or struts, some funky
normals, etc.), but you
On Saturday 26 January 2002 04:09 pm, you wrote:
In an effort to learn 3-D modeling, I've been tinkering with a DC-3
model in Blender -- so far, it's been much easier than I expected.
The model is just roughed in -- it's untextured and far from complete
(no propeller, hub, exhaust, ailerons,
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:
When started with --props=socket,bi,5,localhost,5501,tcp fgfs does only
allow one session e.g. via telnet. After closing this session, it isn't
possible to connect again.
I had a look at that problem and seem to have found the reason. Yet
I cannot provide a patch. On the one hand I'm not
14 matches
Mail list logo
