Can documentation on a replacement approach for 'pcam_host_owner' be written please?

[Invertex]

I noticed this breaking change was mentioned in the update log, but I did not see anything written about what the alternative is to achieve similar behavior... I want to know what the currently active PCAM is, and to do that I was getting the host reference from an existing PCAM through pcam_host_owner so I could check what its active PCAM value was.

What would be the approach for doing that now, given I have no desire to make multiple hosts?

Major breaking changes should generally come with some sort of workaround advice so people don't have to completely dissect all of the addon's code to try and figure out an alternative.

Thanks!

[ramokz]

I noticed this breaking change was mentioned in the update log, but I did not see anything written about what the alternative is to achieve similar behavior...

Major breaking changes should generally come with some sort of workaround advice so people don't have to completely dissect all of the addon's code to try and figure out an alternative.

pcam_host_owner was never a documented nor promoted property or feature, and was meant to only be used internally. It was mentioned in the release notes to communicate the underlying change to the system for those who had forked the project, making local changes or were looking to do any potential PRs, rather than an advisory statement to end-users.

What would be the approach for doing that now, given I have no desire to make multiple hosts?

You can get the active pcam by calling get_active_pcam() from the PCamHost. It was never added to the documentation site, despite being in the source code for a very long time, so added it just now.

I want to know what the currently active PCAM is, and to do that I was getting the host reference from an existing PCAM through pcam_host_owner so I could check what its active PCAM value was.

You might have an easier time referencing the PCamHost via the PCam Manager instead, as that is a globally accessible singleton with references to all addon nodes in the scene. So in your case, you can access the PCamHost by calling PhantomCameraManager.phantom_camera_hosts[0], which should return the first, and by the sound of it only, PCamHost instance in your scene. Where you can then reference the active PCam like mentioned above.