This forum is no longer active. Reference only.

Hi Peter,
i can see you are using (A:ATC FLIGHT NUMBER,string) to broadcast "Owner" (aka nickname) into the Net.
Good move, our vACMI uses it to mantain ID unicity, may i assume you won't change it in the future ?
Tia
/Mario
BTW:
May be you can make a steady feature to broadcast(A:PAYLOAD STATION WEIGHT:index, Pounds) ?

Hi Mario,

I think I'm using (A:ATC ID, string) for the nickname, and the ATC FLIGHT NUMBER is blanks at the moment, I think.

Yes, I can broadcast the PAYLOAD STATION WEIGHT. Which indices would you like to be broadcast?

Peter

Peter wrote:Hi Mario,
I think I'm using (A:ATC ID, string) for the nickname, and the ATC FLIGHT NUMBER is blanks at the moment, I think.
Yes, I can broadcast the PAYLOAD STATION WEIGHT. Which indices would you like to be broadcast?
Peter

Hi Peter,
i see the JoinFS assigned nickname into "Owner" column of the "AIrcraft View",
(A:ATC ID, string) shows on "Callsign" column.
Using TrafficInfo.dll interface, "Owner" column matches with "atc flight number".
That's ok for us and would like not be changed.
I guess (A:PAYLOAD STATION WEIGHT:index, pounds) index from1 to 32 are ok.
tia
/Mario

Hi peter,

Any news about to broadcasting the simvar (A:PAYLOAD STATION WEIGHT:index, Pounds).? Thx for your awesome program!

bolichin wrote:Any news about to broadcasting the simvar (A:PAYLOAD STATION WEIGHT:index, Pounds).? Thx for your awesome program!

Instead of adding all of these little features into JoinFS itself, at some point (probably a few months away) I'm planning on implementing a simple software interface, possibly using SimConnect, that will allow any third party developer to propagate any custom data they like across the JoinFS network session. Think of it as piggybacking on the JoinFS network, where the developer will access a list of aircraft/objects/users with unique IDs that they can assign any custom data to. This data will then be automatically propagated over the network and can be read by the same add-on running on each user's machine.

What this means is that JoinFS can be leaner and will be providing two essential things: a stable cross-platform network and smooth object updates, but have potentially an unlimited expansion of features provided by third party add-on developers.

I think this could be the best way forward for JoinFS.

Peter

Interesting approach!!!

Peter wrote:

bolichin wrote:Any news about to broadcasting the simvar (A:PAYLOAD STATION WEIGHT:index, Pounds).? Thx for your awesome program!

Instead of adding all of these little features into JoinFS itself, at some point (probably a few months away) I'm planning on implementing a simple software interface, possibly using SimConnect, that will allow any third party developer to propagate any custom data they like across the JoinFS network session. Think of it as piggybacking on the JoinFS network, where the developer will access a list of aircraft/objects/users with unique IDs that they can assign any custom data to. This data will then be automatically propagated over the network and can be read by the same add-on running on each user's machine.

What this means is that JoinFS can be leaner and will be providing two essential things: a stable cross-platform network and smooth object updates, but have potentially an unlimited expansion of features provided by third party add-on developers.

I think this could be the best way forward for JoinFS.

Peter

Now that is a good idea.
You may have just provided me with a solution to something I was thinking about writing.

I'll keep you informed if I do it.

Hi Peter,

Any news about this very interesting possibility ?

Thanks