|
From: www2 <ww...@wo...> - 2023-06-12 09:14:28
|
James Thanks for the update This is some thing that need to be fix. An other issue that i see that will be fix in the network code (TCP) is that is no bi direction communication possible with custom protocols ($FGROOT/Protocol/*.xml) Jean-Paul Anceaux (www2) Op 12-06-2023 om 11:00 schreef James Turner: > > >> On 12 Jun 2023, at 09:25, www2 <ww...@wo...> wrote: >> >> I like to get lat, lon, and alt and roll, yaw, and pitch data. >> Current testing with some boilerplate code for interacting over >> websocets[1] and i use /sim/time/gmt as my test path in the prop tree. >> But i expect that /sim/time/gmt update 1 a second but some time have no >> update for a few seconds. > > For getting that primary data effectively, you can also consider the > ‘native’ or netFDM protocols which are lower level (UDP, binary etc) > depending on your use case. Web-sockets are also okay for this but to > work efficiently they do need listeners to being work on the properties > you want to send. > > The problem with /sim/time/gmt is it’a tied property, so a listener on > it won’t fire. However, that seems like a thing we could and should > probably fix :) > > If you test with /position/longitude-deg or similar I think it will just > work as you want. > > Kind regards, > James > > > > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flightgear-devel |