[Bug]: Hitting an exception when attempting to start hololenscaptureapp in hololens2 using VS2022 about psi HOT 5 OPEN

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....

from psi.

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

from psi.

Only thing I am seeing now that is related to this comment in the prereques.... I do not recall being prompted for this 142 windows platform tools, but I assume 143 would have taken care of this, Could not having the 142 tools be causing my capture app to hang on connecting to server?

from psi.

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.

from psi.

It's hard to say what might be going wrong, but here are a few things you can try:

1. Uninstall the capture app from your HoloLens and deploy it from scratch
2. Check your firewall settings on Windows to ensure that the server application has both "Public" and "Private" set
3. Make sure the CaptureServerIP.txt file is present in your device's User Folders\Documents folder, and that it contains the actual IP address of the machine running the server
4. Run both the app and the server from Visual Studio in debug mode with all "Exception" settings turned on, to make sure there aren't any hidden exceptions being thrown that we're not seeing.

Let us know if any of these steps reveals anything.

from psi.