You should check our drives and transport surfaces in the demo model. There you could see how it must be setup. Basically each transport surface needs a drive at the same level or at any level above. Please check that the drives have a reference to the transportsurface. Usually this is set automatically:

Is fixed in latest release.

I am answering in English - this might help also international customers.

I think there is missing a drive on the same gameobject or at a level above the TransportSurface or maybe the connection is lost. You should check if there is a drive and if it is linked to the TransportSurface.

The box is falling down because something is wrong with the colliders. The box should be on the Layer MU and the Surface on the Layer Transport.

As I see you are using game4automation 2021. It might make sense to use realvirtual 2022 because there are big improvements in TransportSurfaces by the GuidedTransport function:

https://doc.realvirtual.io/components-and-scripts/motion/guided-transport

You can also check this tutorial about guided transport:

We changed and adopted all compile switches and Settings to Unity Editor on Linux. It will be in a few hours as a patch on the Unity Asset store. Please note, that SpaceNavigator, some special Interfaces (like SHM based for Simit) and CAD Step Import won't be available on Linux.

Yes I understand but the used Library gives us no direct information about disconnection events. And I don't know exactly in your case who is closing the communication when nothing happens - is it the client or the server. I am closing this issue because for the moment we don't have a better solution.

Uder which system is your Unity editor running?

The interface is only able to detect a disconnection if

StatusCode.BadConnectionClosed

is given back on a read value.

It might be a good idea to read one value in a periodical way and to test if the connection breaks in this situation.