(Resolved) physical cam settings on HDA

[LeoYfver]

What we want:

to be able to add physical cam properties to a hda containing a camera and the repsentative node is the camera inside

why:

In our pipeline we have a camera asset which is an hda which containg camera and other settings. We dont want to unlock the tool to apply the physical camera properties because it would break if the asset gets updated.

Question:

Is this possible to do?

[bdancer]

Yes, that's doable.
Question: could camera be nested in this hda in some subnet?
Basically, I could just check all camera parent networks for physical settings...

[LeoYfver]

yes, check parent network would be great!

[david.anastacio]

What we want:

to be able to add physical cam properties to a hda containing a camera and the repsentative node is the camera inside

why:

In our pipeline we have a camera asset which is an hda which containg camera and other settings. We dont want to unlock the tool to apply the physical camera properties because it would break if the asset gets updated.

Question:

Is this possible to do?

Hi Leo,

We do the same, we also have a camera HDA but instead it already comes with the vray camera properties in it. The camera inside the HDA already has the camera properties applied to it and the top level HDA just has the options to activate/deactivate them and control its settings. This way you don't need to apply the settings to the HDA node or unlock it to apply to the camera.

Best,
David.

[LeoYfver]

david.anastacio We discussed that too and its a possibility. I didnt really want to make our rendercamera tool having software specific settings so I thought this approach was better and artists could just add the physical camera properties when necessary. If it breaks your workflow with it checking parent hierarchies we could skip this feature.

Regards Alexis

[david.anastacio]

david.anastacio We discussed that too and its a possibility. I didnt really want to make our rendercamera tool having software specific settings so I thought this approach was better and artists could just add the physical camera properties when necessary. If it breaks your workflow with it checking parent hierarchies we could skip this feature.

Regards Alexis

Hi Alexis,

I don't see why it would break, so it should not be an issue and then both approaches are supported.

Best,
David.

[LeoYfver]

david.anastacio Sounds good

bdancer Do you think you will implement that? i guess it also needs to be possible to add the physical camera properties to subnet and HDA:s also

[bdancer]

Should be in the nightly already.