-
Notifications
You must be signed in to change notification settings - Fork 97
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
[Bug]: Hitting an exception when attempting to start hololenscaptureapp in hololens2 using VS2022 #282
Comments
I think the VS suggestion is a red herring, but it looks like there is some exception in the initialization of the ResearchMode IMU component for some reason. Did you enable Research Mode on your HoloLens device? (You may need to restart it once after enabling it). Other prerequisite steps can be found here: https://github.com/microsoft/psi/wiki/Mixed-Reality-Overview |
Thanks Sean, After some more investigation I did end up putting it in research mode, thought it was fixed as after reboot was able to start the capture app without the exception, but now the app is just sitting there saying "Please wait Connecting to capture server " but does not ever continue on past this state. I had already installed the prerequisities from the page you linked too. Also on that note, I believe some of the 143 components are needed as I had to install those in order to clear up rebuild errors I was getting earlier in the process.... these are what I have installed.... |
Well I installed C++ (142)UWPT, but capture app and sever still exhibiting the same behavior not seeming to be able to connect to each other. will have to try some more tomorrow. |
It's hard to say what might be going wrong, but here are a few things you can try:
Let us know if any of these steps reveals anything. |
I'm hitting an issue when attempting to Launch the hololensCaptureApp after deploying to a hololens 2. VS2022 hits an exception, and the app fails to begin capturing. The below exception is what I'm hitting.
Line 39 shows this.sensorDevice
and VS gives a suggestion to remove 'this' (not sure if this is the actual issue)
Repro steps:
Rebuild after cloning repository from here: https://github.com/microsoft/psi
Hololens connected to PC via USB cable
Add IP address from PC to CaptureServerIP.txt doc and add to hololens documents folder via device portal
Enable CaptureServer firewall settings to be both "Public" and "Private"
Deploy hololensCaptureApp to hololens 2
Start CaptureServer on PC
Start CaptureApp on HL2
click start from inside the app
Yellow square appears momentarily
Hololens freezes with black screen
Observe exception in VS
If I click on continue from the exception popup, the app re-appears in the hololens and just sits there saying "please wait constructing capture pipeline" and never progresses further.
Attempted on 2 machines, 1 laptop surface book and 1 desktop PC got same results.
Not sure if this is a build issue or if something is not configured correctly.
OS: Windows 10 Enterprise 22H2
VS: Microsoft Visual Studio Community 2022 (64-bit) - Current
Hololens:
System.Exception
HResult=0x8000FFFF
Message=Catastrophic failure
Catastrophic failure
Source=HoloLens2ResearchMode
b__2() in C:\Users\v-jbobillot\source\repos\psi\Sources\MixedReality\HoloLensCapture\HoloLensCaptureApp\HoloLensCaptureApp.cs:line 249StackTrace:
at HoloLens2ResearchMode.ResearchModeSensorDevice..ctor()
at Microsoft.Psi.MixedReality.ResearchMode.ResearchModeImu..ctor(Pipeline pipeline, ResearchModeSensorType sensorType, String name) in C:\Users\v-jbobillot\source\repos\psi\Sources\MixedReality\Microsoft.Psi.MixedReality.UniversalWindows\ResearchMode\ResearchModeImu.cs:line 39
at Microsoft.Psi.MixedReality.ResearchMode.Accelerometer..ctor(Pipeline pipeline, String name) in C:\Users\v-jbobillot\source\repos\psi\Sources\MixedReality\Microsoft.Psi.MixedReality.UniversalWindows\ResearchMode\Accelerometer.cs:line 20
at HoloLensCaptureApp.HoloLensCaptureApp.<>c__DisplayClass46_0.
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.<>c.<.cctor>b__278_1(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
The text was updated successfully, but these errors were encountered: