Announcement

Collapse
No announcement yet.

Tracker support in motion controller component

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

    [VIVE] Tracker support in motion controller component

    I'm using the Vive trackers with get tracked object and everything is working well. However if you list the tracked objects the come up listed as invalid and the motion controller component doesn't seem to be able to use them. Has anyone used current firmware vive trackers with the motion controller component? I used older firmware fine, when they were reported as another standard controller.

    #2
    I am having this problem too! I can't find a way to get around the latency caused by Get Tracked Device Position and Orientation

    Comment


      #3
      Yeah, i think it's not using the late update code the motion controller component does.

      I think the main issue is that at least the version I'm on, 4.14 is using an older open vr library that doesn't have the enum for tracked devices in it. So they come up as invalid devices in the code. Also the motion controller code filters for anything that isn't a controller.

      Comment


        #4
        Originally posted by LokiDavison View Post
        Yeah, i think it's not using the late update code the motion controller component does.

        I think the main issue is that at least the version I'm on, 4.14 is using an older open vr library that doesn't have the enum for tracked devices in it. So they come up as invalid devices in the code. Also the motion controller code filters for anything that isn't a controller.
        Yeah I just had to add a custom component at least temporarily to my plugin to support the trackers, they come up under "Other" for tracked device type now instead of "Controller".

        The motion controller interface for SteamHMD throws out all results that are > the controller index's so it never iterates to the trackers.

        Epic needs to overhaul the SteamVRHMD class to support the trackers officially now.


        Consider supporting me on patreon

        My Open source tools and plugins
        Advanced Sessions Plugin
        VR Expansion Plugin

        Comment


          #5
          Is there any limit in SteamVR on how many Trackers can be tracked at once?
          Unreal Meetup Franken - Unreal Engine 4 Meetup
          Hands for VR - Space HDRI Skyboxes [Marketplace]

          Comment


            #6
            Currently 13 Trackers

            Comment


              #7
              Any one know the timeline for this being supported? If it's not already in master I might do it this week. It's a bit vexing that UE seems so Oculus focused where as Unity is Steam VR focused.

              Comment


                #8
                I'd like to know this too. Any official word from Epic on this?
                Unreal Meetup Franken - Unreal Engine 4 Meetup
                Hands for VR - Space HDRI Skyboxes [Marketplace]

                Comment


                  #9
                  Originally posted by btengelh View Post
                  Is there any limit in SteamVR on how many Trackers can be tracked at once?
                  Originally posted by rasamaya View Post
                  Currently 13 Trackers
                  That's an arbitrary number though, and will be changed whenever there are reasons to track more

                  Comment


                    #10
                    Is there support for Input Events of the Tracker yet?
                    Unreal Meetup Franken - Unreal Engine 4 Meetup
                    Hands for VR - Space HDRI Skyboxes [Marketplace]

                    Comment


                      #11
                      I was planning to add inputs from the trackers to my project this weekend. I hope they are supported. I have a four functioning trackers, but have not tested the pogo pin breakout.
                      I printed and assembled a decent mount/pogo breakout.

                      I find in unreal, depending on which controllers/trackers you turn on first to last, that dictates your device ID. I am using those ID's in my blueprints for the trackers. Anyone know of a way to keep devices assigned to specific iD's.
                      So for example, after the initial calibration, UE knows remembers, unless you re-calibrate. The problem is the device activation order, it changes ID. I wonder if we can read the device serial etc? That may help.

                      Comment


                        #12
                        Hey rasamaya, I couldn't find any blueprint support for the trackers. However, I didn't look in the source code. Maybe you have luck there.
                        Unreal Meetup Franken - Unreal Engine 4 Meetup
                        Hands for VR - Space HDRI Skyboxes [Marketplace]

                        Comment


                          #13
                          Are you using the motion controller component and if so do you have a patch or diff to make it work?

                          Comment


                            #14
                            I'm using the GetTrackedDevice-Blueprints (https://docs.unrealengine.com/latest...en-/index.html)
                            You have to find the right ID for your tracker, then it works.
                            However, you can't get any input events, or poll the state of the tracker, that's really a pitty. Because the tracker is basically a full motion controller with pins for vibration, buttons, etc., but without the plastic parts

                            Again, any official word from Epic about full SteamVR tracker support?
                            Unreal Meetup Franken - Unreal Engine 4 Meetup
                            Hands for VR - Space HDRI Skyboxes [Marketplace]

                            Comment


                              #15
                              Also wanting this.

                              Comment

                              Working...
                              X