License Identifiers

Licenses for specific devices or models are bound to the respective hostID (for devices) or hash (for models). These must be provided with license requests if required by the licensing model.

Getting the HostID using Unity Editor

The host ID of the device that is running the Unity Editor is displayed in the About window in the VisionLib menu.

Press the icon to the right of the host ID to copy it to you clipboard.

License Command Line Tool

Both the host ID and the hash code for models can be generated with the VisionLib License Tool. It is a command line tool and can be called with the following arguments:

Usage on Windows

Open a command line prompt inside the LicenseTool folder that is part of the VisionLib Unity Plugin.

Print the current host id

LicenseTool -i

Print information about the given license

LicenseTool -l <PATH_TO_LICENSE_FILE>

Generate hash code for the given model(s)

LicenseTool -m <PATH_TO_MODEL1> -m <PATH_TO_MODEL2>

Please make sure to copy the complete block enclosed by

-----BEGIN MODEL HASH BLOCK-----
[...]
-----END MODEL HASH BLOCK-----

Usage on macOS

Open a terminal inside the LicenseTool folder that is part of the VisionLib Unity Plugin.

Print the current host id

./LicenseTool -i

Print information about the given license

./LicenseTool -l <PATH_TO_LICENSE_FILE>

Generate hash code for the given model(s)

./LicenseTool -m <PATH_TO_MODEL1> -m <PATH_TO_MODEL2>

Please make sure to copy the complete block enclosed by

-----BEGIN MODEL HASH BLOCK-----
[...]
-----END MODEL HASH BLOCK-----

Host ID and package family on the HoloLens

Engineering License

When deploying for HoloLens, the host ID is logged in Visual Studio's debug console. When asked for the host ID of your HoloLens application, fin and enter this ID. Keep in mind that the host ID will change with your device and certificate.

Developer License

You might be asked for the package family name of your HoloLens application. You can look up this name as shown in the following screenshot:

Please keep in mind that the Package Family Name will change with your certificate and application name. So you should make sure that the correct certificate is selected and it should not be changed. The developer license in the current state is bound to a single application.

Important: We sometimes experienced the problem that the certificate selected in Unity wasn't correctly selected in Visual Studio. This resulted in a displayed package family name which differed from the one used in the application. To overcome this issue please click Choose Certificate... and select the certificate you set in Unity.