At 11/10/02, Jon Berndt wrote:
Michael:
What are your design references for the two WWI aircraft?
Do you mean how did I get the aero data?
Regards,
Michael
**
Prof. Michael S. Selig
Dept. of Aero/Astro Engineering
University of Illinoi
Michael:
What are your design references for the two WWI aircraft?
Jon
smime.p7s
Description: application/pkcs7-signature
I have just added the Fokker Dr.1 triplane to the CVS. There are notes in
the readme below about how to get a 3D model file. Unfortunately, I could
not acquire one under the GNU GPL.
If I were going to be in a dog fight and had my pick of the Camel or Dr.1,
the Dr.1 would be the weapon of ch
* [EMAIL PROTECTED] (Michael Selig) [2002.11.10 13:21]:
> At 11/10/02, Jim Wilson wrote:
> >What a great addition to the fleet! Beautiful 3D model too. Would
> >you or A.F. Scrub mind if I converted that to ac3d? The purpose
> >would be to convert the textures to rgb, alpha the prop disk,
> >ani
David Luff writes:
> So basically they're 2-way, but sequentially, with planes never
> passing wing-tip to wing-tip in opposite directions each side of
> the yellow line?
The yellow line is where your nosewheel is supposed to be. That said,
little planes pass each other all the time on taxiwa
Julian Foad writes:
> It seems silly to have the "brake" key slam on full braking power, if it
> is to be used on the runway. No wonder the aircraft tend to tip over or
> burst their tyres. Can I recommend this patch which sets the "all
> brakes" strength to 0.5 and the individual left/ri
> It seems silly to have the "brake" key slam on full braking power, if it
> is to be used on the runway. No wonder the aircraft tend to tip over or
> burst their tyres. Can I recommend this patch which sets the "all
> brakes" strength to 0.5 and the individual left/right to 0.7?
One option migh
On 11/7/02 at 4:33 PM David Megginson wrote:
Thanks.
>
> > Are major taxiways such as the one parallel to the rwy that
> > normally seems to be called Alpha 2-way or is the traffic normally
> > directed one-way on them by ATC depending on the rwy in use?
>
>That would be very airport specific,
On 11/10/02 at 4:02 AM Julian Foad wrote:
>
>As for the guts of how the engines are modelled ... I first worked on
>the starting and stopping behaviour of the JSBsim engine. The
>thermodynamic model of the engine is probably very good
Parts of it are, parts of it aren't and are overdue a re-vi
I noticed that the radios had nav. freq. range 108.00 to 117.95 but com.
freq. 0 to 140; this should be 118 to 140. But while playing with that
I noticed that the wrapping is a bit unpredictable. With (min=118,
max=140, step=1, wrap=true) adjusting it up and down, it sometimes skips
118 and s
Andy Ross wrote:
Julian Foad wrote:
> It seems silly to have the "brake" key slam on full braking power, if
...
This issue came up about a year ago. There really isn't any good
resolution.
...
My favorite hack, FWIW, was to have the on/off input affect the
braking power slowly -- over a sec
Julian Foad wrote:
> It seems silly to have the "brake" key slam on full braking power, if
> it is to be used on the runway. No wonder the aircraft tend to tip
> over or burst their tyres. Can I recommend this patch which sets the
> "all brakes" strength to 0.5 and the individual left/right to 0.
At 11/10/02, John Check wrote:
On Sunday 10 November 2002 2:24 pm, Curtis L. Olson wrote:
> Michael Selig writes:
> > Since these are imports courtesy of developers working with MSFS, would
> > it be a good idea to keep a copy of their models in original form in a
> > separate directory? That way
It seems silly to have the "brake" key slam on full braking power, if it
is to be used on the runway. No wonder the aircraft tend to tip over or
burst their tyres. Can I recommend this patch which sets the "all
brakes" strength to 0.5 and the individual left/right to 0.7?
Personally I do the
At 11/10/02, John Check wrote:
On Sunday 10 November 2002 2:24 pm, Curtis L. Olson wrote:
> Michael Selig writes:
> > Since these are imports courtesy of developers working with MSFS, would
> > it be a good idea to keep a copy of their models in original form in a
> > separate directory? That way
At 11/10/02, you wrote:
On Sunday 10 November 2002 2:37 pm, Michael Selig wrote:
> At 11/10/02, Curt Olson wrote:
> >Michael Selig writes:
> > > Since these are imports courtesy of developers working with MSFS, would
> > > it be a good idea to keep a copy of their models in original form in a
> >
At 11/10/02, John Check wrote:
On Sunday 10 November 2002 2:21 pm, Michael Selig wrote:
> At 11/10/02, Jim Wilson wrote:
> >David Megginson <[EMAIL PROTECTED]> said:
> > > Thank you very much. It might be a good idea in the future to put 3D
> > > models directly into Aircraft/*/Models/ rather tha
On Sunday 10 November 2002 2:24 pm, Curtis L. Olson wrote:
> Michael Selig writes:
> > Since these are imports courtesy of developers working with MSFS, would
> > it be a good idea to keep a copy of their models in original form in a
> > separate directory? That way they could always come to FGFS
On Sunday 10 November 2002 2:37 pm, Michael Selig wrote:
> At 11/10/02, Curt Olson wrote:
> >Michael Selig writes:
> > > Since these are imports courtesy of developers working with MSFS, would
> > > it be a good idea to keep a copy of their models in original form in a
> > > separate directory? Th
On Sunday 10 November 2002 2:24 pm, Curtis L. Olson wrote:
> Michael Selig writes:
> > Since these are imports courtesy of developers working with MSFS, would
> > it be a good idea to keep a copy of their models in original form in a
> > separate directory? That way they could always come to FGFS
On Sunday 10 November 2002 2:21 pm, Michael Selig wrote:
> At 11/10/02, Jim Wilson wrote:
> >David Megginson <[EMAIL PROTECTED]> said:
> > > Thank you very much. It might be a good idea in the future to put 3D
> > > models directly into Aircraft/*/Models/ rather than
> > > Aircraft/*/Models/uiuc/,
I had to remove a declaration of "memrchr" from simgear/metar/Local.h to
compile under gcc 3.2 (SuSE Linux 8.1). There are lots of semi-standard
functions declared there that probably shouldn't be.
To fix some warnings I added "typename" into some "typedef" lines. I am
not sure about the corr
At 11/10/02, Curt Olson wrote:
Michael Selig writes:
> Since these are imports courtesy of developers working with MSFS, would it
> be a good idea to keep a copy of their models in original form in a
> separate directory? That way they could always come to FGFS and fly their
> original models as
Michael Selig writes:
> Since these are imports courtesy of developers working with MSFS, would it
> be a good idea to keep a copy of their models in original form in a
> separate directory? That way they could always come to FGFS and fly their
> original models as well as any enhancements to t
At 11/10/02, Jim Wilson wrote:
Hi Michael,
What a great addition to the fleet! Beautiful 3D model too. Would you or
A.F. Scrub mind if I converted that to ac3d? The purpose would be to convert
the textures to rgb, alpha the prop disk, animate, and add 3D instrumentation
similar to the j3cub (w
At 11/10/02, Jim Wilson wrote:
David Megginson <[EMAIL PROTECTED]> said:
>
> Thank you very much. It might be a good idea in the future to put 3D
> models directly into Aircraft/*/Models/ rather than
> Aircraft/*/Models/uiuc/, since 3D models are usable by all FDMs (all
> four major ones use the
Andy Ross wrote:
Jim Wilson wrote:
> Anyway, what I now remember is this: the camera position as configured
> for the chase view is always in relation to the FDM location. And in
> the case of Yasim that location is always the nose.
Oh, good point. This will create problems for view directi
David Megginson <[EMAIL PROTECTED]> said:
>
> Thank you very much. It might be a good idea in the future to put 3D
> models directly into Aircraft/*/Models/ rather than
> Aircraft/*/Models/uiuc/, since 3D models are usable by all FDMs (all
> four major ones use the same C172 model, for example).
Hi Michael,
What a great addition to the fleet! Beautiful 3D model too. Would you or
A.F. Scrub mind if I converted that to ac3d? The purpose would be to convert
the textures to rgb, alpha the prop disk, animate, and add 3D instrumentation
similar to the j3cub (which would involve a few cockpit
Andy Ross writes:
> I'd *love* to see good numbers for propeller acceleration, however.
> If one of the Real Pilots out there could go out with a stopwatch and
> get us graphs of RPM vs. time for full throttle acceleration and
> cut-power deceleration I'd be eternally grateful. :)
I don't wan
Michael Selig writes:
> I have just added a Sopwith Camel to the CVS. Not only does it
> include the flight dynamics model, but also there's an external model
> from A.F. Scrub! He has granted permission for us to use and release
> these with FlightGear under the GNU GPL.
>
> There's a re
Julian Foad writes:
> Well, I suppose it needs someone to show how the two aims can be
> compatible. But it's not easy; it would require becoming familiar with
> both implementations and re-arranging the interfaces a bit. While
> that's the sort of thing I do at work, I'm not yet in a pos
You've been busy this weekend, it's always nice to see the range of
aircraft increasing. I'm still on my way to making the CVS work (I'm
very busy here), when I do it'll be great to have a go with all these
aircraft. If I'm lucky I might get something done on the spitfire model
today...
Chris
O
33 matches
Mail list logo