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.

Please turn the DebugMode on on the PLCSimAdvancedInterface and check the log (both console and unity).

Please also replace your PLCSimAdvancedCoupter against this one and send us what you see in the Console log: PLCSimAdvancedCoupler.zip

Can you send us your console log and tell us what is displayed in the interface status?

Hello, have you deleted something in the project. It seems that some scripts are missing. This may be related to wrong assembly definitions or maybe the scripts are really missing. The first thing you should try is to delete the library folder in the Unity project and restart Unity.

If something in the realvirtual.io folder was accidentally deleted or changed, you can try to simply import realvirtual.io back into your project. It is always recommended to make backups or use a revision management system such as PlasticSCM.

Hi, 

did you followed this:

https://doc.realvirtual.io/components-and-scripts/interfaces/plcsim-advanced#interface-configuration

Specially did you provided the path to your local Siemens.Simatic.Simulation.Runtime.Api.x86.dll and did you checked if you after starting the simulation find this dll in the streaming assets folder?

Best regards
Thomas

We recognize that despite the significant changes made in the last release to ensure the drive fixed update sequence for cams and gears, there is still a bug affecting functionality.

After investigation, we have identified the solution. To resolve this issue, please modify the Drive script by adding !issubdrive around line 880. This fix will also be included in our upcoming release.