Bug: node issues with Unity 2018.3.0 and higher

[janetweber]

There is a problem with input and output types with unity 2018.3 or higher. I have only noticed this with the extract vector 3 and vector 4 nodes.

Attachments:

You must be logged in to view attached files.

[crazyasian]

I found out this is because Unity switched to .Net 4.x starting at version 2018.3.0. I had to switch it back to .Net 3.5 to get the Extract node working properly again. You can see instructions here: https://docs.unity3d.com/Manual/ScriptingRuntimeUpgrade.html

Edit => Project Settings => Player => Scripting Runtime Version – change that to .NET 3.5.

I attached the pic from the Unity website.

Attachments:

You must be logged in to view attached files.

[Gavalakis]

Hello and sorry for the late reply.
I can confirm that there is this issue when using this specific combination:
Scripting Runtime Version: .NET 4.x Equivalent
API Compatibility Level: .NET Standard 2.0

If however the “API Compatibility Level” is set to “.NET 4.x”, or like @crazyasian stated, the “Scripting Runtime Version” is set to “.Net 3.5”, there is no such issue. With that said, using API Compatibility Level “.Net 4.x”, instead of “.NET Standard 2.0” when using “.Net 4.x Equivalent”, is highly recommended right not for performance reasons, although this is something I need to look into.

Thanks!

Join us on Discord: https://discord.gg/97q2Rjh

[Author]

Posts