Ability to disable Phone Remote functionality

[chrisyarbrough]

I would like to disable the phone remote part of the in-editor emulation. Specifically, the two GameObjects "PhoneRemoteConfig" and "PhoneRemote" which are instantiated as DontDestroyOnLoad. However, the associated classes seem to be tightly coupled via multiple singleton references. Please decouple these or allow for a configuration option to completely remove the phone remote parts and only keep the GvrEditorEmulator and GvrControllerInput functionality active when running in the editor.

Reason being that we are developing for hardware without a touch interface (e.g. Daydream Mirage Solo) and would like to remove the overhead of unused functionality (failed connection attempts, logged warnings, general clutter in the hierarchy, etc.).

Thank you!

[rusmaxham]

You can change the Controller Emulator Connection to OFF to remove the warnings and clutter. In the GvrControllerInput prefab object in your scene, under the Gvr Controller Input component, change the Emulator Connection to OFF.

We will look into fixing it to not create the extra DontDestroyOnLoad objects when it is OFF in a future release.

[rusmaxham]

Also, those game objects are only created in Editor. All of the PhoneRemoteXXX objects and Controller Emulator functionality is fully disabled in builds for device.

[rusmaxham]

This is now fixed in the latest release.