On Sunday 27 November 2005 08:56 pm, Jon Berndt wrote:
No. The VRP defines the location of an agreed-upon reference point in
structural coordinates. The CG, eyepoint, gear locations, etc. are all
defined (in JSBSim) in structural frame.
...
That was my understanding of it, but it seemed to
That was my understanding of it, but it seemed to not work with ___'s
Connie model. Upon further review it looks like ___'s Connie model has
an x-offset of about 14 meters, and I can't figure out why. So, I'll drop my
investigation of it.
Dave
:-)
Once we get the new JSBSim FDM
One thing that may be confusing is that the VRP setting given by aeromatic is
wrong. In the JSBSim configuration file If the CG location is X, Y, Z,
then the VRP location is -X, -Y, -Z.I had thought that AC_VRP defines the
location of the VRP, however it actually defines the location of
The Constellation looks pretty nice, but has a significant drawback:
The author has forgotten to implement the offset between FDM center and
visual reference point. This means the aircraft rotates around it's
nose which makes it almost impossible to accurately rotate for liftoff.
Furtheron it
Curt wrote:
As a project, FlightGear needs to depend on the stable releases of the
stuff it depends on, not cvs development trees. That get's to be too
big of a mess. Many distributions include the latest stable version of
plib, and that is often easier to build. It's ok for developers to
Vivian Meazza wrote:
So we have the situation where at least some of the current binary releases,
do not follow this policy. The Windows for one seems to accept the crease
token.
The policy is not meant for the binary releases. A binary-release
maintainer may even chose to use plib-1.7.3 if
Vivian Meazza wrote:
So we have the situation where at least some of the current binary releases,
do not follow this policy. The Windows for one seems to accept the crease
token.
Binary releases, by definition, are not meant to be rebuild, so the hassle of
collecting patches and making all
Erik Hofman wrote:
Vivian Meazza wrote:
So we have the situation where at least some of the current binary
releases,
do not follow this policy. The Windows for one seems to accept the
crease
token.
The policy is not meant for the binary releases. A binary-release
maintainer may
Vivian Meazza wrote:
Erik Hofman wrote:
The policy is not meant for the binary releases. A binary-release
maintainer may even chose to use plib-1.7.3 if he/she wishes to do so.
The policy is to make it _work_ with the latest official plib release.
Now I'm confused. Make what work?
Sorry, I
Quoting Vivian Meazza :
The patch has been committed to plib CVS. Now we only (...) need to
convince them to release a new stable version.
Excellent news, what about the joystick problem?
not committed yet, but I just asked again on the plib list.
-Fred
Melchior FRANZ
* Jon Stockill -- Tuesday 30 November 2004 16:39:
At 03:47 today.
Modified Files:
nimitz.ac
Log Message:
Remove crease tag so that people without custom patched versions of
plib can still run FlightGear. :-)
Yes, and at ... um ... right *now*:
$ cd
On Tue, 30 Nov 2004 18:40:53 -, Vivian Meazza
[EMAIL PROTECTED] wrote:
Sorry guys, I sent today's Nimitz before I realized that Curt was removing
crease tokens. Mind you, after all the effort we went to get it in ... I'm a
bit confused here. Mathias submitted a patch to plib, and I thought
Vivian Meazza wrote:
Sorry guys, I sent today's Nimitz before I realized that Curt was removing
crease tokens. Mind you, after all the effort we went to get it in ... I'm a
bit confused here. Mathias submitted a patch to plib, and I thought that
Wolfram Kuss had uploaded it. What's the problem -
David Megginson wrote:
On Tue, 30 Nov 2004 18:40:53 -, Vivian Meazza
No, it's just a matter of stability. We don't want FlightGear
releases to have to depend on prerelease CVS versions of plib, so we
have to wait until the next plib official release.
I'm not convinced that this actually
Martin Spott
No, it's just a matter of stability. We don't want FlightGear
releases to have to depend on prerelease CVS versions of plib, so we
have to wait until the next plib official release.
I'm not convinced that this actually is the point. FlightGear has a
history of depending
Vivian Meazza wrote:
Martin Spott
No, it's just a matter of stability. We don't want FlightGear
releases to have to depend on prerelease CVS versions of plib, so we
have to wait until the next plib official release.
I'm not convinced that this actually is the point. FlightGear has a
Curtis L. Olson wrote:
We all are busy. Steve is extremely busy. It doesn't hurt to follow up
on these things (more than once if needed.) If done in a sensitive
way, you can usually accomplish reasonable things with reasonable people.
I don't think anyone here is attempting to blame
Curtis L. Olson wrote:
Perhaps as a direct suggestion to the immediate issue of the crease
patch, we should get more FG people onboard as plib contributors with
cvs access so we can make direct contributions and get this fixed?
I looked at the developer list of the plib project (
Melchior FRANZ wrote
Mathias has put all the necessary stuff here:
ftp://ftp.uni-duisburg.de/FlightGear/Misc_maf/carrier/
The code that he sent me works well, but I haven't tried it from that
location yet.
I applied all the stuff and it worked very well. My first carrier landing
Jim Wilson
Curtis L. Olson said:
Jim Wilson wrote:
How about this one? ;-)
http://www.spiderbark.com/fgfs/barneymobile.png
Is that the don't-ask-don't-tellicopter.
Haha! Is this what they call aviation innuendo? What about
these folks:
Jim Wilson wrote
Vivian Meazza [EMAIL PROTECTED] said:
Josh Babcock
Vivian Meazza wrote:
I enter the loop in a shallow dive, 2nd stage boost on, 350
kts, pull
baaack the stick and the model rolls violently and does not
enter the
loop ... Works fine in
* Vivian Meazza -- Friday 13 February 2004 13:19:
Could the prop pitch be the problem
Unlikely -- it's already maximum by default.
- I can't find any method of controlling it
Either via http/telnet/property browser:
/controls/engines/engine[n]/propeller-pitch
Some joystick configs
Vivian Meazza [EMAIL PROTECTED] said:
Martin wrote:
David Megginson [EMAIL PROTECTED] wrote:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/pa28-161
In directory baron:/tmp/cvs-serv12589
Modified Files:
pa28-161-yasim-set.xml
Log Message:
Change camera position
Jim Wilson wrote
Vivian Meazza [EMAIL PROTECTED] said:
Martin wrote:
David Megginson [EMAIL PROTECTED] wrote:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/pa28-161
In directory baron:/tmp/cvs-serv12589
Modified Files:
pa28-161-yasim-set.xml
Jim Wilson added
Vivian Meazza [EMAIL PROTECTED] said:
Tried that. Looks just the same to me. As I said some time ago: yer
pays yer money and yer takes yer choice. Neither is right on the
ground for differential braking: with one brake full on the
aircraft
more or less rotates
Vivian Meazza wrote:
I enter the loop in a shallow dive, 2nd stage boost on, 350 kts, pull baaack
the stick and the model rolls violently and does not enter the loop ...
Works fine in other models so it's not the obvious - the joystick. But I
expect I'm doing something wrong.
Yup.
Jim Wilson asked
Vivian Meazza [EMAIL PROTECTED] said:
I moved the origin, then applied an equal and opposite offset. When
one differential brake is applied and the model is viewed in or
helicopter view tower view it appears to be turning around its axis
rather than around the
Josh Babcock
Vivian Meazza wrote:
I enter the loop in a shallow dive, 2nd stage boost on, 350
kts, pull
baaack the stick and the model rolls violently and does not
enter the
loop ... Works fine in other models so it's not the obvious - the
joystick. But I expect I'm doing
Jim Wilson wrote:
Erik Hofman [EMAIL PROTECTED] said:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/fokker100
In directory baron:/tmp/cvs-serv5280/Aircraft/fokker100
Log Message:
Directory /var/cvs/FlightGear-0.9/data/Aircraft/fokker100 added to the
repository
Hi Erik,
Think we're still
29 matches
Mail list logo
