Log in or register to post comments

'Unity Pro license is required' with multiple plugins

December 9, 2014 - 12:53pm #1

Vuforia SDK Version: 3.0.9 -

Description with steps to reproduce:

We also encountered the 'Unity Pro license is required' in the Webcam-preview component inspector, while using Unity Pro, just like in this thread https://developer.vuforia.com/forum/issues-and-bugs/webcam-play-mode-issue-unity-4) but with a different cause.

I spent quite a bit of time trying to solve it by recreating the project, exporting and importing the assets, and etcetera, but every time the problem came back at some point.

Ultimately I was able to pinpoint it to a single moment: exactly after our own Windows plugin was added to the Plugins/x86 folder (possibly after re-opening Unity, I'm not sure if that was required), did the message appear.

In our own plugin we have also implemented the rendering callbacks. So the theory is that in the case of two plugins that implement these callbacks, Unity will only call them in one DLL. And if our DLL was picked, this means that the Vuforia DLL won't receive them anymore, and conclude from that that it is not running in a Pro edition of Unity.

So quite possibly this is an issue with Unity, not Vuforia (why would multiple rendering callbacks not be supported? I don't think there is a fundamental reason, although one would want to be able to schedule the order in which they are called). But I thought I'd mention it here. Also because perhaps not everyone will expect that a tracking-plugin would implement rendering functions (for image processing most likely).

Has anyone else encountered this? 

Perhaps we can solve it by calling LoadLibrary and GetProcAddress on the Vuforia DLL to bind the functions ourselves, and then call them when we receive the calls, thereby making everybody happy.. Of course this would only work if Unity consistently prioritizes our DLL over Vuforia's... 

On the device this is not a problem since single-threaded rendering can be selected there (on Android at least), and the callbacks aren't used. 

So hopefully we can get the workaround to work.. If anybody has any other ideas about this we'd love to hear about it!





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

Mobile OS and Version: N/A -

Mobile Device Manufacturer and Model name: N/A -

Do the Vuforia Sample Applications show the same behavior?: Yes, we tried it with the Background texture access sample and our own plugin.

Log in or register to post comments