The Mixed Reality Forums here are no longer being used or maintained.
There are a few other places we would like to direct you to for support, both from Microsoft and from the community.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.
If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.
And always feel free to hit us up on Twitter @MxdRealityDev.
Why does the resolution change and what was it beforehand?
From what I'm seeing, the resolution changes when enabling Mixed Reality Capture. What's the regular resolution when MRC is disabled? In particular, it would appear that the image is "zoomed" when enabling MRC as it suddenly enlarges and crops the outer edges when MRC is enabled at any resolution. Is there a particular reason this occurs and the two modes don't even appear to match in aspect ratio?
Best Answer
-
Options
@StephenEnochian said:
From what I'm seeing, the resolution changes when enabling Mixed Reality Capture. What's the regular resolution when MRC is disabled? In particular, it would appear that the image is "zoomed" when enabling MRC as it suddenly enlarges and crops the outer edges when MRC is enabled at any resolution. Is there a particular reason this occurs and the two modes don't even appear to match in aspect ratio?I found a workaround. In Unity, if you store the initial field of view value from the camera, set the canvas render mode to "Screen Space - Camera", set the UI Scale Mode to "Constant Pixel Size", and then dynamically set the canvas Scale Factor to the initial field of view value divided by the current camera field of view value, then it will dynamically scale - which in turn will prevent the "zooming" effect.
A side note, if you find that UI elements are off screen, attempt to anchor them to the center point first. That may fix that issue.
0
Answers
In normal mixed reality (MR) mode you are seeing a window used for 3D drawing of the MR scene, but not any camera input since it is transparent. In MRC mode you are seeing what one of the HoloLens cameras captures (unless you deselect that option in developer mode web page), with the 3D scene drawn on top of the camera input. The camera used is likely the one used for gestures which is wider than your display screen so gestures can be captured in a wider area, and therefore it is likely lower resolution in the field of view for the MR scene. This likely translates into a lower resolution image approximating the primary MR scene we normally see, and may explain the aspect ratio difference.
Hopefully on of the MS HoloLens team can provide further detail or corrections...
In Formation, Inc.
.
With this in mind, is there a definitive way to ensure what is developed can be 100% visible in both views? Maybe a recommended aspect ratio, a way to detect MRC is in use and rescale, etc. The concern is using MRC for an audience preview and they lose part of the content in the process.
Also hoping the MS HoloLens team can jump in with clarification/details...
I found a workaround. In Unity, if you store the initial field of view value from the camera, set the canvas render mode to "Screen Space - Camera", set the UI Scale Mode to "Constant Pixel Size", and then dynamically set the canvas Scale Factor to the initial field of view value divided by the current camera field of view value, then it will dynamically scale - which in turn will prevent the "zooming" effect.
A side note, if you find that UI elements are off screen, attempt to anchor them to the center point first. That may fix that issue.