Prop Manipulator not hiding props?

Development Programming & Scripting
, , ,
1

image
image769×616 29.5 KB

image
image909×628 42.9 KB

For some reason, when I do a prop manipulator over a device it didn’t hide it. I thought the reason might be because I was starting the prop out as hidden, showing it, and then hiding it again there was something wrong with Creative 1.0. So, I’m trying to do it through code, but it still isn’t hiding. I’m wanting to hide the prop whenever the prop mover stops moving. What am i doing wrong?

2

Bump. Still having tbis issue

3

For verse, are the @editables linked to the verse device camping_gear_hider_device in your map?

Does it ever print “Cooler hidden”? If it does print this something is wrong with the prop manipulator, maybe a setting or it is attached to the wrong actor

4

Yeah thats the problem. Printing a message works but the prop manipulator does not.

5

Is the actor is it attached to hideable? Maybe you try to hide an object that you cant hide, maybe try attaching it to a tree

6

If this doesn’t work as intended, a possible workaround is to teleport the prop somewhere outside the map. This will surely hide it… but if you want it to still be “existing” for e.g. collision purposes then you will need to swap it (teleport-in) a second prop that’s identical except e.g. Visibility disabled, mesh with different material, whatever is appropriate.

2 Likes
7

o/ I can confirm hiding props via Verse using prop_manipulator_device_ is perfectly working for me.
For starters:

  • Add Sleep(0.0) before anything in OnBegin()
  • play with settings of prop/prop device (not at PC now wait till I come home ill post mine)
  • make sure stuff is connected as previously said. Check @editable devices validity (check my discord for guides on how to)
1 Like
8

Thanks for the help everyone. Ill try later today!

9

o/ new things:
Make sure collision is setup on the prop AND there is some collision primitive of that prop touching the PropManipulator zone. I’ve had bug fiesta when manipulating collisions on props… eh

10

Also make sure your prop is not set to Static, either set it to Stationary or Moveable.

11

I know this is an old post, but I’m curious about having the zero time sleep in the OnBegin() event. Do you know what this does and why we should do it? Is this something we should be doing all the time, or only under certain conditions.

12

I did find this note in Verse.digest, however I’m still not sure as to it’s purpose in the OnBegin(). I’m assuming it just gives a little extra time for things to load, but that’s only a guess.

If Seconds = 0.0 then it waits until next tick/frame/update.
Waiting until the next update (0.0) is especially useful in a loop of a coroutine that needs to do some work every update and this yields to other coroutines so that it doesn’t hog a processor’s resources.