Announcement

Collapse
No announcement yet.

Mouse X and Y input axes don't work with touchpad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

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

    https://answers.unrealengine.com/que...k-with-to.html

    I recall Oculus suggested to used mouse axes for Gear VR's touchpad swipes. Somehow it doesn't work with UE4 on Gear VR :/

    #2
    Per Epic it sounds like it's not supported :/

    Going off-topic, the problem with not supporting this is that if player wants to use bluetooth keyboard and mouse with Android, player wouldn't be able to

    Comment


      #3
      Bluetooth controllers are supported and show up with axes and buttons for gamepads. This is not mouse x/y.

      Comment


        #4
        So how would I work with bluetooth mouse if I want it to be functioning as PC mouse, but on Android? (in UE4)

        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?
        Last edited by motorsep; 04-28-2016, 09:51 PM.

        Comment


          #5
          Anyhow, I tried using InputTouch and got location out of it (can use it to determine swipe). However, I am not sure how to determine whether it's a front-to-back or back-to-front, or top-down, or down-up swipe :/

          How can I do that?

          Thanks

          Comment


            #6
            Remember the location of the touch begin and compare to location of touch end to determine the swipe direction.

            Comment


              #7
              Originally posted by Chris Babcock View Post
              Remember the location of the touch begin and compare to location of touch end to determine the swipe direction.
              From what I saw yesterday, if I swipe from back to front, I get this:

              [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

              If I swipe from front to back, I get something similar, where X goes from larger value to smaller value. So when I compare it, direction will be indistinguishable, since in both cases value goes from larger to smaller and is always positive :/

              Comment


                #8
                I think you mean moving your finger over the trackpad surface on the GEAR VR, get touch input and that behave like a mouse.

                Click image for larger version

Name:	3953-screen+shot+2014-04-12+at+7.46.25+pm.png
Views:	1
Size:	17.5 KB
ID:	1105621

                Let me know if that works, just wire it up to print string somewhere

                For your numbers, that just sounds like an algebra problem, solve for the bounds [a,b] and scale (clamp)!!

                Comment


                  #9
                  Originally posted by rrstuv View Post
                  I think you mean moving your finger over the trackpad surface on the GEAR VR, get touch input and that behave like a mouse.
                  It doesn't behave as mouse. Mouse coordinates always begin from 0, and can be either negative or positive, depending where you move it from initial position (initial position is always zero). Gear VR's pad is detected by OS as mouse, and Unity for example treats it as mouse (there is no pressure, there only 1 finger support, so it's not really a pad). UE4 treats it as touch screen apparently.

                  Originally posted by rrstuv View Post
                  [ATTACH=CONFIG]91179[/ATTACH]
                  That's not how my touch input node looks like. What engine version are you using ?

                  Originally posted by rrstuv View Post
                  Let me know if that works, just wire it up to print string somewhere
                  I had basics working already. That's how I got those coordinates. Just need to figure out how to determine swipe direction.

                  Comment


                    #10
                    Alright, I don't know what I was doing yesterday, but today I got swipe direction figured out. Thanks all!

                    Comment


                      #11
                      hi,can you help out please?

                      Comment


                        #12
                        Originally posted by pixin studio View Post
                        hi,can you help out please?
                        Sorry, I am still learning the ins and out of the engine/BP myself, so I am not the best person to ask for help at this moment. However, here is a good solution for you: https://forums.unrealengine.com/show...l=1#post452131

                        Comment


                          #13
                          Thanks i all ready have that link, now i switched to HTC vive its much much better especially with room scale..

                          Comment

                          Working...
                          X