[VIVE] - and probably occulus - VR intereractable physic objects

[jamis]

Hi guys,

thanks for the feedbacks

@superme2015;671062

Why did it not pass quality checks if you don’t mind me asking?

various reasons, some I could easily fix (naming convention, non PBR materials), but the main one is that epic said “to easy to reproduce” … (wich is a shame because I saw far simpler blueprints in the marketplace … but I assume they have been submitted when the market needed to be filled up …

@GruntosUK;671558

2. But! It’s missing the normal pickup object from the template, I can only find yours. I added in one BP_Slot with an ID of 1 and two BP_PickupObjects (your version) with ID of 0 and 1. I expected only the item with the same ID (1) to snap, but they both did. Whats the solution if I want to use a normal pickup item from the standard template and don’t want it to snap. I can’t see an option to do this. I don’t want every item I create to snap to a slot.

hey… read carefully the description :

@jamis;669129

---

*** BP_PickupObject actor ***

---

Similar to epic’s BP_PickupCube actor but with additional features.

• can be place in a slot

• has a “type” variable picked up from the enumeration “ENUM_PickupObjectType”
  **If the type of the PickedupObject doesn’t match the “type” of the slot he’s dropped on, it won’t collide and fallto the ground.
  **

• has a “ID” integer variable
  If the type matches but not the ID, the PickupObject will be place into the slot (aligning its pivot to the slot’s pivot) but the slot will remain “locked”(slot’s “Locked” variable is still set to true)
  If Both ID and type match, PickupObject will be place into the slot (aligning its pivot to the slot’s pivot) and the slot will be “unlocked”(slot’s “Locked” variable is still set to false

in another words if the item type’s is “Key” and the slot wait for a “key” item, the item will snap, regardless its ID, in addition, if ID’s of the slot and the item match, the slot variable “locked” will be set to false
(you can add custom types by editing the corresponding ENUM

@GruntosUK;671558

2. So, I setup a standard template from the launcher, added your project on top of it. Now the standard pickup object from the base template is there, but I can’t pick it up now. It doesn’t attach, I can only push it around when trigger is pressed.

3. I think this should have been bolted on top of the normal template, some helpful things are deleted (the standard motioncontroller map for example as well as the standard pickupobject). Because of the missing items, this can’t function on its own, and it has problems when its merged on top of the standard VR template.

regular pickup objects from epic template should be pickable too … they are not included in the package… because this is the way epic want stuff to be submitted to the marketplace.

be carefull using the default VR template from epic… you may run into issues if you swap objects from my package from one hand to another. this is caused by the way the checks before firing the grab and drop event are done in their player controller… those checks have to be adapted… I recommend to have a look at the modification I made in the player controller and the motion controller.

or if you don’t want to bother… just migrate the pickup object from epic template into a new project created from the template I’ve provided.