4.20 have a Bug
i Change the Flags.bCompositeDepth to false and build new release but problem not fix!
i need rebuild the sln or what?
Rebuilding the SLN doesn’t do anything, its an engine issue so unless you are on a source copy of the engine then you need to get a version of the engine with the fix (IE: 4.21+).
If you ARE on a source version then you can pull that fix commit and patch your 4.20 version.
i use normal engine what ist better from 4.20 downgrade to 4.19 or upgrate to 4.21 with your plugin?
4.21 is pretty good, and downgrading is rather hard with any BP content…
List of recent bug fixes / changes, live on Master branch of the repository.
Now caching the secondary attachment pointer, lets me
make sure that the server gets a valid pointer on release of secondary grips, also lets me throw drop events
when the secondary attachment changed but its still a secondary.
Changed to sending the full transform on drop with client auth grips instead of just position / rotation.
Fixed a Z axis bug introduced with the lever angle re-write
Moved EVRInteractibleAxis to the VRInteractibleFunctionLibrary header,
it belongs there instead.
Switched levers over to use the Interactible library functions
Also made the dial use the same basic logic as the lever for rotation,
with an option to revert back to direct hand sampling.
Added new grip type "EventsOnly", will skip ALL extra logic of grips and only store the grip
data and fire the events for it. Whether you do anything else with it or not is up to you.
Like a CustomGrip except even more barebones as it does not fire TickGrip or obey any of the
dropping simulation logic, it is also auto excluded from late updates.
Stopped calling "StopSimulating" on Custom Gripped objects automatically.
It is legal to start and keep a custom grip simulating, that call should have
never been there. Anyone who needs their custom grips to auto stop simulating on grip
will need to call it in the OnGrip event themselves.
quick question, Is there a method for locking the controller location when gripping something like a lever, so it only moves along the levers path
How should I go about implementing the OpenVR skybox override for a loading screen? I’ve tried using your blueprint nodes but it’s still giving me the default SteamVR skybox between levels. Are there any further instructions for setting up?
You don’t want to lock the “controller”, you want to snap your hand mesh to the lever.
The textures need to be uncompressed RGBA, OpenVR won’t accept compressed textures.
It should be logging an output log error though if it gets an error returned from openVR. “VR Compositor Error %i”
VRCompositorError_InvalidTexture = 102,
VRCompositorError_IsNotSceneApplication = 103,
VRCompositorError_TextureIsOnWrongDevice = 104,
VRCompositorError_TextureUsesUnsupportedFormat = 105,
VRCompositorError_SharedTexturesNotSupported = 106,
Are the likely error codes that it would be throwing
Best Practice for Elevator in VR
Hi,
I thought to ask here, since all VR junkies are in thread ;).
I’m having some trouble creating a smooth elevator in VR. Basically, the environment ‘shakes’ a lot for the user as soon as the elevator is moving. I think is caused by the elevator floor moving, and the VR character ‘floor offset’ not updating every frame (or being delayed by the NavMesh updating?).
Does anyone have ideas on how to improve on ? Should I adjust actor location together with the elevator maybe?
Thanks a bunch!
W
You may want to move the elevator before the character moves, its likely that it is in the same tick group and the ordering is random so sometimes it moves before the chracter and sometimes it moves after the character.
Adding a tick pre-res for the player to the elevator should work…though normally a dynamic base like that should already be doing that.
Hello,
I’m trying to understand how you created the laserbeam, may I ask you in which BPs you’re setting it all up?
Thank you!
I put it inside of Epics MotionController_BP actor since I had moved the controllers out of there. I didn’t want to put all of those components into the primary character blueprint.
I didn’t manage to get an improvement out of adding pre-res… But eventually I did find the cause: I was using ‘MoveComponentTo’ (and moving the root component so that the rest would follow). It turns out doesn’t play nicely. Using a TimeLineComponenent and Lerp SetActorLocation solved my issue.
So, another day another question: Using IK on a standard SkeletalMesh, I can grip the different parts of the mesh and move them around. When using the GrippableSkeletonMesh instead (to get better control on the gripping logic), I don’t manage to grab anything but the root bone of the Skeleton. Simulation works fine. Is maybe a bug in the plugin? Or am I missing a setting here?
Let me know if you need more details…
In the template there is a “PerBoneGripping” gameplay tag that switches to using the traced bone name for the object. It is an option because normally per bone gripping is undesired. It requires a simulating skeletal mesh though (rag doll or bone chain).
If you are manually gripping then passing in the bone name / transform of the bone to the grip command is the same thing.
Be warned that overlaps cannot return a bone name, so either you would have to iterate over the closest physics bodies from an overlap or not use them.
If you are talking about posing a skeletal mesh though (as you seem to imply from IKing to match the hand) then you are out of luck here, that logic HAS to be custom as you cannot simulate and then unsimulate a bone chain and have it retain position without snap shotting the pose in the animbp (pose returns to the animgraph one on unsimulation).
You can run that manually with a custom grip type and performing your logic in the TickGrip function.
Okay, I’m having trouble with creating a holster or slotting system. It’s gripping but not by motion controller(s). Most common is pickup a sword and holster it to your hip. If I AttachComponent then gripping no longer works to unholster the sword. I was hopping to find a example of where any actor can perform a grip action not just the grip motion controller component. To me it the same issue if you build a gun with parts you can attach (different sights - upgrade gun by attaching components). The parts would be grip but then need ability to attach/unattach/swap. Any idea how one accomplish ?
Gripping works fine on attached things…if it is not an attachment grip or a physics grip (both of those automatically remove attachment by their very nature) then it will need to be detached OnGrip though, I do not automatically call Detach as in some cases you will want it to remain attached and I do not assume.
As for holstering FROM a grip, calling DropAndSocket is generally the best way as it is an all in one node for that, but dropping and then attaching is also fine.
In a general contextual sense Attachment is exactly what you are looking for regarding scopes / additions…there is no general “grip” system and one would be a far worse use for that case than just attaching. I think you may be a bit confused about how the engine works in general, every scene component or actor that is a “Child” of another one is “attached” to it.
You can look at the Potion and the Gun in the template for how they current dictate attaching to the waist on drop as well.
Okay, I missed the call to ‘Set Simulate Physics’ off on the static mesh component. I did not realize you could holster the gun or potion to your body anywhere. In the Gun case I see you implemented RequestsSocketing override. I just totally missed when going through the tutorial room stuff. Okay, so I get how to do properly with the plug-in.
I also looking to do some really advanced dynamic socketing. In my current implementation which I’m trying to convert to your plugin, I define a spline along the handle(s) of the weapons where a gripping is allowed. A marker is displayed where the final grip will occur along the spline based on where the hand is located. Like your VRSlider but the cube moves to be near the hand along the spline and OnGrip the cube marks the grip location. So to do i have to highlight the item (weapon) based on hand proximity or hand jedi pointing at a weapon. Best to use RequestSocketing and your VRSlider to implement style of gripping?
You can switch a held objects grip type to custom when it overlaps your area and manually handle tracking it to the spline it you want, the grip types are able to be set live.
It would be a good use case for a grip script though, you can either have one already on the item or add one live when its within the area that takes a spline and forces the held object to follow it.