Hi Melchior,
Melchior FRANZ schrieb am 10.12.2007 19:32:
> Note that loops/listeners that were started in have
> to be stopped/removed in ! Otherwise they will keep
> running (which is a feature), and you might accumulate them over
> time. The bo105 does that correctly, the v22 does not! :-)
>
>
* Melchior FRANZ -- Sunday 09 December 2007:
> * Melchior FRANZ -- Sunday 09 December 2007:
> > BTW: in my tests yesterday I noticed that the part was
> > never called, and so the loop is never stopped.
>
> Just for the record: yes, that's not done ATM. Will fix tomorrow.
Which is now done. It m
* Melchior FRANZ -- Sunday 09 December 2007:
> BTW: in my tests yesterday I noticed that the part was
> never called, and so the loop is never stopped.
Just for the record: yes, that's not done ATM. Will fix tomorrow.
m.
-
* Maik Justus -- Sunday 09 December 2007:
> With this trick I should be able to transfer the wing-fold
> and engine-tilt animation of the v22 over the MP-protocol.
Yeah, that's a typical case for properties where standardization
wouldn't make much sense, and generic ones are therefore preferable
Hi Melchior,
Melchior FRANZ schrieb am 08.12.2007 17:08:
> * Melchior FRANZ -- Saturday 08 December 2007:
>
>> it was time to add some generic properties for "internal communication".
>>
>
> It's probably also time to remind people again of the possibility to
> add Nasal code to model (anim
* Anders Gidenstam -- Saturday 08 December 2007:
> Though my dual control version of the c172p already uses more
> than 10 extra float properties.. :)
I have no problem with adding more, now that I know that they
have no effect if they aren't used. And if you are using some
others, anyway, then we
On Sat, 8 Dec 2007, gerard robin wrote:
> Nasal animation Probably valuable for YASim but with JSBsim their is an other
> way easier.
But those properties are not sent over MP - which is the whole point of
the /sim/multiplay/generic/* properties.
While I agree that JSBSim allows many useful tr
* gerard robin -- Saturday 08 December 2007:
> but don't forget that we can within JSBSim avoid most of the Nasal code
> everything done in the FDM.
Again: this doesn't even *work* for what you fear it could be (ab)used.
The bit of Nasal code in bo105.xml is simply ignored if you fly the
bo105. I
On sam 8 décembre 2007, Melchior FRANZ wrote:
> * Melchior FRANZ -- Saturday 08 December 2007:
> > it was time to add some generic properties for "internal communication".
>
> It's probably also time to remind people again of the possibility to
> add Nasal code to model (animation) XML files. This
* Melchior FRANZ -- Saturday 08 December 2007:
> $FG_ROOT/Aircraft/Models/bo105.xml
Bah ... $FG_ROOT/Aircraft/bo105/Models/bo105.xml
m.
-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the
* Melchior FRANZ -- Saturday 08 December 2007:
> it was time to add some generic properties for "internal communication".
It's probably also time to remind people again of the possibility to
add Nasal code to model (animation) XML files. This is then only
run when the model is used as as a static
* gerard robin -- Saturday 08 December 2007:
> I worry that way /sim/multiplay/generic/.. because i thought
> that the best way, regarding every surface position was to
> include it into the "/surface-positions/foo" property
You miss the point, as maybe some others do as well. The generic
pr
AnMaster
> Sent: 08 December 2007 14:02
> To: FlightGear developers discussions
> Subject: Re: [Flightgear-devel] multiplayer generic properties
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Vivian Meazza wrote:
> > Anders has a really neat
On sam 8 décembre 2007, Vivian Meazza wrote:
> AnMaster
>
> > Sent: 08 December 2007 11:55
> > To: FlightGear developers discussions
> > Subject: Re: [Flightgear-devel] multiplayer generic properties
> >
SNIP
> >
> > Melchior FRANZ wrote:
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Vivian Meazza wrote:
> Anders has a really neat bit-mask utility which allows the transmission of
> up to 32 bools in one int property - much neater for light switches and the
> like.
>
> Vivian
>
> P.S. - by tradition we bottom-post on the devel l
AnMaster
> Sent: 08 December 2007 11:55
> To: FlightGear developers discussions
> Subject: Re: [Flightgear-devel] multiplayer generic properties
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Yes, I already made a patch (see "[Flightgear-devel] P
* AnMaster -- Saturday 08 December 2007:
> Yes, I already made a patch (see "[Flightgear-devel] Patch for
> Harrier: making it's thrust vector work over mp") for the harrier
> that makes use of this :)
Yes, you are quick. This will have to be reviewed and OK'ed by the
harrier model maintainer.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Yes, I already made a patch (see "[Flightgear-devel] Patch for Harrier: making
it's thrust vector work over mp") for the harrier that makes use of this :)
And I can think of several other aircrafts that could make use of this. For
example position l
After Maik has clued me up about multiplayer properties -- that
only those are transmitted, which actually exist at init time
(which is why they need to be defined in the *-set.xml file),
it was time to add some generic properties for "internal communication".
That is: properties which aren't dedic
19 matches
Mail list logo
