Your comments
G4A itself for sure not duplicates classes. Currently I don't know why this happens. Please delete the duplicated classes.
Hi Dat, I just checked. Objects wich are colliding with the Sensor must alway have the MU script on the same or in a level above the collider. This is the planned behaviour. I don't know in what combinatione exactly your problem comes up. Can you send me a simple example?
Hi Martin,
I will check to replace my Newtonsoft.Json against the Newtonsoft.Json you proposed.
I did not tested with the Hololens emulator. All I know currently is, that it seems that the connect must be done for Hololens in a parallel thread because the connect in the main thread will stop the Hololens to work. I am not having any more an Hololens to test but I have an intermediate solution for a connect in a parallel thread.
I could imagine to give you my current beta unprotected and you can check it with your Hololens. But we would need to have some kind of agreement. Are you interested? If yes we should talk via phone. You should have my phone number.
Best regards
Thomas
Hi Dat, will need to check that. Most probably I will get back to you tomorrow!
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
Problem was solved by deleting Parts4Cad and Zip in Tools. Included ZIP is not compatible with UWP. We will change that in future.
Hi Oliver,
can you send your log file?
You can find it here:
|
Thanks
Thomas
Customer support service by UserEcho
Hello,
writing to DBs is described here and it should be possible what you like to do:
https://game4automation.com/documentation/current/s7tcpip.html#Reading-and-Writing-DBs
I think it should be DB43.DBX145.0