Adding the Igloo Player

Unlike previous generations of the Igloo Toolkit, the player system is not included automatically and instead must be added if it is required. This is achieved by using the Samples system of the Package Manager which adds the various scripts and features required for the player system to function, to your Project folder.

Importing the Igloo Player

Open your Package Manager and navigate to the Igloo Toolkit in the ‘In Projects’ section, then click on the Samples page.

Samples page of the Igloo Toolkit Package

Then click Import on the Player System, and it will add the Samples → Igloo Toolkit → Player System directory to your Project Assets.

It will also add a IGLOO_PLAYER scripting Define Symbol into the Player section of the Project Settings.

If you happen to not require the Player System and wish to remove it, you also need to manually remove the IGLOO_PLAYER scripting define symbol from Project Settings to avoid compile errors.

Scripting Define Symbols showing IGLOO_PLAYER added

You can now press play and you’ll notice that the Igloo player system is created.

New Features of the Igloo Player

With this evolution of the Igloo Player, we’ve streamlined the process of using the player further with the following features

You now no longer need to choose what input method you use. It will begin listening for OSC and Mouse events and respond to either.
The only exception to the above, is if Headtracking is being used, in which case you specify in the settings that it is active, and then it will listen to either VRPN or Optitrack messages based on the setting in the xml.
The player is now fully generated from code, so to modify it you can add additional features to the code creation process. We found may clients preferred this method over modifying the prefab.
A lot of old code was removed from the player system, further streamlining its creation and processing cost.