In the 0.6.0 release when not syncing to the OBS main render thread there could still be situations where frames are processed by receivers in the wrong order. Some progress has been already made in this area, but it's not part of a release yet. The FrameBuffer.cs source code has extensive comments explaining the situation in more detail and the current state of the implementation.
[x] Reorder frames if received in wrong order
[x] Compensate frames received delayed due to network lags
[x] Support sender and receiver having different frame rates
Releases after 0.6.0 include the partial fixes so the situation should be improved already. What stays is what is described in the comments linked above.
In the 0.6.0 release when not syncing to the OBS main render thread there could still be situations where frames are processed by receivers in the wrong order. Some progress has been already made in this area, but it's not part of a release yet. The FrameBuffer.cs source code has extensive comments explaining the situation in more detail and the current state of the implementation.