Jim Wilson [EMAIL PROTECTED] wrote:
Heh don't laugh. At LWCE Borland was giving away Kylix which is basically
delphi ported to linux...and if i'm not mistaken that uses something like
turbo pascal as its language. It's what they call a RAD tool. Or is it a
RAG (rapid atrocity generation)
Michael Selig wrote:
At 3/14/02, you wrote:
Just a quick note and question. I've been able to get engine sound
for the different models except the UIUC models. Specifically I've
been running the different versions of the Cessna 172. JSB and
Larcsim both produce engine sound but UIUC
Tony Peden writes:
You need to write the data to the appropriate properties. You might
take a look at JSBSim.[ch]xx and what we're doing with the
/surface-positions/elevator-pos-norm
/surface-positions/rudder-pos-norm
etc.
For LaRCSim, I just added code to copy the control inputs
Erik Hofman writes:
To get it working the UIUC code should populate the property tree with
at least the following properties (for a piston engine driven aeroplane):
starting/stoping the sounds:
---
/engines/engine/cranking
/engines/engine/running
David Megginson wrote:
Erik Hofman writes:
To get it working the UIUC code should populate the property tree with
at least the following properties (for a piston engine driven aeroplane):
starting/stoping the sounds:
---
/engines/engine/cranking
At 3/15/02, you wrote:
David Megginson wrote:
Erik Hofman writes:
To get it working the UIUC code should populate the property tree
with at least the following properties (for a piston engine driven
aeroplane):
starting/stoping the sounds:
---
On Friday 15 March 2002 01:57 pm, you wrote:
At 3/15/02, you wrote:
[2] Where should we put the sound files. Right now the files are in
~fbfsbase/Sounds. But different aircraft will have different
sounds. Should these sound files go in the respective ~fgfsbase/Aircraft
directories?
Jon S Berndt writes:
The best solution would be for the UIUC guys to bite the
bullet and port their work to use JSBSim. :-) :-) :-)
Hmm -- today seems to be a big day for trolls. I wonder if any of
Jon's NASA contacts are still waiting for him to bite the bullet and
port JSBSim to
David Megginson writes:
Jon S Berndt writes:
The best solution would be for the UIUC guys to bite the
bullet and port their work to use JSBSim. :-) :-) :-)
Hmm -- today seems to be a big day for trolls. I wonder if any of
Jon's NASA contacts are still waiting for him to bite the
David Megginson wrote:
Jon S Berndt writes:
The best solution would be for the UIUC guys to bite the
bullet and port their work to use JSBSim. :-) :-) :-)
Hmm -- today seems to be a big day for trolls. I wonder if any of
Jon's NASA contacts are still waiting for him to bite the
On Friday 15 March 2002 02:20 pm, you wrote:
Michael Selig writes:
Thanks for all the input on this. It helped get us going. The
properties structure is pretty neat!
Thanks.
If few questions (probably too many):
[1] Does it sense to define and set our properties inside
The best solution would be for the UIUC guys to bite the
bullet and port their work to use JSBSim. :-) :-) :-)
Hmm -- today seems to be a big day for trolls. I wonder if any of
Jon's NASA contacts are still waiting for him to bite the bullet and
port JSBSim to FORTRAN.
Why?
On Friday 15 March 2002 05:15 pm, you wrote:
The best solution would be for the UIUC guys to bite the
bullet and port their work to use JSBSim. :-) :-) :-)
Hmm -- today seems to be a big day for trolls. I wonder if any of
Jon's NASA contacts are still waiting for him
David Megginson wrote:
Curtis L. Olson writes:
I'm just about to commit a massive series of changes that converts all
the .xml files to more standard .ini files. Oh, shoot, I meant to
save that announcement for 4/1/2002. :-)
We have to coordinate better -- I'm just finishing
I'm just about to commit a massive series of changes that converts all
the .xml files to more standard .ini files. Oh, shoot, I meant to
save that announcement for 4/1/2002. :-)
We have to coordinate better -- I'm just finishing switching them all
to TeX. FlightTeX will be
David Megginson [EMAIL PROTECTED] said:
Curtis L. Olson writes:
I'm just about to commit a massive series of changes that converts all
the .xml files to more standard .ini files. Oh, shoot, I meant to
save that announcement for 4/1/2002. :-)
We have to coordinate better -- I'm
Jim Wilson wrote:
Heh don't laugh. At LWCE Borland was giving away Kylix which is
basically delphi ported to linux...and if i'm not mistaken that uses
something like turbo pascal as its language. It's what they call a
RAD tool. Or is it a RAG (rapid atrocity generation) tool?
That's
Gene Buckle writes:
If you're going to insist on cross-platform portability, then it should
obviously be Python.
Shhh...
a Python FGFS is probably closer to being unleashed then
most have any inkling of, so let's not scare it away :-)
Norman
___
On Fri, 15 Mar 2002 23:01:59 -
Jim Wilson [EMAIL PROTECTED] wrote:
Heh don't laugh. At LWCE Borland was giving away Kylix
which is basically
delphi ported to linux...and if i'm not mistaken that
uses something like
turbo pascal as its language. It's what they call a
RAD tool. Or is
On Fri, 15 Mar 2002 14:20:49 -0500
Michael Selig writes:
If we do add the myriad properties for many aircraft configuration
types to LaRCsim.cxx it means adding lots of code I think.
[3] The properties structure is pretty general. It seems like it
would be pretty easy to trample
Jon S Berndt [EMAIL PROTECTED] said:
Don't laugh, yourself! ;-) I've used C++Builder since
v1.0 and it's an awesome tool. It is waaay RAD. I'm
excited that they ported Delphi to Linux, and the C++
version is due soon. In a former job we used it for
developing a *major* gas measurement
At 3/14/02, you wrote:
Just a
quick note and question. I've been able to get engine sound for the
different models except the UIUC models. Specifically I've been
running the different versions of the Cessna 172. JSB and Larcsim
both produce engine sound but UIUC doesn't. I've looked at the xml
22 matches
Mail list logo
