Doesn't Work on NReal
I paid for the Pro version and built sample scenes for NReal. None of them are working.
Extremely disappointed!
1. SDK Version: 6.1
2. Development Environment: Unity-Android
3. Tracker/Scanner: Object Fution Tracker
4. License Type: Pro-Subscription
5. Target Device(Optional): NReal
First, we apologize for the inconvenience.
Please let us know where it's not working and we'll get back to you quickly.
In order to use nreal, we need to set up a few things.
See the Nreal Setup Guide .
If you have any questions, feel free to ask.
Thank you.
Best regards,
Shelden
MAXST Support Team
Hello,
I have meticulously followed the guide (Nreal Setup Guide).
But, nothing happens when I build and run the app on Android for the Nreal Glasses. The ObjectFusionTrackerForNreal and ImageFusionTrackerForNreal scenes are not tracking anything.
The trackable object is not recognized.
When I build the 'MaxstARSamples' for Android (AR on the phone itself, with the ARCamera Object), the tracking does work for ObjectFusionTracker and ImageFusionTracker.
I don't know what more I can do for NReal.
Best Regards,
Patrick
It's hard to tell what the problem is based on the situation you described.
Please send the Asset package to sdk@maxst.com and we'll look into the issue and let you know, thank you.
Best regards,
Shelden
MAXST Support Team
We apologize for the inconvenience.
There was something missing from the Nreal Setup guide.
Please refer to the Unity Setup guide
Build a Sample App (Android) 8 and 10 seem to be missing.
We will fix the developer documentation. Thank you.
Best regards,
Shelden
MAXST Support Team
There was one more problem. AR SDK 6.1.0 supports up to Nreal 1.x.x.
It does not currently support Nreal 2.x.x. Please use Nreal 1.10.2 until it is updated. We'll let you know when an update is available.
To summarize
1. go to Project Settings > enter a package name
2. select Project Settings > Configuration > Scripting Backend > IL2CPP, Target Architecture > ARM 64
3. Import Nreal 1.10.2
Thank you.
Shelden
MAXST Support Team
Hi Shelden,
Yes, downgrading to NRSDK 1.10.2 (with those project settings) solved the issue.
Thanks a lot,
Patrick