A. The physics engine is not enabled or configured properly
B. The collision tag is missing a name attribute
C. The sphere radius is too small to detect collision
D. The geometry tag should be outside the collision tag
Solution
Step 1: Check collision tag correctness
The collision tag syntax is correct and includes geometry with a sphere shape.
Step 2: Identify common cause of passing through objects
If physics is disabled or misconfigured, collisions won't be processed, causing objects to pass through.
Final Answer:
The physics engine is not enabled or configured properly -> Option A
Quick Check:
Physics engine must be active for collisions [OK]
Hint: Collision needs physics engine enabled to work [OK]
Common Mistakes:
Thinking missing name attribute breaks collision
Assuming small radius disables collision
Placing geometry outside collision tag
5. You want to simulate a robot pushing a box realistically in Gazebo. Which combination of settings is best to achieve this?
hard
A. Only define visual shapes and manually move the box in code
B. Disable physics engine, use only visual shapes for robot and box
C. Enable physics engine with friction, define collision shapes for both robot and box
D. Use collision shapes but set friction to zero in physics settings
Solution
Step 1: Understand realistic pushing requires physics and collision
Physics engine simulates forces like friction and collision shapes define contact areas.
Step 2: Evaluate options for realistic interaction
Enable physics engine with friction, define collision shapes for both robot and box enables physics with friction and collision shapes, allowing realistic pushing behavior.
Step 3: Reject options disabling physics or friction
Disabling physics or friction or using only visuals prevents realistic physical interaction.
Final Answer:
Enable physics engine with friction, define collision shapes for both robot and box -> Option C