Hi Rudy!, thanks for reply :). Related to your questions:
Yes, I can reproduce that issue. For this what I do is:
-
I start an empty, mobile, blueprint only, 2d scalable and
without start content project. -
I enabled the option “Configure the android manifest for deployent to gearvr” option in edit->project configurations->Platforms->Android->AdvancedAPKPackaging
- In edit->project configurations->Rendering->VR i enabled the options mobile mutiview and mobile multiview direct checkboxs, then restart now.
- I created a character or pawn (in both happens the same issue).
- In the bluerprint of this character(or pawn) I added a touch event. To see what it appens with touch coordiates I added a camera and in front of them put a text component, those show me the vector input when i test with the mobile device (i do that because the print node doesnt work when multiview direct is enabled).
- Finally i ran the project on mi device (Samsung galaxy S6) to test.
Doing this if you touch the panel of the gear motion controller you may notice that the left side of the touchpad had a weired behavior(the coordinates in the screen not change, or change only once).
I’m using Samsung Galaxy S6, Android 7.0 whit gearVR development mode enabled.
Another important thing that I noticed doing tests, is that the problem not only happens with the controller, but also happens when I press on the screen and even with the side touchpad of the GearVR.
Thanks!.