Seeing 3D collision shapes would make debugging a lot easier but even after I turn physics → debug on, I cannot see debug shapes.
I get this warning when debug enabled (WARNING:RENDER: Out of debug vertex data (10000). Increase graphics.max_debug_vertices to avoid this warning.) so I increased it a lot. The warning is gone but still no shape is visible. It works well on 2D, is it possible to use with 3D?
Also, the example of debug on: Physics debug is not playing on slow motion when debugging as the text suggest so it needs a quick fix
I tried to work out why this example does not display collision normals and did not succeed.
Also this error message occurs:
ERROR:SCRIPT: example/physics.script:12: Could not find socket 'main' when sending message 'set_time_step' from 'default:/go#script' to 'main:/loader'.
stack traceback:
[C]:-1: in function post
example/physics.script:12: in function <example/physics.script:6>
Caused by:
if self.show_debug then -- <4>
msg.post("main:/loader", "set_time_step", { factor = 1, mode = 0 })
else
msg.post("main:/loader", "set_time_step", { factor = 0.1, mode = 1 })
end
The manual says that this should be posted to a loaded proxy; what is this if a proxy is not loaded, “default:/stuff_dunno”? I am confused, probably missing something obvious, I think the solution is to mow the lawn.
edit0: The normals are drawn, but only when the collision object stops moving for long enough, and this does not happen in the example, add friction to fix. Also the arrows are hard to see because of the colour used.
