Android: Virtual Joystick showing by default in 3.10.0

[terranprog]

Observed Behaviour
After upgrading android app from 3.9.0 to 3.10.0-beta2, a new "virtual joystick" appears on the screen.
It has to be explicitly turned off. Using settings.setVirtualJoystick(AppSettings.VIRTUAL_JOYSTICK_DISABLED);

Expected Behaviour
Virtual joystick should not appear by default.

Caused by #2803 Virtual/on-screen joystick support
"VirtualJoystick can be used to set the virtual joystick mode , defaults to VIRTUAL_JOYSTICK_AUTO"

"VIRTUAL_JOYSTICK_AUTO will automatically display the virtual joystick on mobile, if there is at least one joystick bind registered by the app, and if there is not an hardware joystick connected"

Fix: is to default settings.VirtualJoystick to VIRTUAL_JOYSTICK_DISABLED.
It can be enabled if desired by the application developer.

[riccardobl]

Why is this a problem? I think it's expected behavior to show a virtual joystick if you bind joystick inputs, we just didn't have a virtual joystick before

[terranprog]

What is "bind joystick inputs"? If this is some default behaviour I (and perhaps others) am not aware of it.

The problem is that after upgrading your android app a mysterious new UI element appears on the screen, that wasn't asked for.

[riccardobl]

What is "bind joystick inputs"

So, I assume your app uses FlyByCamera.

FlyByCamera binds joystick, mouse, and keyboard inputs. In 3.10, the engine detects that your device doesn't have any of those peripherals available, so if VIRTUAL_JOYSTICK_AUTO is enabled, it shows a virtual joystick to let you control the camera.

This is the new default behavior: if the engine sees that your app requires inputs that the device cannot provide in any other way, it assumes that a virtual input method is needed.

As you noted, you can disable the virtual joystick explicitly. Alternatively, you can call flyByCamera.setEnabled(false), which unregisters all of the FlyByCamera input mappings, and then bind the touch inputs manually.

FlyByCamera cannot be controlled with touch alone, so I'd say this is the right approach.

[terranprog]

I tried the virtual joystick and it works very well by the way. Noticeably better than the custom solution I was using previously.
Important to note that existing apps will have to be updated to make use of it.