Sub Camera with Post Effects conflicts with Game Camera (BUG?)

Greetings-

I'm experiencing an issue with setting up a virtual camera to have post-effects inherited from a sub-camera as per the documentation (this is in conjunction with Cinema Director). I'm hoping i'm missing something and it's just a matter of setting things up correctly.

The issue i'm having is that when i place a "real" camera (a unity camera with post effects on it) and make it a child of the virtual camera which I want to inherit the post effects, it conflicts with the Main Camera (which has a Main Camera tag on it) at runtime. The conflict is that it causes the Main Camera to turn off (since it sees this other camera and only allows one camera to be active, thus turning off the main one), which causes the other shots using that main camera to not render and display the "no cameras rendering" text in Game view. IF I turn off the post effects camera, it is ignored and no post-effects are inherited. When using Cinema Director with the standard camera shots, they are enabled and disabled depending if they are currently active in the timeline.. this is not happening with the nested virtual post-effects camera.

So my question is, how do I get the nested post-effects camera NOT to conflict with the Main Camera? Also, is the expected behavior that it ONLY inherits the post effects OR that it uses the actual nested camera? It appears the latter is true.

here's the repro steps:

Create a Main Camera with Main Camera Tag (if one isn't already in scene)
Using Cinema Director create two CinemachineShots
Reference shot one to "Virtual Camera A"
Reference shot two to "Virtual Camera B"
Create a new camera and add a post-effect to it (image effect\color adjustment\grayscale)
Make post-effect camera a child of "Virtual Camera B"
Hit Play in editor and notice GameView does not render and displays "no cameras rendering"
Note Main Camera is turned off in Hierarchy

thanks.. hope this made sense.

 

Thank you for the reply and instruction: I failed to mention that i'm running Unity 5.5.0 with the lastest Cimemachine from the Asset Store. I found the the pre-release Post Processing Stack package and imported that, however I'm not finding a CinemachinePostFX behavior anywhere, is this a 5.6 feature rolled in with the Unity 5.6 native Cinemachine? Can I get this workflow to work in 5.5?

thanks!!!!

 

Excellent! Will do... thanks

 

one last shot, so importing WITHOUT the Cinemachine/Timeline still throws a slew of compile errors with the scripts in the Runtime directories... is there a more selective import to try ?

 

Gladly, but before I re-import the package let me make sure i'm EXCLUDING the right assets.. here's a snapshot of my import:

 

Ahh.. i see. In doing so, is there a potential to break existing cutscenes/rigs that are already set up using CM?

 

ok.. i'm going in... first set of compile errors as follows

 

Greetings again!

Thanks for your help, i've managed to get it running and am in the process of replacing my cameras and overall everything seems kosher with one exception... as i'm working with Cinema Director the Cinemachine Shot no longer recognizes the new Virtual Cameras. It appears the old ones were prefabs and the new ones aren't. I searched for the issue on the forum but came up empty. If you can guide me past this, i think I will be good on my own from here on out... so one last time.. HEEEEEELLLLLP

thanks!

 

PS creating a prefab out of the Virtual Cam doesn't do the trick either, so it must be something other than that.. i'm hoping I haven't found a chink in the armor

 

I suppose I could just add the cameras as actor groups and enable/disable them....

Welp, unless you know of a fix for the "Cinemachine Shot Track" issue, I may have spammed my way to a solution with this thread

 

What I meant was that I'm using Cinema Director from the Asset Store and after going to CM2.0 the Cinemamachine Shot inputs in the Shot Track no longer allow me to hook up a Virtual Camera, it simply won't let me select or drag one into the "Target Camera*" slot.
Having said that, I did import JUST the legacy API package and imported that (no other timeline assets were installed prior) and that resulted in a spew of errors:

For the most part, adding the CM Virtualcams to the Cinema Director as Actors has worked but of course the Fade/transitions don't work with those Actors (Global Tracks).. I wish we did move to 2017, but that move is above my pay grade Hopefully we will in the near future, but for now... this is it.

Also, unfortunately the Game Camera Guides don't render either, which I presume was due to commenting out the initial lines that were throwing out errors as per #12 in this thread.

 

Not worries, I'm sure there's enough to keep straight just with going to 2017. Yes, Cinema Director has Cinemachine CinemaDirector Integration as part of their package. I'll hobble along until our studio puts on their big boy pants and moves to 2017. Thanks again for your support.

 

@Oneironaught , Cinema Director needs to be updated to support CM v2.0. I know Dan and Adrian at Cinema Suite and will let him know about this, thanks for the heads up. Hopefully they get a fix in soon, I bet it's incredibly trivial to update on their end.

 

Hi Adam, thanks for your response and offer to contact Dan and Adrian at Cinema Suite. I was wondering if you were able to get around to speaking with them. If indeed it turns out that it is a trivial fix for them, I would be very interested in communicating with them to perhaps get a patch. We're a bit stuck with some of the Director features not working because of it. Would you be willing to make an introduction? I'd be happy to pass you my contact information.

 

Hi @Oneironaught - Dan responded "I will have the guys squeeze this in on Monday."

PM me your email so I can intro you two.

 

Hey @Oneironaught and @Adam_Myhill,

Squeezed in this update for you, the CinemachineShot should now accept any of Cinemachine's virtual cameras. If you installed the old integration package you may want to delete those files first just to be safe.

 

Excellent Adam, much appreciated! Everything seems golden

 

Amazing! Great job on the fast turnaround. Much appreciated.

 

Yes, thanks to ALL of you for the great support!