Strange behaviour route after data exchange

Hello, I used the new data exchanger to transfer a route, gribfile and polar from a Windows 11 desktop to an Intel Macbook. The transfer worked flawlessly but the route on the Macbook behaves rather strange.
When time stepping through the transferred route, the boat leaves at the original time but not from the starting point but from the destination. It than follows the route in the opposite direction back to the starting point. Not back in time but progressing from the original arrival date. While doing that the line of the route is erased in the wake of the boat.
Regards, Ruud

There can be many reasons:
The boat not using the same polar, not having the same grib loaded, route starting from boat but boat is not at the same position, boat parameters and constraints not being the same, etc.
--Philippe

The POIs in the route are ordered by alphabetical order or by sequence number ?

Hello Philippe, 
the grib and polar are identical and the POI's on both computers are ordered by sequence. However your answer made me realize that I wrongly assumed that also the underlying routing parameters would be transferred. 
In this case my issue was probably caused by the starting date. After calculating the route on the original computer the starting time by default was assigned as 'fixed date'. However, without interfering, on the second computer 'from grib date' is used. After changing that both routes indeed behave identical. I still do not understand how 'starting from grib date' can let the boat go in the opposite direction. But it is more important that you made clear that data exchange is not automatically a mirror function.
Thanks for your immediate response and all your efforts...
Regards, Ruud

Normally the parameter concerning starting date should be transferred too, I will check and eventually fix that if it is not

And indeed there was a bug (an old one btw, not related to data exchanger). Thanks for finding this.