Hello Vuforia Developers,
How to Upgrade/Install to Vuforia Engine 8.6 SDK
With Vuforia Engine 8.6 SDK, we've made some changes to our upgrade/install Path.
Please check out following article for more info: https://library.vuforia.com/content/vuforia-library/en/articles/Solution/vuforia-engine-package-hosting-for-unity.html
Vuforia Engine Support
New Release 8.5 Patch (8.5.9) and samples (8.5.10) are available!
Today we’re launching a patch to the Vuforia Engine 8.5 Unity Extension (8.5.9) to include a fix for a linker error seen in Xcode when building Vuforia Engine iOS apps with Unity 2019.3 beta 8 and later. The new version will be made available via Unity’s package manager.
Known issue: iOS build failures with Vuforia Engine 8.5.8 & Unity 2019.3 beta
We are aware of iOS build failures occurring when using Vuforia Engine 8.5.8 and the latest Unity Editor 2019.3 beta, and we are actively working on resolving the issue with a patch release.
In the meantime, please follow these steps to work around the issue:
Known issue: Package Manager upgrade to Engine 8.3.9 is incorrect
Unity has informed us that due to a Package Manager issue, the 8.3.8 version of Vuforia Engine was incorrectly listed in Package Manager as 8.3.9.
There is currently no 8.3.9 version of the Vuforia Engine SDK, so this is a false notification.
Apologies for any inconvenience.
Vuforia Engine Support
Suggested workaround when accessing Unity materials interferes with background texture updates
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?)
2018.3.14f1 - Crashes out of nowhere
Since a few weeks 2 of our testing devices started crashing on one of our apps when opening the app. At first it started happening on my personal device, it would just crash. Last week it started happening on another testing device. So far only Android devices.
We narrowed it down to when Vuforia initializes at VuforiaRuntime.Instance.InitVuforia().
We're using ARCore & Vuforia together, but previously this was not an issue. It also crashes when we disable ARCore.
Vuforia is updated to latest version
Are you sure you want to delete this message?
Are you sure you want to delete this conversation?