-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to make it works in unity and show in Hololens 2? #46
Comments
what is your dll-path in your project? You are providing no information... |
Those settings are ok. |
You have to work with Windows Mixed Reality. Remove OpenXR. As for the path error, I can't tell you exactly what your problem is. Maybe your path is too long? There was a issue in some unity versions with the length of a path. |
if you followed the instruction for this plugin, there nothing else you have to do. It should work. |
I think I followed the instruction, is it possible to have your successful project, I don't know what happen to my project. |
I know it has been long but anyway. The built DLL and winmd files just give you an interface (basically functions that you can call) to access the research mode sensor data via C# script. Putting these two files directly in your own Unity project won't show you anything: you need to write your own C# script and configure materials and shaders in Unity if you want to visualize it. The UnitySample folder showed a sample Unity project on how to do that, though I guess you don't have to visualize the images in your own app if you are just interested in its computer vision applications. If you are only interested in streaming sensor data to laptop, the psi project is definitely easier to use. |
Thanks for author's project. When i try to follow the steps to put the .dll and .winmd into my unity project, it didn't show the depth camera view in hololens.
My hololens just show the view that i built before, but there is no any error msg, what's wrong with this situation, do i need to do anything to activate the .dll?
The text was updated successfully, but these errors were encountered: