Okay. That does seem to confirm that the system assumes UDP blocks are "dispensable", that if there's a clash the UDP block is lost and not re-sent. With TCP and SPX, if there's a timing clash anywhere I think the block is re-sent. The sender "cares" about the block getting there, but not with UDP.
That is a good solution then,
Do you notice if things are smoother, or about the same as with TCP or SPX? I think my PM gauges look smoother (so the block timing is better, less latency from the replies confirming receipt presumably), but it is very subjective. As with FS's own "smoothness", the frame rates are no measure for this -- WideServer regulates the frame rates to match FS in any case. The only time they will appear to exceed the FS rates is when the data from one frame needs to be split into more than one block to keep within protocol and buffer limits.
Regards,
Pete
Hi Pete,
Yes.
I wrote down the PM-Frames, Datarates and FS-Frames (Read over PM "F" on all PC`s) before I made any changes (WideFS 6.51) and after installing the WideFS 6.596/8.
With 6.51:
Frames = 78-90
DataRate = 22-31
FS-Frames = 21-29
With WideFS 6.596/8:
Frames = 80-92
DataRate = 40-44
FS-Frames = 34-44
This both test I made under the same conditions, saved situation on same Airport with same plane and weather, all the same .
And I can reproduce it.
When I fly the PFD/ND and PFD/ND (FO) are smoother, also the other PC`s.
I made yesterday night a flight, more than 1 hour, and NO "block sequence errors" or anything else.
In Log`s only the beginning with programstarts and when I closed the Ends, nothing more.
Great, as ever.
Thanks Pete