Open ghost opened 1 year ago
See https://github.com/godotengine/godot/commit/b11bb595d137c82bbf30340ef7d8fdf6d6dc08de – this was changed when ClippedCamera was removed in 4.0.
Has this issue been resolved yet?
I think this is a bug and should be addressed. The camera shouldn't automagically decide to do a shapecast and it should respect the ray + camera configuration. clipped camera and spring arm cohexisted previously and they had different usecase for creating different types of camera. This should be still supported as it was before. I believe the existence of this issue is proof that they address different needs and both should be supported.
If we agree this is a bug, why was it closed as not planned?
If we agree this is a bug, why was it closed as not planned?
Sorry, I reopened it ;)
Godot version
v4.0.2.stable.official [7a0977ce2]
System information
Windows 10
Issue description
SpringArm3D
does not apply themargin
property if the direct child is aCamera3D
, take a look: C++ linkSteps to reproduce
SpringArm3D
with a direct childCamera3D
:margin
property ofSpringArm3D
changes nothing;Node3D
between the nodes:margin
property now correctly influences when a collision happens.Minimal reproduction project
N/A