Vuforia Engine requires a specific setup for the material and its textures in order to ensure that the video background is rendered correctly each frame. Our workaround solution is to not directly use the VB material (which create a new instance), but create a new material and reference textures from a reference to the first one (i.e. sharedMaterial). Our example creates a shallow copy and does all the necessary setup required for rendering the camera feed.
Workaround: Compiler errors with Unity 2018.4
With Unity 2018.4 LTS, you might see compiler errors like below when using Vuforia:
Assets\Vuforia\Scripts\Internal\RuntimeOpenSourceInitializer.cs(61,63): error CS0234: The type or namespace name 'ScriptableRenderContext' does not exist in the namespace 'UnityEngine.Rendering' (are you missing an assembly reference?)
This can be easily resolved by opening that script, and change all occurrences of
Known issues with Unity 2019.1
We are aware of the following known issues with Unity 2019.1. These issues have not been observed with Unity 2018.4, so if you're impacted we recommend to stay with that version.
Issues seen with Unity 2019.1.x with Vuforia Engine 8.1.X and 8.3.X:
Known Issue: Package Errors when importing Vuforia Samples into Unity 2019.1 from Asset Store
Update: this has been fixed in Unity 2019.1.4f1
We are currently looking into a known issue where errors like the following are displayed after importing a Vuforia sample from the Asset Store into Unity 2019.1: Library/PackageCachefirstname.lastname@example.org/Editor/Sources/UI/PackageDetails.cs(5,32): error CS0234: The type or namespace name 'UIElements' does not exist in the namespace 'UnityEngine.Experimental' (are you missing an assembly reference?)
Known issue after importing Vuforia samples on 2018.1 & 2018.2
Recently, Vuforia released 7.2 SDK with updated samples to the Unity Asset Store. These samples are not compatible with the 7.1 SDK, which is already packaged with most (if not all) of the current versions of the 2018.1 and 2018.2 Unity Editor.
The most common Vuforia error message observed is the following: "The type or namespace name `FusionProviderType' could not be found. Are you missing an assembly reference?"
Updating Vuforia Version when using Unity Hub
The steps for patching the Vuforia version in Unity 2018.1 when it is installed via the Unity Hub is a bit more involved when on a Mac. The follow instructions are meant to guide you through this upgrade process.
Note: These steps are for Mac. Updating on Windows can be done by running the Vuforia upgrade package and selecting the version of Unity within the Hub directory which can be found in C:/Program Files/Unity/Hub/Editor/<your version>
Unity Sticky Archive
An archive of sticky topics as posted by Vuforia moderators.
Note that some links and topics may have been moved, or are no longer available. If this is the case, we apologize for the inconvenience and suggest that you search the forums to find an answer to your questions.
Workaround for iOS Apps failing review
Attached is Vuforia’s version of the app-level fix scripts provided by @adrianj (many thanks!) in the following forum thread. This can be used immediately with SDK 6.5 (Unity 2017.2), SDK 7.0 (Unity 2017.3) and SDK 7.1 (Unity 2018.1).
Here are the recommended steps for installing and enabling:
Load dataset from Android split binary (obb)
A previous thread has described a few different approaches to handling an Android app that exceeds 100mb in size: https://developer.vuforia.com/forum/faq/unity-how-can-i-handle-large-android-apps
This thread will provide a small example of how to load a dataset from the obb file when using the split binary option.
Are you sure you want to delete this message?
Are you sure you want to delete this conversation?