Log in or register to post comments

Issue Migrating to 2017.2.0f2

October 9, 2017 - 10:59am #1

I've been having a lot of troubling migrating an existing project into the new versions of Unity with Vuforia built in. At first I was in 2017.2 and did like many others have said and remade all my image targets with Vuforia 6.5 and then deleted the old instance. My builds for iOS however kept failing within Unity. I then tried upgrading Unity to 2013.3 and was able to successfully get a build out of Unity and into Xcode but then they failed there. I downgraded back to 2017.2.0f2 and now have an error I can't seem to get to the bottom of:

Assets/Vuforia/Editor/Scripts/OpenSourceInitializer.cs(53,11): error CS0535: `OpenSourceInitializer.DefaultBehaviourAttacher' does not implement interface member `IDefaultBehaviourAttacher.AddDefaultSmartTerrainEventHandler(UnityEngine.GameObject, Vuforia.PropBehaviour, Vuforia.SurfaceBehaviour)'

Anyone else encounter this same issue?

Issue Migrating to 2017.2.0f2

February 20, 2018 - 7:22am #9

I'm also having the same exact issue, but it only happens when I open the project on a PC, not on my macbook. I also got about 20 error messages saying "Broken text PPtr in file". Anyone have a solution to this?

Im using Unity 2017.2.1

Issue Migrating to 2017.2.0f2

December 31, 2017 - 10:04am #8

I am also having the same issue. Did you able to solve it? Please let me know if anyone has solution for it.

Issue Migrating to 2017.2.0f2

October 13, 2017 - 9:00am #7

A * is often used as a wildcard character to mean "all" so this case Assets/Vuforia/*.* means delete all files of all extension types in Assets/Vuforia/

Thanks,

-Vuforia Support

 

Issue Migrating to 2017.2.0f2

October 13, 2017 - 7:32am #6

Thanks Strasza.

I'm having trouble following one part of that document though. In the file paths, what does *.* mean? 

Issue Migrating to 2017.2.0f2

October 12, 2017 - 11:46am #5

Hi BennyOKC91,

Please check this post to find our new migration documentation: https://developer.vuforia.com/forum/unity/migrating-vuforia-62-unity-projects-vuforia-65-unity-20172

Thanks,

-Vuforia Support

Issue Migrating to 2017.2.0f2

October 11, 2017 - 8:05am #4

In Vuforia Configuration in the Inspector, I just noticed that it still says I'm on Vuforia 6.2. Hopefully removing the old SDK will do the trick.

Issue Migrating to 2017.2.0f2

October 11, 2017 - 7:54am #3

It looks like I failed to screenshot the original issue with my 2017.2 project. To my best recollection, it was something about not having the material files for my image targets. I was pretty sure that was due to a failed attempt at deleting Vuforia 6.2 (I think I deleted stuff associated with 6.5) which is what prompted me to just redownload Unity. 

Would there be a way to repair the error I'm getting now or will I have to create a new project? Would the error still be attached to game objects I would be copying into the new project?

Any additional support would be greatly appreciated.

Issue Migrating to 2017.2.0f2

October 9, 2017 - 2:42pm #2

Hello BennyOKC91,

The errors you posted here are likely because you pulled the project into 2017.3, which Vuforia currently doesn't support.

Do you recall what the error was that was preventing you from building in 2017.2 after you updated all of your game objects to use the native Unity version of Vuforia? The other major step you'll need to take at this point is to remove the old 6.2 sdk that you previously had in your project.

A document that will assist with this migration is going to available soon as well.

Thanks,

-Vuforia Support

Log in or register to post comments