Hi Leve,

I assume that you are having PLCInputs and PLCOutputs in your project after importing from TwinCAT:

Now you can write to the PLCInput with 

PLCInput.Value = YourValue;

You should write your own behavior scripts and attach this to the Gameobject with the rigid-body where you want to measure the velocity.

Here is a simple example of a behavior script (it is the Sensor_standard script from the Game4Auomation Framework).

This script is sending a "High" to the PLC when the sensor is occupied.

namespace game4automation
{
    [RequireComponent(typeof(Sensor))]
    //! The Sensor_Standard component is providing the Sensor behavior and connection to the PLC inputs and outputs.
    public class Sensor_Standard : BehaviorInterface
    {
       
        [Header("Settings")] public bool NormallyClosed = false;  //!< Defines if sensor signal is *true* if occupied (*NormallyClosed=false*) of if signal is *false* if occupied (*NormallyClosed=true*)
        [Header("Interface Connection")] public PLCInputBool Occupied; //! Boolean PLC input for the Sensor signal.

        private Sensor Sensor;
        private bool _isOccupiedNotNull;

        // Use this for initialization
        void Start()
        {
            _isOccupiedNotNull = Occupied != null;
            Sensor = GetComponent<Sensor>();
        }

        // Update is called once per frame
        void Update()
        {
            bool occupied = false;
        
            // Set Behavior Outputs
            if (NormallyClosed)
            {
                occupied = !Sensor.Occupied;
            }
            else
            {
                occupied = Sensor.Occupied;
            }

            // Set external PLC Outputs
            if (_isOccupiedNotNull)
                Occupied.Value = occupied;

        }
    }
}    

For anyone experiencing similar issues.

Problem was that the compile settings were not set correctly:

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

, that collision layers were not set correctly:

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

and that Prostprocessing was not included in the Assembly Definitions:

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

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

Hi,

we don't know this error. Could you upload your project? I will send you via email a link for uploading.

Hi,

usually it should also work with 2019. But we recommend to use LTS (Long Term Stable) releases because Unity is sometimes changing to fast for industrial use cases. We develop and test in 2018.4. On our build server we also try to compile and build with 2019, but it is more risky that we miss something in 2019. So I would recommend to only use 2019 if you really need it.

I just checked latest release and 2019 and it works on my computer without problems. The main menu is available and the demo model is working as expected.

You should also check that you are using .Net4. compatibility level - even if this should be not an issue with the main menu. But some interfaces might not compile without .Net40

There seems to be an issue / collision with anything what is already in your 2019 project. I don't know what. Could you please check the Console log for some more information.

Hi,

the license is tied to the organization who purchased the Asset. There seems to be no official way to transfer a license to another organization (e.g. from school to you personal) if you purchased on the Unity Asset Store.

You could purchase the license directly from us. For doing so please just fill out this form (Button "Request a quote" and you will get an offer: https://game4automation.com/en/buy

We could allow you the transfer if needed later on based on a simple mail you are sending to us.

Best regards

Thomas

Hi, 

you need to change this line (left = old, right = new) in the Drive script:

It will be changed in Release 1.024 (Build 246 and upwards).

For customers who wish a Beta download - please send us your Invoice Number and we can send you a download link!

You seem to be in editor view. The UI can be disabled by 

- deleting everything under game4automation (what will delete totally the UI out of the project)

- or by deselecting the Layer

In Game mode you can deactivate the full UI deselecting this option:

Hi, 

first of all I strongly recommend to use Unity 2018.4 instead of 2019. Specially when compiling to the Build with an IL2CPP compiler there might be issues with Unity 2019.

There is something interfering with the demo use cases (need still to check what exactly). 

Please follow these steps:

- Make sure that the compiler defines are set to GAME4AUTOMATION; GAME4AUTOMATION_PROFESSIONAL 

Import while running the OPCUA server the nodes again. If you have enabled with the Compiler defines the full framework it will also create all PLCInputs and Outputs:

If you try now to run it you will get errors:

These errors are because the demo server is limited in subscriptions.

You need to turn off all subscriptions in the OPCUA nodes or you turn it off in the OPCUA interface and import again:

Please also delete the Use Cases completely (we will get rid of the problem with the use cases in the next release).

Now it should work as expected:

You find also the full working model (based on Unity2018.4) in the Uploadfoalder I have send you via mail.

Hi Dat,

I uploaded Version 1.020 to Unity's Asset Store. This should fix the problems. You can now use pure .Net4.0 projects. Also CADLink is now able to compile wit .Net4.0 settings.

It will be availabe latest on Monday on the store.

Thomas