Log in or register to post comments

Where is this guide???

April 30, 2015 - 3:31am #1

https://developer.vuforia.com/forum/ios/ios-8-video-playback-frame-rate

Each time I tap on this link I either get to the KB menu and this guide is not present or I get directed to my account profile?

Help???

Where is this guide???

May 1, 2015 - 12:03am #5

Thanks, looks like my projects are well and truly stuffed...I now find it is actually using 3.0.9!!!  How I do not know...but down to me obvioulsy.

 

I starting afresh with 4.0.105 and Unity 5 ..... DOH!

 

Thanks

Where is this guide???

April 30, 2015 - 3:03pm #4

In each of the Unity sample apps, there's a license_3rdpartynotice file which mentions the SDK version. For troubleshooting purposes you should try to isolate a single issue at a time using one of our sample apps. Please provide specific details in accordance with this guide:

https://developer.vuforia.com/forum/device-support/how-report-device-issue

You can also check our SDK and Samples release notes for info about what has been fixed:

https://developer.vuforia.com/library/articles/Release_Notes/Vuforia-40-SDK-Release-Notes

https://developer.vuforia.com/library/articles/Release_Notes/Vuforia-40-Sample-Release-Notes
 

Where is this guide???

April 30, 2015 - 2:18pm #3

I'm using Unity 4.6.2 with either 4.0.103 or 4.0.105 and have the following problems....

1. Is there a way to identify which version of Vuforia is imported in my project?

2. I am finding dependant on what I'm using Vuforia for I'm having to use Unity 4.6.2, 4.6.4 or 5.0 as some things that worked in one does not in other from:

    quarter sized camera, Unity UI not appearing (I thing in 4.6.3 and 4.6.4 the UI fails to appear but open in 4.6.2 it all works well?)

3. I am having the video playback lag but know I am using either 4.0.103 or 4.0.105

4. when the video from fullscreen returns to AR view the screen appears black with no camera view

 

????

 

Where is this guide???

April 30, 2015 - 9:23am #2

The issue described in that post has been fixed in 4.0.103 and the workaround is no longer necessary.

Log in or register to post comments