UnitySubsystemsManifest.json
contains metadata about your provider that can be queried before your plug-inA set of code created outside of Unity that creates functionality in Unity. There are two kinds of plug-ins you can use in Unity: Managed plug-ins (managed .NET assemblies created with tools like Visual Studio) and Native plug-ins (platform-specific native code libraries). More info
See in Glossary is loaded. The values in this dictionary are used to populate specific instances of SubsystemDescriptors in C#. For example, information within the displays
list is used to populate XRDisplaySubsystemDescriptors.
For Unity to find the a native library referenced by the UnitySubsystemsManifest.json
file, the library must be no more than two subfolders deeper than the UnitySubsystemsManifest.json
file.
Example .json file:
{
"name": "PluginName",
"version": "1.0.0",
"libraryName": "UnityXRDisplayExample",
"displays": [
{
"id": "Display0",
"supportedMirrorBlitReservedModes" : ["leftEye","rightEye", "sideBySide"]
}
],
"inputs:": [
{
"id": "MockHMD Head Tracking Stationary"
},
{
"id": "MockHMD Head Tracking Simulated"
}
]
}
Metadata | Description |
---|---|
name |
The name of your provider. Must match the first parameter of your native plug-inA platform-specific native code library that is created outside of Unity for use in Unity. Allows you can access features like OS calls and third-party code libraries that would otherwise not be available to Unity. More info See in Glossary’s RegisterLifecycleHandler call. |
version |
Unused currently. |
libraryName |
Must match the name of your provider’s native plug-in binary without the extension. |
displays |
Collection of Display subsystem providers. |
id |
Identifier for this display plug-in configuration. The id must match the string you pass into your native plug-in’s RegisterLifecycleHandler call for that subsystem. You can have more than one display , as long as your native plug-in calls RegisterLifecycleHandler for each. |
inputs |
Collection of Input subsystem providers. |
Your manifest file can include additional fields for a display record after id
- subsystems specify which parameters are valid.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.