Log in or register to post comments

Qualcomm Vuforia conflict with Unity 4.6

October 28, 2014 - 3:37pm #1

Vuforia SDK Version: 3.0.9 -

Description with steps to reproduce:


We are trying to use Vuforia with our latest Unity project but have encountered a conflict with the Image class in your Qualcomm.Vuforia.UnityExtensions.dll and a new class called Image in the UnityEngine.UI package. I believe the Vuforia solution would work if Image in your DLL was namespaced. Would this be possible to do in a short amount of time? Are there updates planned for the library to support Unity 4.6?
Alexander Cooney
Filament Games LLC


Development OS (Mac OS X, Windows, Linux): Windows -

Mobile OS and Version: Android OS -

Mobile Device Manufacturer and Model name: Ipad Air, Nexus -

Do the Vuforia Sample Applications show the same behavior?:

Qualcomm Vuforia conflict with Unity 4.6

January 6, 2015 - 9:56am #5



That's great to hear! Thanks for the update, and the link.


Best Regards,


Qualcomm Vuforia conflict with Unity 4.6

January 6, 2015 - 9:49am #4

Hi Worfram,

your suggestion has been taken into consideration already, 

and in fact, Vuforia 4.0 (currently available in "beta" version), has introduced the "Vuforia" namespace for all its Unity / C# classes.

If you're interested to upgrade to 4.0, you may want to download Vuforia 4.0 beta at:



Qualcomm Vuforia conflict with Unity 4.6

January 6, 2015 - 9:38am #3



By now, Unity 4.6.1 is official, and while your suggested workaround of prepending every occurance of Image with UnityEngine.UI does prevent the compile errors, this is a very tedious and error-prone method, especially if you include many external packages from the AssetStore


It would be much more convenient (and best-programming-practice) to move your Image class away from the global namespace into your own, or at least rename it to something less ambiguous (such as QCARImage or similar).


Thank you very much for considering this change!

Best Regards,

Wolfram Kresse





Qualcomm Vuforia conflict with Unity 4.6

November 3, 2014 - 12:39pm #2


note that Unity 4.6 is still in Beta at present.

However, have you tried accessing the UnityEngine.UI element by prepending the UnityEngine.UI namespace prefix to the class name (i.e. using the fully qualified class name) ? This should avoid the name conflict.

(as a similar example, non-Vuforia related, UnityEngine.Object may conflict with System.Object, which is solved by prenpending the namespace prefix)



Log in or register to post comments