VR Expansion Plugin

[mordentral]

@MevNav;734691

Ooooh. Well now I feel silly.

That does make things a lot easier. However, it seems that in certain situations that doesn’t quite work. I found that if the trace fails and it falls back on the “overlap” method, it will use the “ComponentOverlapComponents” function. It’ll pick the first value in that array and ignore everything else, and component might be the one set to not be blocked by VRTraceChannel. I found that means it’ll grab onto these components away if they’re attached to something that implements with VRGrip Interface. For example, if you have an actor consisting of a smaller static mesh surrounded by a larger collision box, you can grab onto the larger collision box despite it being set to ignore VRTraceChannel due to the fact that it’ll still implement VRGrip Interface.

My solution was pretty similar to the last one. Rather than picking the first object in the array, I removed any objects that ignored VRTraceChannel. After checking if anything is left, it’ll then pick the first object in the array. Probably not the best solution, but it seems to work just fine.

Also, since it was my first post I’m pretty sure the site made it invisible until it made sure it wasn’t spam. Probably why you missed it.

Hmm, your edge case is correctly bugged then and your solution is useable, I had not considered bounding geometry around the overlap attempt. However instead of directly denying it there I made a new function “IsValidGrabOverlap” so that the filtering can be overridden further. Newest version of the template has it corrected.

However what it does is loop through overlaps and returns with the first one in order that collides/overlaps VRTraceChannel.

I had forgotten that the grab sphere now overlap with all geometry not just vrtracechannel, behavior was caused by that.

@Astrea337;734645

Hello ,
I love the work you’ve done on plugin. truly fantastic.

In the VR Template, the collider on the VRRootComponent follows the X and Y movement of the HMD. makes sense, as it is a cylindrical “full body” collider by default.
Is there a way to have it follow the HMD’s Z movement as well, for a spherical “head only” collider?

I would normally just put the collider as a child of the camera, but I do want to block the head from moving through walls.

Currently? No, that actually would involve a surprising amount of re-coding of the entire character system, due to how ingrained floor detection and offsets are it would be even more of an overhaul than the VRCharacter already is. Let alone trying to handle cases like the head moving over an object that is below the neck and deciding if it should be the new floor for the player or not.

I had proto code for adding a second collider only around the head and running additional logic around how both capsules behaved, however the results were inconsistent and not what I was looking for at the time, also without integrated waist tracking I don’t foresee them being good enough to spend a large portion of my time on.

If using only “flight” style movement something of the sort could likely be achieved by setting the capsule height to something very small and adding to the VRCapsuleOffset in the Z direction to center the capsule around the camera. However as soon as a walking / ground based movement was introduced it would break down as it would find the floor off of the new location.

@LCCssumsion;733667

Super cool template and functionalities!

So, I replaced the laser activate action in the left-controller, with a hold-pressing to show a VRStereoWidget that I’ve attached to the HeadMeash … but it is not interactable with the laser from the right-controller – like the server menu is (the one on the cube that has the “mirror”).

I understand that VRStereoWidget is alpha now; have you made any headway into its use as an interactable HUD? (I’m pretty sure I’m implementing it incorrectly on the Vive_PawnCharacter.)

Sorry for late reply, your post got buried. It should already work as an interactible hud, you can directly load the server menu up in one and use the options (that is what I was testing with initially).