hi VM101, and maybe a bit late ( i do a fg break between each winter and just started recently to see what i missed in the fg world
)
to avoid the jitter problem and the need for one fg session for each copter, plus a mp server to set up, the best solution is to have the quadcopters as mpplanes in one single fg session, the difficulty is in the way to do it.
i see 3 ways:
-one is to have simulink send the copters position as mp paquet, the wiki page seems quite acurate for this and you can try to contact Richard who worked on the recent mp protocol code for pointers.
the minimum to send are:
timestamp
position
orientation
a different callsign for each copter
other mandatory fields can be zeroed
- or you can make a piece of code who read the net_fdm udp paquets sent by simukink and convert them to mp protocol, and run it between simulink and fg.
- last, make fg read net_fdm paqets, and create mp plane with this. i don't know if a call sign is included in the net_fdm protocol, or if each copter need a different port ?
if the timestamps are in sync between the differents copters, there's a way to display them in sync in a fg session ( a git fg personnal branch WIP not ready for a real mp world, but the current code should be fine displaying the copters in sync, based on the timestamps provided. we did some try with zero lag last winter and that was good ! )
the velocity, rotationnal velocity and accelerations are only mandatory if you need a realtime display in FG, where they are used to predict the plane position a bit ahead of time, but if it's just to display the result, we don't need them as we interpolate between latest received positions.
maybe other can come up with different solutions?