pointmass3d physics engine causes foot-bot's proximity sensors to detect non-existent obstacles about argos3 HOT 3 CLOSED

I can't solve this issue right now, but I can point to where the problem is and suggest some quick workarounds until Carlo has time to look at this.

Non-movable objects, such as the boxes you are using for walls are added to all physics engines. Furthermore, the proximity sensor will query all physics engines for an intersection with the proximity sensors ray. The issue is most likely in the maths of bool CBox::Intersects in core/utility/math/box.cpp. This is used by the pointmass3d engine to determine whether a ray intersects the box or not.

As for a temporary workaround, setting the box to movable and just giving it a large mass might work. This should, I think, force ARGoS to place it into the first physics engine available, which would be dynamics2d, assuming the data structures inside ARGoS are initialized in the same order as things are specified in the XML (usually the case).

Note, you may want to remove the overlap from the walls as the collision forces will now come into play since the walls (boxes) are movable.

from argos3.

@allsey87 is most likely right, because this bug is probably related to issue #22.

from argos3.

Finally fixed in commit e81c753

from argos3.