Your comments

Solution was to remove GAME4AUTOMATION_PROFESSIONAL from the compiler defines. We will investigate why sometimes these defines are set - even if you just have got Starter.

First of all please check all these steps described here:

https://forum.game4automation.com/de/knowledge-bases/2/articles/193-step-by-step-guide-if-you-have-problems


Maybe there are errors which prevent the g4a scripts to be compiled. If yes please check the console log and send it to us if the message is not helping you.

Are you using Professional. Please check your Scripting Define Symbols as described here:

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

If you are using Starter GAME4AUTOMATION_PROFESSIONAL should not be in the compiler defines.

On which platform are you working. Please try deleting the full path

Assets/game4automation/private/RuntimeUI/SpaceNavigator

Good morning,

I think this fits well vor Game4Automation. What do you mean with basic (369€) per year?

You need Unity Professional (about 150€ a month) and Game4Automation Professional (700€ for one license). You can import Inventor CAD data by exporting and importing them via STEP data format.

For the Rasperry PI what kind of a module are you looking for. We have implemented several industrial communication protocolls and if RasperrryPI is talking one of these protocolls communication with Game4Automation Signals would be also. Our source code is open so you could also implement your own custom interface to a rasperry pi.

You can also check our new FAQ if you have more questions:

https://game4automation.com/en/


Best regards

Thomas

HI

Hi, you seem to have errors in your project but I can`t see which errors. Based on the latest review on the Unity asset store (which might be from you) you might have multiple identic dlls in your project. This is normally if you are using multiple assets which are using the same dlls. You need to delete on of these duplicated dlls because they are only allowed to be once inside. O

We will check why this still happens - we need to look for a more robust solution in setting the correct compile settings while first installing the asset.

Hi, OPCUA is by itself a very slow connection. It has much communication overhead and the S7 OPCUA server is also as far as I know limited to 100ms cycle time. If you need fast update rates you should use S7 TCP, this is much faster. So OPCUA is mainly usefull for HMI stuff but not for fast sensor and axis data.