Related to the comment in the issue for this.

Think it makes more sense to do this as a property in the PCamHost node for usability and flexibility reasons.

It's also a lighter change, as the caller of the get_follow_target_physics_based() method is just the PCamHost. So can effectively skip the entire logic of that method by simply adding a conditional checker around it like mentioned in the issue.

Feel free to set up the logic for the interpolation_mode mentioned in the issue for this PR; it should be a fairly trivial amount of work.

Otherwise, am happy to add it myself for the next release!

Hey, I'll have this PR updated within the next day or so.

Thanks for taking the time to read everything over, as well as provide the context with PCamHost. I think the solution you mentioned is much more concise.

Hi @ramokz, I've just made an update that incorporates the enum. Please let me know if you have any questions.

On your comment about the change being lighter:

It's also a lighter change, as the caller of the get_follow_target_physics_based() method is just the PCamHost. So can effectively skip the entire logic of that method by simply adding a conditional checker around it like mentioned in the issue.

In order to ensure that each Camera's _process/_physics_process is called where appropriate, I used the _physics_interpolation_enabled property and added some getters/setters. If there's a better way of doing this, please let me know.

@ramokz I've done the following:

1. Removed the logic in phantom_camera_2d.gd and phantom_camera_3d.gd
2. Updated the setter to call _check_pcam_physics

I also double-checked, and this resolves my issues with #535 .

Let me know if you need anything else. 👍