Describe the project you are working on

A third-person action RPG, camera and controls are similar to Monster Hunter or Soulsborne games

Describe the problem or limitation you are having in your project

Camera movement should not be tied to the physics update rate.

The player body moves during _physics_process, but the camera rig moves on _process and copies the body's interpolated position.

This produces perfectly smooth camera motion, even at a physics rate of 10hz, with the exception of the spring arm when the camera is near an obstacle. The spring arm causes jitter as the physics rate is lower than the framerate.

Describe the feature / enhancement and how it helps to overcome the problem or limitation

Add a property in the inspector that determines whether the spring arm is processed during physics, frame, or manually. This gives the user the most control to only update the spring after they have moved the camera.

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

Similar to AnimationPlayer::callback_mode_process, expose an enum property dropdown that determines when process_spring() is called.

Add an enum property in the inspector to control when the SpringArm performs its raycast, allowing the options:

• Physics
• Process
• Manual

It would also be nice to expose the C++ SpringArm3D::process_spring() to GDScript to support manual updates.

If this enhancement will not be used often, can it be worked around with a few lines of script?

No work around, it requires a custom implementation.

Is there a reason why this should be core and not an add-on in the asset library?

This is a small change to the existing node that makes it more useful, especially for its intended use case.