So I updated Vuforia 7-5-20
Now I cant reference my scripts because my singletons and monobehaviours both scream in the console that "The name `SomeManager' does not exist in the current context. When it previously did and works everywhere else. Just not in the DefaultTrackableEventHandler.cs script. I am doing some custom stuff to only show the Renderer if something in one of those scripts is set to something. I have no set name spaces at all. Even if I do something like below it tells me I need a reference.
public SomeManager someManager; <--- says the namespace doesn't exist and its a monobehaviour with that name.
Does anyone know why this is happening since updating Vuforia?
I've seen the note above about known issues but I am on the latest version and it is still doing it.
I have just encountered the exact same issue. I don't understand why do we have to roll back Vuforia??
I am using Unity 2019.2.10f1 and Vuforia 8.5.9
Why haven't this been fixed? What prohibits the developer team from fixing this?
In general, I have found that Vuforia / Unity are very sensitive in terms of which versions are being used together.
I would like to know, @Medabit , how do we in fact map the SDK version to the Unity version? Is there a list of which versions are most compatible?
Edit: same issue with Vuforia 8.5.8; 8.3.9; 8.1.12 in Unity 2019.2.10f1;
same with Vuforia 8.5.9 in Unity 2019.3.0b10; Vuforia 8.3.9 in Unity 2019.1.14f1
What's going on? What if I don't want to / cannot downgrade my Unity version?