Your comments

Hi Pablo,

thanks - I will send you a beta today or tomorrow. Maybe you can check with the beta if the problem still occurs. 

Best regards

Thomas

Hi, 

FMI could be the future standard for behavioral model exchange, but currently it seems that you can't get FMUs of any component from the OEMs. And I'm pretty sure that you can't export FMUs from Simit, for example, and that Siemens doesn't provide FMUs for their own drives (Siemens is interested in selling Simit, not replacing it ;-)). Currently I would not rely on FMUs to replace own behavior models. Unfortunately, I don't see an industry accepted standard being available anytime soon. If you are a Simit user and have your own behavior models, then you can continue to use them and Simit along with Game4Automation.

I hope this helps, even though it may not be the answer I was hoping for.

Best regards

Thomas

Hi, I am in vacation until this Thursday. I think it will be best to look first into your project and to check. You can send us your NDA to info@game4automation.com and I can sign on Thursday morning.

Best regards

Thomas

Hi, you are deploying to which destination platform. Which version of G4AProf are you using. Can you share your project so that we are able to check?

Please try both - latest OPCUA4Unity and the version before. We replaced the full OPCUA basis library in latest release.

The colliders of the MU are not defined as they should. You can compare with the MUs in the Demo scene.

You need to have at least one box collider on an MU which is on the layer g4a_MU (see my sceenshot). This layer is working for transport collissions as well as sensor collissions.

Please also check:

https://game4automation.com/documentation/current/physics.html

The example MU in the demo scene is even more complicated. It has two colliders - one for the transport (like realistic rolling on the bottom - on the layer g4a_TransportMU) and one for the sensor on the layer g4a_SensorMU.

Hi, I would recommend Visual Studio 2019 - which is usually used. I have seen some customers using Code but I would not recommend it, because there might be some limitations. We are using Rider for development which is also very good with Unity but Rider is not for free. 

If you have problems in using Visual Studio 2019 this is a general Unity or Visual Studio installation or setup problem.

Please follow this guide:

https://docs.microsoft.com/en-us/visualstudio/gamedev/unity/get-started/getting-started-with-visual-studio-tools-for-unity?pivots=windows

We found the issue. Automatic install script had a bug. Is fixed in the latest release.

Hard to say - please compare the source settings with the demo model or send us your model and we will check what is wrong.