Hi there!
I’m trying to make a rifle that i can hold with two hands. But sadly there are 2 problems. (and I’m using the example template.) Can you help me out?
First problem is when I want to let go of the rifle’s forend (‘VRGripS1’) by releasing the grip button, I still have to toggle the grip button by pressing again. (real problem is ‘VRGripP1’ - which is the rifle’s grip - I managed to make it possible to drop it by just releasing the grip button. So where in the Vive_PawnCharacter blueprint should I look at?)
Second problem is when I let go of the forend (‘VRGripS1’), my character drops the whole rifle when I want to still grab it by the forend.
I’m still struggling to figure out how to make reloading mechanism but I’ll try to work on that myself as much I can.
I’d be so appreciated if you could help me!
Dude, you are seriously insane. You already made a custom AI controller? That’s awesome! Yes, the only reason I was trying to switch to simplecharacter was for the AI. I’d just thought it would be easier (for me), and maybe more performant, than trying to get the AIController to set the real VR transform of the player all the time. Really appreciate the reply with the insight and suggestions, let alone the idea of a custom AIController. I have been using AIBehaviorToolkit (Marketplace AI state chaining system) for my game prototype and the toolkit AI has worked great with SimpleCharacter. I will stick to VRCharacter and press on!
Pushed a new commit to the plugin, 4.16 preview is now out, so besides some minor refactoring of the (unfinished) TrackedDeviceParent stuff I intend to get it ported over to that tomorrow.
Finished Replication overhaul for motion controllers / camera. Now has two selectable levels of
quantization at the cost a 1 bit due to replicating which option selected.
Default quant level is rounded to 2 Decimals.
Added VRAIController, can be the base of an AI controller for a pawn. Overrides the Line of Sight To and GetActorFocalPoint functions so that
if it is acting on a VRBaseCharacter it will use the HMD offset location instead of root.
I ended up only setting two levels for selection, I tried the extreme mode and it managed to save slightly more, but barely, and at the cost of a second additional bit on the other two levels. Quantization already scales how many bits are replicated based on the size of the number being replicated so at the relatively low numeric values that you will see in relative positions its difficult to get much more of a savings.
When the primary hand drops the weapon you want to to check if there is a secondary grip on it, if so, call a grip on that hand at its current location, then when the primary goes back into position you can flip it back again. Secondary grips are not full grips, they are just components that are tracked, when the primary grip is ended it also kills the secondary portion of it. Primary grips contain the information for the secondary within them.
allows for a pretty flexible system but takes some planning depending on how you want to setup your interactions.
From the sounds of it, you are actually approaching things backwards from how I set it up in the template though, you are considering the front grip the primary and the back grip the secondary, if you just renamed the sockets it would solve that for you.
Hi.
I can’t change rotation on Vive_character teleporting.
Actor -> teleport and setWorldRotation keep default rotation. Can you help me? Maybe one overrides somewhere?
(sorry for my bad English)
Sorry, back again. Is there a way to do via blueprint? I found a “Set VRClimbing Step Height” and linked it to the Vive_PawnCharacter VRMovementReference, but it doesn’t seem to do anything?
Thanks! I enabled collision on the desk w/ drawers, and i still have weird pop-up thing where if im standing against the desk and rotate myself 180 degrees ill now be standing on the desk. happens with everything waist height or lower. I can probably live with it by making my objects taller though.
EDIT waist height in the first person test mode. About knee height while actually using the vive.
Thats the normal character movement step up height variable then. The VRClimbingStepUpHeight is seperate so that you can have a different value when climbing than when walking.
i changed the normal step up value awhile ago, and it made it so I can’t walk forwards and get bumped up on top of something, but i can still turn myself and end up on top of ledges and stuff ;D
i turned the collision on the desk to block so i could jump on top of it.
I can make the same behavior occur by taking a standard cube actor and changing the scale to 0.6, 0.6, 0.6 and placing it on the floor. Then playing without a Vive, just First Person using the engine, if i walk up against that cube and rotate using the mouse, I pop up on top of it. It happens in VR too, but the cube has to be way smaller so its not a big deal at all.
Yo, did you test in VR? Or just with the fps pawn?
I can replicate with the FPS pawn and understand why it happens there, but I can’t replicate in VR and it doesn’t make sense that it would happen in VR, the movement collision behaves a little differently since the HMD directly drives the rotation of the capsule.