Invisible barriers
Some times we don’t want entire space aviable, then we use some invisible planes to block out people, in this tour I place many of them but I can pass trough if you click far point on screen. This problem also happen whith walls (seethe video) Compartir - YouTube
if I put a invisible barrier all Hotspot behind them is totally block, so is imposible to interact with trigger behind barriers.
This issue born because some users complain wen them click on a wall and move in front of but too close, so they stick there. I tried to figure it out how to avoid that.
If someone have an answer to those issues please let me know.
The first issue is a bug in how the collisions are handled in scenes with stairs. When you click on an object, the collision detection logic checks how far in this direction the camera can move in a straight line without hitting any obstacle. This approach works correctly if there are no stairs, but with stairs, the path can become blocked by an obstacle because the camera height changes. We will work on fixing this.
Tomorrow we will release a change that adds support for setting WALK.KEY_MOVE_MIN_DISTANCE_TO_OBSTACLE. It will allow you to limit how close you can walk to obstacles without affecting trigger click detection (for now this will be available only in Shapespark hosting so you will need to upload the scene to test it).
Hi @jan, I still have the problem of crossing barriers when I touch a point in the distance and there are stairs in the middle, did you manage to solve that? a customer asks me why he keeps reaching places he doesn’t want to even when he has barriers in the middle and I can’t give him an answer to his problem!
Does the barrier go all the way up (for example up to the ceiling), so the customer is forced to click the barrier, no matter how high he is on the stairs?
I’ve tried that option, but I have interactions beyond the barriers and I can’t take the barrier up to the ceiling because that would also block the interactions!
Temporal solution
For now (and only in this case) I can place a ¨change view action¨ on that surface, so instead of taking the user to the place he touches, the action will locate him at a certain distance.