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.
Very long SyncStrings are truncated when sent over sharing service
Hi,
I am attempting to transmit image data (e.g. a photo taken at runtime) from one device to another using the sharing service. My current approach is to take the Texture2D, encode it into a JPG byte array, then base64-encode it and set it up as a SyncString as part of a SyncObject model.
However, it appears that very large SyncStrings are not being completely transmitted to other clients. For example, after encoding one particular image in this way, I get a string of size 1057988 characters, but when the other device receives the updated SyncString, it contains only the first 9412 characters. (When loading the data into a Texture2D I see the first couple pixel-rows of the image, a sign of truncated JPG data).
Is there anything I can do to allow for larger sizes of this kind of data when using the sharing service? For specific implementation reasons I would prefer not to have to upload the images to an external site and transmit just a URL via the sharing service.