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

It looks like the issue you're encountering might be due to using realvirtual.io Professional 2022.15 with Simulation 2022.13. To resolve this, please revert to using both Professional 2022.13 and Simulation 2022.13 together.

We're currently working on upgrading both to version 2022.16, which should be available next week. If you need a hotfix in the meantime (a beta version of Simulation 2022.16 and Professional 2022.16), please email us at info@realvirtual.io.

Thank you for your patience!

Best regards, Thomas

If you encounter issues, follow these steps to resolve them while keeping references to realvirtual.io components in your user scenes:

1. Close Unity.
2. Delete the Library folder in your project directory. This action clears cached data and forces Unity to rebuild the project.
3. Restart Unity. Unity will regenerate necessary files from scratch.
4. If the problem persists, close Unity again.
5. Delete the entire realvirtual folder from your project. This action removes all realvirtual.io assets and configurations.
6. Open Unity again. Unity will load without the removed assets, but your scene references should remain intact.
7. Re-import the realvirtual.io Asset. This step ensures that all components are restored, and references in your scenes to realvirtual.io components are preserved.

These steps should help resolve most issues while maintaining the integrity of your references to realvirtual.io components in your user scenes.