Quazar Posted May 8, 2018 Share Posted May 8, 2018 I Build and Run on the Unity 2018.1. But can't start app on the Focus Headset -SDK is version 2.0.32 -Unity 2018.1.0f2 Building app on the Unity 2017.3.1f1 with not problen. Link to comment Share on other sites More sharing options...
_Alex Posted May 8, 2018 Share Posted May 8, 2018 I confirm. Had to downgrade to 2017.4.2 Link to comment Share on other sites More sharing options...
Tony PH Lin Posted May 9, 2018 Share Posted May 9, 2018 Yes, current plugin supports 2017.3. But looks 2017.4 works well. We're survey 2018 now and will keep you posted once new update release. Thanks. Link to comment Share on other sites More sharing options...
razoredge Posted May 18, 2018 Share Posted May 18, 2018 Tony this is a big problem for us as well. With the new package manager and other project management available with Unity 2018.1.1f1 we were really hoping NOT to have to downgrade and lose the great feature enhancements from a production pipeline perspective. I think your team would be doing us all a great service by ensuring that the plugin works with Unity 2018.1.1f1. Any updates there? Link to comment Share on other sites More sharing options...
razoredge Posted May 18, 2018 Share Posted May 18, 2018 any update yet? Link to comment Share on other sites More sharing options...
Tony PH Lin Posted May 21, 2018 Share Posted May 21, 2018 Thanks for your opinions. Yes we're working on supporting to latest Unity 2018 now, and planning schedule is to be ready around 7/E. BTW, Unreal plugin will also be updated on 7/E for latest version support. Link to comment Share on other sites More sharing options...
dario Posted May 21, 2018 Share Posted May 21, 2018 As a workaround (and just a workaround until 2018 is officially supported) you can open your project in 2017.x first, then edit the file Plugins/BuildCheck.cs and replace "2017" with "2018" on line 23. Then open/import the same project in Unity 2018.x (you can't go back and forth however). Also if you're having an error regarding a missing package name you can add it manually in AndroidManifest.xml as long as it matches the name you set in build settings by adding: package="..." Place it inside the main "<manifest..." tag on the first line. Note: You may see an issue (blank screen) only with the first execution of the app after an install, simply going back to the launcher and back corrects this and there's no issues with subsequent runs. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.