Hardcoded maximum ray distance when Viewport processes 3d object picking

[Flarkk]

Godot version

4.0 dev 8b692e8 + all 3.x

System information

n/a

Issue description

When processing its physic 3d picking events, Viewports cast rays from camera's origin to 10000 units ahead from it.

The 10000 is harcoded in Viewport::_process_picking() when calling PhysicsDirectSpaceState3D::intersect_ray() as following :
intersect_ray(from, from + dir * 10000, [...] ); (see the actual code here)

This does not allow object picking in arbitrary large scenes using the built-in Viewport's event handling capabilities.
A possible workaround would be not to rely on the built-in Viewport's event handling capabilities but instead casting rays manually with a custom 'to' distance. This however makes user interaction handling much more cumbersome.

Here are the few possibles ways of fixing it that immediately come to my mind :

• using camera's far clipping distance instead of harcoded 10000
• adding a user defined property to Viewports allowing setting a custom maximum distance
• providing PhysicsDirectSpaceState3D a method to check ray intersection without any maximum distance, and use it in Viewport's picking events processing

I think the point of view of experienced Godot contributors is required here to select the most suitable fix regarding Godot design philosophy.

Steps to reproduce

Obvious from code reading

Minimal reproduction project

No response

[Flarkk]

Realizing that some others arguments of PhysicsDirectSpaceState3D::intersect_ray(), namely the physics layer bitmask and the Bodies / Area toggles are hardcoded as well.

They probably need to be either turned into Viewport properties or taken back from the Camera settings depending on Godot design principles.

[S0yKaf]

Here are some videos just to show the issue in action.

Current Behavior

old.mp4

---

Fix in #54369

fix.mp4