Question Clear Shot camera children that are not actual children of the gameobject

My game world consists of several 3D terrain tiles that together with a floating origin are able to move and do not have fixed world space positions. Now I wanted to add some kind of "landmark" cameras to each terrain tile. Of course, their transforms have to translate with their terrain tile.

CinemachineClearShot unfortunately only seems to support direct children of its game object. As I can't make CinemachineClearShot the children of multiple terrain tiles, I am not sure how to proceed. I have a custom CameraSwitcher component which switches between vehicle and gameplay context specific cameras. Via input the user shall be able to override these cameras with the Clear Shot, which in turn should be able to choose the ideal landmark camera.

Is there a way to avoid adding multiple CinemachineClearShot cameras, one for every terrain tile?

 

Thank you for your reply. It works for now. I have my clear shot vcams persistently stored under the terrain tile together with a MonoBehavior which holds a list of them. When the game starts I reparent them under my CinemachineClearShot game object. But instead of reparenting them back under their terrain tile when the world translates, I simply translate them the exact same amount as I translate their superordinate terrain tile. I tried parenting them under their terrain tile just for the short period in which the terrain tile gets translated, but it seemed that I would have to pass at least one frame before translation propagated through the hierarchy. At least this is what I think happened, because the vcams did not translate with their tile.

It also looked as if calls to CinemachineVirtualCameraBase.OnTargetObjectWarped did interfere with the translation. Does OnTargetObjectWarped also translate its attached transform or does it only update the internal state?

 

There may had been a bug, I don't know. Fortunately, it is gone now and I can't reproduce it.

I fixed the issue regarding OnTargetObjectWarped. Previously, I called this on all CinemachineVirtualCameraBase that I could find in the entire scene. Now I don't call it on cameras that are/become children of CinemachineClearShot since they have a fixed position and don't have Follow set, don't orbit or do anything else. They just look towards LookAt. For them it is enough to translate them in parallel with the rest of the world.

I actually only call OnTargetObjectWarped on CinemachineFreeLook cameras that orbit vehicles. I guess OnTargetObjectWarped is only required when anything is damped or smoothed.