You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the only mechanism to visualize a specific controller model is for that model to be baked into the application as an obj, fbx, etc. and referenced in the appropriate profile.
HoloToolkit leveraged UnityGLTF, from Khronos, to enable requesting the model from the device. That had an additional dependency on Newtonsoft's JSON library. This dependency has caused conflicts when customers attempted to integrate HTK into projects that used a different version of the library,
To enable GLTF without the dependencies, we are investigating modifications to the UnityGLTF code that replaces the Newtonsoft library with .NET's DataContractJsonSerializer
The text was updated successfully, but these errors were encountered:
Overview
Currently, the only mechanism to visualize a specific controller model is for that model to be baked into the application as an obj, fbx, etc. and referenced in the appropriate profile.
HoloToolkit leveraged UnityGLTF, from Khronos, to enable requesting the model from the device. That had an additional dependency on Newtonsoft's JSON library. This dependency has caused conflicts when customers attempted to integrate HTK into projects that used a different version of the library,
To enable GLTF without the dependencies, we are investigating modifications to the UnityGLTF code that replaces the Newtonsoft library with .NET's DataContractJsonSerializer
The text was updated successfully, but these errors were encountered: