Haptic buzz on Snap Zone Enter?

bjornsyse

Hi, anyone with ideas on how to get a Haptic buzz activated when entering a snap zone? I'm still getting used to this new event/prefab driven way of thinking in v4... 😅

bjornsyse

Hi. I've managed to activate the Haptic on the interactors when i grab Interactables now. However, I get both controllers to rumble ignoring that I set it to only rumble the active one. Has anyone else succeded in using Haptics for example when grabbing Interactables?

populousHippo

I don't know if this could help, but I managed to solve it this way

https://flarum.vrtk.io/d/69-haptic-feedback-oculus-quest

bjornsyse

populousHippo Since I'm using VRTK4 I suspect the findings does not apply to me...

ChrisH

Hi @bjornsyse

It seems likje OnlyRumbleActiveInteractor is just turning RuleChecker active/inactive.

That rule checker will match which controller you're using (left or right) and toggle respecive VibrateXController components.

I've tested on BarnLeftDoor (which requires 2 hands to use) - the method ApplyRules never gets called, without that respective VibrateXController elements are not updated at all.

I suspect that could be the reason why both of them vibrate for you. On your Interactable with InteractorHaptics call InteractorHapticsFacade.ApplyRules (and pass InteractorFacade as argument) - that'll enable / disable correct elements.

https://ibb.co/nfdNn3z

bjornsyse

Hi Chris

I am doin exactly that, calling both gameobject.setactive and the applyrules function. However, I'm not sure how to pass something as an argument via the unity events on that function?

ChrisH

Hi bjornsyse - if you look at InteractableFacade Grabbed (InteractorFacade) event you'll see it already has an argument of InteractorFacade - you don't have to do anything else than calling InteractorHapticsFacade.ApplyRules - just make sure you're choosing top method that says Dynamic - that'll pass interactor that is used for grabbing to function.

BTW - interactor get's there from CollisionTracker on /VRTK Setup//TrackedAlias//Aliases//LeftControllerAlias/LeftInteractor

It's due to chain-call-process that's set for grabbing interaction - toolkit passes it down. If you want to know exactly how it happens you can add a breakpoint in Interactables.Grab.GrabInteractableConfigurator.NotifyGrab function and once you grab something and debugger kicks in just navigate up the stack trace, that'll help you understand what's happening.

bjornsyse

That is very strange, I'm trying something really simple now:

I add an InteractorHapticsprefab as a child to an InteractablePrefab
I hook up the Grabbed-event to InteractorHapticsFacade.ApplyRules() OR Begin() function.

If I use ApplyRules() nothing happens.
If I used Begin() both controllers rumble, even though I've checked the "Only Rumble Active Interactor" flag on the InteractorHapticsFacade().

What could be going on here? Am I using this stuff right?

[https://dl.dropboxusercontent.com/s/qz0hmqjqrh8y6vb/2019-11-21_12-51-15.png]

ChrisH

I think you're on the right path, by default Begin calls both VibrateLeftController and VibrateRightController.

Apply Rules should not start vibrations but rather it's kicking off the process where it'd disable corresponding VibrateXController - then when Begin is called it'll just vibrate the one you've used (still enabled one).

I'd call

ApplyRules first
and then call Begin, your structure should have one of those Vibrate disabled

https://ibb.co/2k5nX0f

PS: also generally to consider (in case you're not aware) execution order of those 'wired up' action ie 'Grabbed' might not be guaranteed, would be good to split ApplyRules so they are guaranteed to run before (maybe even on touch?)
https://forum.unity.com/threads/order-of-execution-in-unityevent-invoke.544727/

bjornsyse

I hear the logic, and thanks for taking your time to help me. However, even if I call ApplyRules() AND Begin(), both of my controllers still buzz. Tried moving ApplyRules() to Touch-event (wasn't aware of the non-guaranteed order of execution) but it still fires both controllers..

Both the VibrateLeftController and VibrateLeftController-object remain active after both ApplyRules() and Begin() btw,. What rule is really run when I call ApplyRules()? Should I have to do something else than ticking that box?

ChrisH

If there still both active then that's definitely why they both rumble.

Is that RuleChecker enabled at all when whole haptics object activate? If it's not make sure you've ticked 'Only Rumble Active Interactor' - I know you've written you did but doesn't hurt to double check.

If that's still not quite working, try renaming RuleChecker to something more unique and put a breakpoint in

Zinnia.Rule.RulesMatcher.Match

        public virtual void Match(object source)
        {
            if (Elements == null)
            {
                return;
            }

            foreach (Element element in Elements.NonSubscribableElements)
            {
                //CH: put a conditional breakpoint here with condition 'this.gameObject.name == "YourNowUniqueName"'
                if (element.Rule.Accepts(source))
                {
                    //CH: rule should check if source is say LeftController, if it is it'll fire corresponding Matched that'll Enable left and disable right, then the same thing will happen for right controller.
                    //CH: so really you should get true for LeftInteractor rule and debugger should enter here, and false for RightInteractor
                    element.Matched?.Invoke();
                }
            }
        }

Or if you want to drop to code somewhere I could have a quick look.

Malikk

Double check that your InteractorCollections are set right in the inspector, that tells the RuleChecker what to compare. If you just drag a prefab in from the folder there's gonna be some stuff missing. Look at any of the prefabbed GameObjects in the example scene that have haptics and look at all of the overrides it has for scene specific objects (like the interactors) that the prefab can't save. You'll probably see what needs to be dragged into those slots on your own object.

Everything else looks the same as what I eventually got working for me, you def need both ApplyRules(InteractorFacade) and Begin().

The only thing I can't personally get working is duration. It just doesn't seem to do anything.

bjornsyse

Hi, did things evolve when it comes to haptics? I see new slots in the LinkedAliasAssociationCollection pointing to haptic processes. Does anyone know what the intended way to produce haptics for Oculus Quest is using this?

drogna

I just struggled with getting the 'Only Rumble Active Interactor' toggle to work too. You might double check what type of objects you're assigning to the two InteractorHapticsFacade lists. You have to assign the actual InteractorFacade of each Interactor in the InteractorHapticsFacade. I had previously assigned the GameObjects of my Interactors which doesn't allow ApplyRules() to do it's thing.

bjornsyse

Oh ok, interesting. I would have to look that up! However, I also see new placeholders for something called Controller Haptic Process in the LinkedAliasAssociationCollection. I haven't had time to look into what that is. Would you know?

SwedishMeatball

I just managed to solve this, too! Like drogna said the Haptics prefab needs the links to each InteractorFacade. It's confusing that the prefab object in my VRTK version is linked to the wrong thing, and I don't know how to drag the InteractorFacadelink to the right place instead of the GameObject. Fortunately, in the Farm example scene there is a door (BarnDoor, the small one to the side) where the haptics are properly set up. So, copying that, enabling the main/root haptics object on first grab and also doing ApplyRules(), gives me functioning haptics that rumble the correct controller when Begin() is called.
Next problem is when two controllers are grabbing the same object and both should rumble. So far I only get it to work by having two separate haptics objects, the second one turned on by the secondary grab action, and sending a Begin() to that one, too. I wish I knew a less clumsy solution, but at least it seems to work.