It seems the issue is that the part is being gripped by two components, which is something we currently don't support. Typically, we use a combination of a Fixer (for the passive part) and a Gripper (for the active part). In the coming days, I'll be creating a test model to explore whether we can extend the functionality of the Gripper to address this.

We wanted to let you know that we won't be upgrading because Cadenas has announced the end of support for the technology we are currently using. Instead, we recommend using 3Dfindit, where you can find a wide range of 3D components online. This platform allows you to export components as OBJ or Collada files, making it a versatile alternative.

Issue is solved with newest 2022.16 release. Please use 2022.16 Professional and 2022.16 Simulation together. On Problems when updating please also consider this:

https://doc.realvirtual.io/advanced-topics/troubleshooting

I think you are talking about the mail yesterday evening. We are working in the European Timezone. I expect that we can fix all issues and release 2022.16 today.

Did you followed this:

https://doc.realvirtual.io/advanced-topics/troubleshooting

You need to implement your own move script based on mousedown and drag events. we will add it to the todo list for the next releases.

You need to develop your own interface based on this information:
https://doc.realvirtual.io/components-and-scripts/custom-interfaces

Question was (translated by Deepl): 
In some projects, Party A is not allowed to access the PLC directly using the signal acquisition tool, but accesses the WEBAPI interface through Party A's device management platform. Is there a convenient way to make this connection in realvirtual.io?

You would need to implement a custom interface based on the WebApi specification