* Mathias Fröhlich -- Saturday 01 July 2006 10:48:
On Saturday 01 July 2006 10:44, Melchior FRANZ wrote:
But it's not finished, and I'm not sure if I want to waste more time.
Why 'waste time'?
What do you have and what do you still need to do in your opinion?
You apparently missed that I had
Melchior FRANZ wrote:
This new code still requires several more hours of work. Tapes don't currently
work for the F16, everything needs more cleanup etc. A few FIXMEs to fix,
some TODOs to do. But now that I know that you are working on yet another
implementation, I consider every minute
* Erik Hofman -- Monday 03 July 2006 08:58:
I didn't have the impression that Mathias has been working on another
implementation at all. He just seemed to have looked over the code and
*did* try some workarounds for the HUD symbols to end up in the
scenegraph. Which doesn't sound like
* Melchior FRANZ -- Monday 03 July 2006 08:23:
Tapes don't currently work for the F16 [...]
BTW: the reason for this is that the F16 altitude tape uses this
setting:
input
property/position/altitude-ft/property
factor0.001/factor
max100/max
min-100/min
/input
Melchior FRANZ wrote:
BTW: the reason for this is that the F16 altitude tape uses this
setting:
input
property/position/altitude-ft/property
factor0.001/factor
max100/max
min-100/min
/input
major-divs1/major-divs
minor-divs0.1/minor-divs
* Erik Hofman -- Monday 03 July 2006 13:45:
I *think* I see what you mean.
What you could do right now is committing the new HUD code and activate
it in the f16at-set.xml only (if that's possible) then more developers
can look at it and try to figure out the problem.
No, no. You
Melchior FRANZ wrote:
* Erik Hofman -- Monday 03 July 2006 13:45:
What you could do right now is committing the new HUD code [...]
... but I should probably do that anyway, just so we have concrete
code to discuss, and maye even to work on. It should just be noted
Agreed.
that this is
On Mon, 03 Jul 2006 00:28:06 -0400, Josh wrote in message
[EMAIL PROTECTED]:
Arnt Karlsen wrote:
..this works, thanks, but I _should_ be able to use Ralf's Makefile
too. The idea is make this useable off a Live CD too.
Oh, I see. Yes, it should come with a valid .cvspass for an
Arnt Karlsen
On Mon, 03 Jul 2006 00:28:06 -0400, Josh wrote in message
[EMAIL PROTECTED]:
Arnt Karlsen wrote:
..this works, thanks, but I _should_ be able to use Ralf's Makefile
too. The idea is make this useable off a Live CD too.
Oh, I see. Yes, it should come with a
On Sun, 2 Jul 2006, Maik Justus wrote:
src/FDM/YASim/airplane.cpp in function void Airplane::solveHelicopter()
from
applyDragFactor(Math::pow(15.7/1000, 1/SOLVE_TWEAK));
applyLiftRatio(Math::pow(104, 1/SOLVE_TWEAK));
to
applyDragFactor(Math::pow(1, 1/SOLVE_TWEAK));
Josh Babcock wrote:
The ch-53e has a pretty odd empenage, so I need to make sure I
know what I am doing here. If I define a vstab with a dihedral
of 110, ahich side will it be on? Can I control which side it
is on?
The vstab is a left wing with a dihedral of 90 degrees. Making
it 110 degrees
On Mon, 3 Jul 2006 15:10:03 +0100, Vivian wrote in message
[EMAIL PROTECTED]:
Arnt Karlsen
On Mon, 03 Jul 2006 00:28:06 -0400, Josh wrote in message
[EMAIL PROTECTED]:
Arnt Karlsen wrote:
..this works, thanks, but I _should_ be able to use Ralf's
Makefile too. The
-Original Message-
From: [EMAIL PROTECTED] [mailto:flightgear-
[EMAIL PROTECTED] On Behalf Of Arnt Karlsen
Sent: 03 July 2006 17:08
To: FlightGear developers discussions
Subject: [Flightgear-devel] ..fixed, was:..~/.cvspass???
On Mon, 3 Jul 2006 15:10:03 +0100, Vivian wrote in
Hi,
Joacim Persson schrieb:
On Sun, 2 Jul 2006, Maik Justus wrote:
src/FDM/YASim/airplane.cpp in function void Airplane::solveHelicopter()
from
applyDragFactor(Math::pow(15.7/1000, 1/SOLVE_TWEAK));
applyLiftRatio(Math::pow(104, 1/SOLVE_TWEAK));
to
applyDragFactor(Math::pow(1,
Joacim Persson schrieb:
On Sun, 2 Jul 2006, Maik Justus wrote:
the helicopter simulation as it is in cvs has the bug, that any kind of
surfaces, stabs, fuselages have no aerodynamical effect.
That bugfix had a huge impact on the chinook. I still get a negative yaw
moment from the
On Mon, 3 Jul 2006 18:07:57 +0100, Vivian wrote in message
[EMAIL PROTECTED]:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:flightgear- [EMAIL PROTECTED] On Behalf
Of Arnt Karlsen Sent: 03 July 2006 17:08
To: FlightGear developers discussions
Subject: [Flightgear-devel]
On Monday 03 July 2006 08:23, Melchior FRANZ wrote:
You apparently missed that I had started to work on a new HUD
implementation in src/Instrumentation/HUD/. It is based on the old HUD, but
heavily changed, cleaned up, extended. I spent at least 20 hours work on
that, and you didn't bother to
On Mon, 3 Jul 2006, Maik Justus wrote:
We could on the other hand let the model designer set and tweak the
fuselage Cd manually in the config file.
That would be the easier way. Maybe it make sense to look, which results
the solver get for different airplanes.
...faking a wing from rotor
Andy Ross wrote:
Josh Babcock wrote:
The ch-53e has a pretty odd empenage, so I need to make sure I
know what I am doing here. If I define a vstab with a dihedral
of 110, ahich side will it be on? Can I control which side it
is on?
The vstab is a left wing with a dihedral of 90 degrees.
On Monday 03 July 2006 09:08, Melchior FRANZ wrote:
OK, but how should I go on with the broken F16 tape?! Mathias will probably
change that anyway, so is it worth spending time to fix it now?
To make that clear: I very much agree with Mathias plans, at least so
far as I know them. Putting the
Joacim Persson wrote:
Or translate the rotor equations to jsbsim -- ?
It always seemed odd that YASim should be the one to have rotary
support. The whole solver idea just doesn't seem to fit at all. Lookup
tables however work great for helos, you just have to calculate each
blade separately and
On Monday 03 July 2006 14:09, Erik Hofman wrote:
Melchior FRANZ wrote:
* Erik Hofman -- Monday 03 July 2006 13:45:
What you could do right now is committing the new HUD code [...]
... but I should probably do that anyway, just so we have concrete
code to discuss, and maye even to work
On Mon, 3 Jul 2006, Maik Justus wrote:
If you put the stick forward or backward there should be a yaw effect.
With the bugfix you have to cancel the torque generated by fuselage and
airspeed by putting the stick backward. This could be the cause for the
yaw. (Or dou you get the yaw moment
* Mathias Fröhlich -- Monday 03 July 2006 21:32:
Either by submitting patches between us or by using cvs for that task.
But before that we should really have a plan. I for one am against
using animations and textures for HUD symbols, and also against a
mixture of two techniques. An inhomogenous
On Saturday 01 July 2006 18:05, Josh Babcock wrote:
Is there some property that plane modelers can use to do LOD and turn
off certain animations on aircraft that are being flown remotely? Planes
like the bo105 with complex animations look pretty funny when they are
not being flown locally,
Melchior FRANZ a écrit :
The question would then only
be, how to draw lines if not with gl* commands, and how to transfer
that into the scenegraph?!
You can make a new ssgVtxTable with GL_LINES type :
ssgLeaf *leaf = new ssgVtxTable( GL_LINES, vertexList, normalList,
texCoordList,
Hi
Joacim Persson schrieb:
On Mon, 3 Jul 2006, Maik Justus wrote:
If you put the stick forward or backward there should be a yaw effect.
With the bugfix you have to cancel the torque generated by fuselage and
airspeed by putting the stick backward. This could be the cause for the
yaw.
On Monday 03 July 2006 21:37, Melchior FRANZ wrote:
But before that we should really have a plan. I for one am against
using animations and textures for HUD symbols, and also against a
mixture of two techniques. An inhomogenous solution will cause nothing
but problems, starting with different
On Mon, 3 Jul 2006, Josh Babcock wrote:
Joacim Persson wrote:
Or translate the rotor equations to jsbsim -- ?
It always seemed odd that YASim should be the one to have rotary
support. The whole solver idea just doesn't seem to fit at all. Lookup
tables however work great for helos, you
* Mathias Fröhlich -- Monday 03 July 2006 22:10:
May be we can implement a special leaf node that provides some vector drawing
primitives like lines or something like that. [...]
sounds good
To see if this path is worthwhile, it would be good to see the cleaned up
code ...
I hope I can
On Monday 03 July 2006 22:18, Melchior FRANZ wrote:
To see if this path is worthwhile, it would be good to see the cleaned up
code ...
I hope I can commit tomorrow. But the drawing code didn't change much
at all. My changes are mostly about cleaning up the classes, removing
redundant code,
Hi all , I have another silly question how does one enable autopilot
passive mode ?
Im rewriting my flightdirector routines because I thought that having
the autopilot in passive mode would give me readouts of target roll
and pitch properties without the autopilot controlling the plane
syd sandy wrote:
Hi all , I have another silly question how does one enable autopilot
passive mode ?
Im rewriting my flightdirector routines because I thought that having
the autopilot in passive mode would give me readouts of target roll
and pitch properties without the autopilot
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-01_15:06:05 (mfranz)
/var/cvs/SimGear-0.3/source/simgear/scene/model/shadanim.cxx
actually query the condition that is already set up in SGShaderAnimation
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-01_11:00:27 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Main/fg_init.cxx
make clear that Failed to find runway ... doesn't have fatal consequences
2f585eeea02e2c79d7b1d8c4963bae2d
Using Tomcat but need to do more? Need to
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-06-27_16:09:01 (mfranz)
/var/cvs/FlightGear-0.9/data/Models/Geometry/parachuter.ac
/var/cvs/FlightGear-0.9/data/Models/Geometry/parachuter.xml
Dave CULP: parachutera.k.a. Asparagus Man[TM]
I've been playing around with some scripts to leverage the autopilot to
chase ai/multiplayer aircraft and also some script to control the lead
ai aircraft in various ways. In the process I snapped a couple short
movies with my digital camera which I thought turned out pretty cool, so
I've
Jon S. Berndt wrote:
I've been playing around with some scripts to leverage the autopilot to
chase ai/multiplayer aircraft and also some script to control the lead
ai aircraft in various ways. In the process I snapped a couple short
movies with my digital camera which I thought turned out
38 matches
Mail list logo
