Hello,
Probably a stupid question (i promise will be the last of the year)
I would like to know (to calculate) the diff of position between the position
of the aircraft and the position of a specific point on an AI object in my
case the catapult and the wires on the carrier.
Is their
On Dec 22, 2007 7:46 PM, gerard robin [EMAIL PROTECTED] wrote:
Hello,
Probably a stupid question (i promise will be the last of the year)
I would like to know (to calculate) the diff of position between the position
of the aircraft and the position of a specific point on an AI object in
On sam 22 décembre 2007, Csaba Halász wrote:
On Dec 22, 2007 7:46 PM, gerard robin [EMAIL PROTECTED] wrote:
Hello,
Probably a stupid question (i promise will be the last of the year)
I would like to know (to calculate) the diff of position between the
position of the aircraft and the
* gerard robin -- Saturday 22 December 2007:
The problem here is we don't have a generic solution this must
be calculated for each carrier or any AI object according to the
.xml file definition , one calculation for Nimitz one for Foch one
for ... and so on.
That's not the problem.
* gerard robin -- Saturday 22 December 2007:
The problem here is we don't have a generic solution this must
be calculated for each carrier or any AI object [...]
Ah, you want to avoid the calculation per object. Frankly, I don't
think that's such a generic problem. Most carrier capable
On Dec 22, 2007 8:55 PM, Melchior FRANZ [EMAIL PROTECTED] wrote:
And even if: noting down offsets is something that we as modelers
do all the time anyway, as we need it in animations.
Well, the FGAICarrier code already finds catapult and wire nodes,
maybe we can just add them to the property
* Csaba Halász -- Saturday 22 December 2007:
Well, the FGAICarrier code already finds catapult and wire nodes,
maybe we can just add them to the property tree there?
But it does so as an OSG node visitor with intersection testing
done by OSG, or something. One could certainly get the values
* Melchior FRANZ -- Saturday 22 December 2007:
One could certainly get the values out, but that would be a
lot more work.
Oh, and the manual way has the advantage that you can easily add
arbitrary stuff, such as other (non-cat) vertex offsets, or offsets
for places where no vertex is anywhere
On sam 22 décembre 2007, Melchior FRANZ wrote:
* gerard robin -- Saturday 22 December 2007:
The problem here is we don't have a generic solution this must
be calculated for each carrier or any AI object according to the
.xml file definition , one calculation for Nimitz one for Foch one
On sam 22 décembre 2007, Melchior FRANZ wrote:
* Csaba Halász -- Saturday 22 December 2007:
Well, the FGAICarrier code already finds catapult and wire nodes,
maybe we can just add them to the property tree there?
But it does so as an OSG node visitor with intersection testing
done by OSG,
On sam 22 décembre 2007, Melchior FRANZ wrote:
* gerard robin -- Saturday 22 December 2007:
It is the best way, to have in property the coordinates of the points
which are defined in the AI model (may be, the precision would a
problem)
The properties are the smaller problem, whether
* gerard robin -- Saturday 22 December 2007:
Yet, we have such information out of YAsim, from AI ? (like said Csaba )
fgfs --aircraft=WhichFly --carrier=WichFloat --parkpos=cat1
FG place the WhichFly at the right place on the cat
Yes, but that's something else -- that's defined in the
12 matches
Mail list logo
