VisualScripting does not work because of a deprecation

Unity Engine
, , , , ,
1

Hi,
when starting to use visual scripting I only get back a couple of warnings and "Inspectors are disabled when plugin versions are mismatched to prevent data corruption.

Digging deeper I have a better explanation with:
Assets/Unity.VisualScripting.Generated/VisualScripting.Core/Property Providers/PropertyProvider_UnityEngine_XR_Interaction_Toolkit_AffordanceSystem_Theme_Primitives_Vector2AffordanceThemeDatumProperty.cs(15,76): warning CS0618: ‘Vector2AffordanceThemeDatumProperty’ is obsolete: ‘The Affordance System namespace and all associated classes have been deprecated. The existing affordance system will be moved, replaced and updated with a new interaction feedback system in a future version of XRI.’

And some more like this. Now, I’m clear I need to switch off the affordance - whatever - classes. But HOW?

Everything worked well in the tutorials with version 2022.3.7f1. But when doing my own stuff suddenly went wrong. I updated to 2022.3.43f1 -same issue.
Anybody knows how to stop this?

Thanks for any help,
Benny

2

Once you updated Unity, did you check to see if there are any updates available for the visual scripting package?

3

Yes, I did. And there was one. But updating did not help.

I now run Visual Scripting 1.9.4 (which comes with the latest 2022.3 anyways), but when trouble started I had 1.9.2 and updated - which killed my whole project…

Thanks for the fast help anyways!

4

You’ll want to delete your generated visual scripting project files, then regenerate them in Project Settings > Visual Scripting.

5

Yes, that I found already. Unfortunately does not help. Even in a new project without any visual scripts the error appears.

regards,
Benny

6

While not directly related, I have a ticket related to Visual Scripting requiring an update with the package in order to fix it.

I’m using 2022.3.40f + Visual Scripting 1.9.4

The issues started when I upgraded from an earlier 2022.3 ~ version.

Previously, I spent 2 years using VisualScripting, so it seems there is an internal incompatibility at the moment with 1.9.4?

7

Looks to me like that could be the case.
How did you solve that? Could you just go back to an earlier version? Because I think that was not possible for me. If you say so I’ll try again.

8

In my case, I submitted my project as a bug report. They stripped it down and confirmed it as a bug in their issue tracker. You can try that for the greater good, if you can show that it generates errors.

Beyond that, it would require trickery to stop the generation of my erroneous entries.

9

Thanks, I’ll do that.