Skip to main content
motorsep
Inspiring
April 28, 2016

[Gear VR] Mouse X and Y input axes don't work with touchpad

When I was digging Unity, I used mouse axes for Gear VR's touchpad swipes. Somehow it doesn't work with UE4 on Gear VR :/

This is my test setup (below). On PC (in the Editor) when I move mouse by X, I get coordinates printed. On Gear VR coordinates are always zero :/


Full image: http://s32.postimg.org/6sj0gjzn7/gearvr_touchpad_test1.png

Is there a different way to work with touchpad in UE4 ?

Thanks
    This topic has been closed for replies.

    6 replies

    artyom17
    Up and Coming
    April 28, 2016
    You should use Input Touch event instead of mouse. See the attached pic.

    motorsepAuthor
    Inspiring
    April 29, 2016
    That worked (printed coordinates)! Thanks a bunch!

    Btw, just noticed something interesting. When I take out phone from Gear VR, the phone reports "mouse disconnected". So, perhaps Gear VR's touchpad is a mouse after all if system treats it like one?
    motorsepAuthor
    Inspiring
    April 29, 2016
    For horizontal swipe (from back to forward) I got the following coordinates:

    [2016.04.29-04.18.52:340][  0]LogBlueprintUserMessages: [FirstPersonCharacter_C_1] X=1268.005 Y=738.986 Z=1.000
    [2016.04.29-04.18.52:356][  0]LogBlueprintUserMessages: [FirstPersonCharacter_C_1] X=1266.005 Y=738.986 Z=1.000
    [2016.04.29-04.18.52:374][  0]LogBlueprintUserMessages: [FirstPersonCharacter_C_1] X=1266.005 Y=739.986 Z=1.000
    [2016.04.29-04.18.52:391][  0]LogBlueprintUserMessages: [FirstPersonCharacter_C_1] X=1264.006 Y=739.986 Z=1.000
    [2016.04.29-04.18.52:408][  0]LogBlueprintUserMessages: [FirstPersonCharacter_C_1] X=1262.007 Y=739.986 Z=1.000
    [2016.04.29-04.18.52:442][  0]LogBlueprintUserMessages: [FirstPersonCharacter_C_1] X=1261.007 Y=739.986 Z=1.000
    [2016.04.29-04.18.52:459][  0]LogBlueprintUserMessages: [FirstPersonCharacter_C_1] X=1247.013 Y=738.986 Z=1.000

    Just ~21 units is all there is across the touchpad?

    Do I just calculate delta to determine whether it was a full swipe or partial ?

    Another odd thing I noticed that there is no way to saw whether I swiped front to back or back to front, top down or down up :/ How would I be able to determine that ?

    Thanks
    motorsepAuthor
    Inspiring
    April 30, 2016
    I think I figured it out (almost)! Thanks :blush: 
    artyom17
    Up and Coming
    May 2, 2016
    So, yeah, it might be a bit counter-intuitive. When you touch the touchpad first time (in any location), it gives you coordinates {1280,720}. Now if you slide you finger towards the front panel it will decrease the X, towards your face - increase the X (starting with 1280). Up - Y value is decreasing, down - Y value is increasing (starting from 720).
    motorsepAuthor
    Inspiring
    May 2, 2016
    I didn't use "moved" socket after all. I got vector broken to X and Y, got those values on press and release, got delta and based on that determined whether it was an actual swipe or a tap.
    Terms & ConditionsAccessibility statement