I'm working on a STOL aircraft, the Fiesler Fi-156, and I thought it
might be fun to land in Candlestick park... Unfortunately, the lack of
detail inside the stadium makes it really hard.
So I added 12 rectangles to the model to create a football field.
http://www.jentronics.com/fgfs/candlestick.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed; thanks.
Tim
Hans Ulrich Niedermann wrote:
> Allow parallel make ("make -j2") by giving make the opportunity to
> determine dependencies.
>
> As in subdirectory foo/bar, $(top_builddir)/foo/bar is defined to be the
> current directory, this
> I would need:
> CLtail = f(alpha_tail, delta_elevator)
>
> where alpha_tail = alpha_aircraft + horizontal_stab_angle - Epsilon
We should be able to do this.
> Some time ago I've been told that this can be done using the
> speedbrake property (indeed this is the way it is done in the 747
> ex
>
> No assumptions are made for the horizontal stabilizer, whether it is
> all-moving, or is fixed with a movable surface. There is only a deflection
> associated with the surface, and that is used to index into an aero table. I
> am not quite sure what you need, or what you are referring to here.
Ron Jensen schrieb:
>
>
> This can be fixed by removing the
> true
> line from c150/Models/c150.xml.
>
> However removing that line makes the instruments overlay the yoke. The
> other solution is to do a proper 3D panel and remove the 2.5D panel.
>
> Ron
>
>
Thank you Ron, for pointing this
On Sun, 2007-07-22 at 21:03 +0200, Sébastien MARQUE wrote:
> hi all,
>
> I just tested the new c150, it's a very nice piece of aircraft and
> surely one of my favorite ones ;)
>
> I wanted to report that the 3D panel is continuously blinking on my
> fresh compilation of FG/CVS OSG/SVN, using os
* Harald JOHNSEN -- Sunday 22 July 2007:
> I'll make the change to overide the other function too.
Ahh, I hadn't thought of JSBSim using hard-coded property paths.
Yes, looks like redefining the other function is the only solution
then. Will fix lots of joysticks *and* the key binding (m/M keys).
> Indeed, I was talking about two 2-D tables, "wrongly" guessing that
> JSBSim would interpolate the data in case, let's say, the current slat
> position is not any of the specific slat for which the tables are
> defined. Such an interpolation would be quite accurate, being better
There certainly
>
> We could probably use the existing code to do that interpolation between two
> or more tables. It would just be really ugly. In the case of DATOM+ output,
> I'd have to generate that ugly code automatically.
Well, it may be ugly and inaccurate, but for some cases the phisics
could probably be
> Indeed, I was talking about two 2-D tables, "wrongly"
> guessing that JSBSim would interpolate the data in case,
> let's say, the current slat position is not any of the
> specific slat for which the tables are defined. Such an
> interpolation would be quite accurate, being better the mor
See my comment after quotation...
> 2. I think what you are saying is:
>
>epsilon = f( alpha, flap, slat )
>
> I don't think that you were advocating using two 2-D table
>
>epsilon(slat=0) = f ( alpha, flap )
>epsilon(slat=20) = f ( alpha, flap )
>
> If you were, there wou
hi all,
I just tested the new c150, it's a very nice piece of aircraft and
surely one of my favorite ones ;)
I wanted to report that the 3D panel is continuously blinking on my
fresh compilation of FG/CVS OSG/SVN, using osgviewer. here are some snaps:
http://seb.marque.free.fr/fichiers/flightge
Melchior FRANZ wrote:
>I also removed the "userarchive" flags on the hobbs and yoke properties,
>and let those properties be written to the c150's own aircraft config
>instead. I decided to not wait for your reply, as the "userarchive"
>settings polluted the systems's autosave.xml file, which woul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The altitude following mode of the --aircraft=mibs is "lazy", that is it
doesn't follow very closely, while this is good in case of for example loops,
it cause problems when following for example a climbing Concorde.
See this screenshot for an exampl
* Melchior FRANZ -- Saturday 21 July 2007:
> (I only changed text files with MSDOS line terminators to Unix
> style according to fgfs rules. :-)
I also removed the "userarchive" flags on the hobbs and yoke properties,
and let those properties be written to the c150's own aircraft config
instead. I
> On the topic of calculating downwash at the tail, and the
> effects thereof, rather than make a four dimensional table it
> might be better to think outside the box and consider
> alternative ways to do what you need.
I agree. That's why I brought it up in the first place, to see if anyon
On Sat 21 July 2007 19:06, Harald JOHNSEN wrote:
> Jon S. Berndt wrote:
> >Nice looking 3D model. Did you use the JSBSim converter to convert the
> >model? Was it relatively painless? Do I even want to know? ;-)
> >
> >Jon
>
> Thank, yes I used the converter at the begining, I don't remember
> exac
On the topic of calculating downwash at the tail, and the effects thereof,
rather than make a four dimensional table it might be better to think
outside the box and consider alternative ways to do what you need. Modeling
ground effect is one example of that. It's a function that is calculated
outsi
FG/OSG currently offers to build the "fgfs" binary as one of three
different versions:
a) Using glut
b) Using SDL
c) Using osgViewer
As the whole thing is still in development, it makes sense for
developers to have more than just one of the three, so that one can
compare their behaviours.
> Quoting Fabian Grodek
> Now, regarding the 737 sample case, it should be checked
> which flaps-slats combinations are normally possible; it may
> be the case where let's say flaps 20 cannot come with
> retracted slats (if there is a problem with the slats
> deployment you are allowed to u
Fix typo in README
Index: README
===
RCS file: /var/cvs/FlightGear-0.9/source/README,v
retrieving revision 1.2
diff -u -p -r1.2 README
--- README 19 Nov 2004 22:10:41 - 1.2
+++ README 22 Jul 2007 13:46:13 -
@@ -7,7 +7,7 @@ For
avoid g++ warning about the members being initialized out of order
Index: src/Cockpit/hud.hxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/Cockpit/hud.hxx,v
retrieving revision 1.38
diff -u -p -r1.38 hud.hxx
--- src/Cockpit/hud.hxx
Allow parallel make ("make -j2") by giving make the opportunity to
determine dependencies.
As in subdirectory foo/bar, $(top_builddir)/foo/bar is defined to be the
current directory, this does not cause any regressions.
Index: simgear/bucket/Makefile.am
Fix typo
Index: Thanks
===
RCS file: /var/cvs/SimGear-0.3/source/Thanks,v
retrieving revision 1.4
diff -u -p -r1.4 Thanks
--- Thanks 15 May 2007 22:28:08 - 1.4
+++ Thanks 22 Jul 2007 13:53:41 -
@@ -120,7 +120,7 @@ Petter Reinho
Print $CC and $CXX using the proper configure.ac mechanism
Index: configure.ac
===
RCS file: /var/cvs/SimGear-0.3/source/configure.ac,v
retrieving revision 1.101
diff -u -p -r1.101 configure.ac
--- configure.ac 30 Oct 2006 19:56:09 -00
>
> Finally, one short question: why there is no dedicated horizontal
> stabilizer property available in JSBSim, and we need to use for this
> the speedbrake property? Just curious...
>
> Fabian
Are you talking about JSBSim, or DATCOM? I'm not sure I understand your
question. There is a property
First, thank you all for the direct answers to my question.
Now, regarding the 737 sample case, it should be checked which
flaps-slats combinations are normally possible; it may be the case
where let's say flaps 20 cannot come with retracted slats (if there is
a problem with the slats deployment y
> I saw that ans it is a bit disturbing. If I understand well
> you take the output from datcom and assign half of those
> numbers to each flap. Except that we suddenly have negative
> flap angles in the datcom.xml (they are positive in datcom.out).
ZOIKS! You are correct. It was caused by
Bill Galbraith wrote:
> <>
> Don't know if anyone noticed, but the flaps are already split left and
> right. I did this for the asymetric flap deflection issue.
I saw that ans it is a bit disturbing. If I understand well you take the
output from datcom and assign half of those numbers to each f
29 matches
Mail list logo
