Hello Pablo,

G4A is fully compatible with more or less all VR/AR solutions you can find for Unity.

you should follow the Occulus Documentation:

https://developer.oculus.com/documentation/unity/book-unity-dg/

Or you could use Steam - the advantage with Steam is that it works with most VR headsets on the market:

https://valvesoftware.github.io/steamvr_unity_plugin/articles/Quickstart.html

At the end, you need to integrate with all that VR Applications some standard Assets in your project and in your scene some standard components like VR Camera, Teleport and so on. You will need to deactivate or delete the G4A Camera because camera movement will be replaced by the VR application.

Maybe I will do soon an official tutorial about that. But if you follow the VR documentations and tutorials on the web you should be able to do that.

And sorry, did not notice, the forum is now also in English...

Best regards

Thomas

I don't know exactly how you would like to align the objects. But playing around with the Align Object and the rotation of the geometry in your Chain Element should do the job. Please check the video:

QbVAbcVI4D.mp4

Sorry we can't tell you what is wrong based on this rough information. It could be your Unity Configuration or the OPC Server configuration .....

To be able to check it we would need an example based on an OPCServer we can test with.

Please try to rebuild your problem based on UaCPP C++ Demo server (will send you a download link for this test server in a private message later).

Please upload your project where you can reproduce your problem based on UaCPP Demo server here:  https://game4automation.com/send 

yes for sure. Each PLC must have a different IP address. Numbers of interfaces in one scene is not limited.

There are on Github MQTT Libraries for .Net available you could use with Unity.

On our side MQTT is planned but so far not with very high priority because MQTT is not much used on PLCs.

Nein leider nicht. Es gibt mehrere möglichkeiten einen Roboter bewegen zu lassen. Die beste ist eine externe Inverse Kinematik zu verwenden (RoboDK, ABBRobotStudio....) in der man die Roboterpositionen an einer Robotersteuerung teacht. Der Roboter in Unity ist dann mit den einzelnen Achsen der Robotersteuerung verbunden.

In Game4Automation selbst ist keine Inverse Kinematik enthalten. Hier kann man nur die einzelnen Achsen verfahren was relativ mühsam ist. Im Demomodell haben wir das so gemacht un in einer Unity-Animation die einzelnen Achspositionen festgelegt.

You will need to set the Values "PlaceObjects" or the corresponding values to true to loose the can. If you use PickBasedOnCylinder this can be controlled by a connected cylinder. So the Can should fall down whenever you open the Cylinder.

The focus in our research project changed, AML is not needed any more, so an official AutomationML interface is not planned any more. In general I am missing very much the availability of AML exporters for common CAD systems. As soon we see, that there affordable standard exporters available (besides the very special solutions for automotive) we will change our mind. But you are free to develop your own importer - it should be not to much work because reading in XML and Collada into Unity should be very easy.