I'm using the newest package of Vuforia for Unity and I'm trying to use it alongside NGUI. The problem is NGUI already has a UIButton, UIRect, and UILabel class which is conflicting with the new Vuforia UI Scripts. What's the easiest way to get rid of Vuforia's GUI scripts without breaking everything?
- Sort Posts
- 16 replies
- Last post
2.8.7 Namespace conflict with NGUI
2.8.7 Namespace conflict with NGUI
If you need to keep the scripts in, when the three namespace errors pop up in unity open the first script in Mono and right click on the name, i.e. UIButton and find all references and go through each script ending. then saving scripts.
Then backup and use for further projects so you don't have to go through the process again. Short term fix.
Agree though, the scripts can be taken out and project can be built up manually.
2.8.7 Namespace conflict with NGUI
+1
Or even better, why not take out the UI stuff all together? Seems those elements are causing the trouble, while (as mentioned before) NGUI is pretty much becoming the standard for UIs.
Or maybe post a way to disable/strip down the SceneManager/AppManager to just detect inputs?
I do have a project which contains a previous example of the video texture, without the UI hoopla (just PlaybackBehaviour and Controller), which worked fine.
2.8.7 Namespace conflict with NGUI
Same here. This issue is causing a lot of extra script editing, trial and error in some cases. The bug in previous versions of Vuforia for Android platforms means that the latest version of Vuforia is the only version available to use, unless there's access to a previous and stable version. Using the most up to date SDK and NGUI is a nightmare.
2.8.7 Namespace conflict with NGUI
Hi,
Has there been any developments regarding this issue?
Noted that on the Playmaker forum one of the developers will be looking at a solution to a connected issue.
http://hutonggames.com/playmakerforum/index.php?topic=5817.msg28943#msg28943
Thanks
2.8.7 Namespace conflict with NGUI
2.8.7 Namespace conflict with NGUI
2.8.7 Namespace conflict with NGUI
Please fix this. NGUI is a veyr popular UI solution, and you have chosen naming conventions which conflict with NGUI's. Anyone who updates to the latest Vuforia will get stung with loads of errors, which are a nightmare to fix. Please fix this ASAP and release a new build.
yes,
or you can just get rid of the sample UI stuff completely and create your own project with the Vuforia prefabs (not the samples); for example, a simple Imge target project can be setup by starting with a fresh new project and:
- drag ARCamera prefab into your scene
- remove MainCamera
- drag an Image Target prefab into the scene
- import Datasets, configure ARCamera and targets
- add augmention object to each Image target
etc.
see the developer guide for details about using Vuforia in Unity.