PostProcessing Adapter conflicts with CM 2.3.3

We're upgrading a project to use Unity 2019.1 and CM 2.3.3. We were previously using the post processing adapter, which was under our Assets folder. I see now that the adapter is included in the CM package. This leads to compiler errors, because the scripts are now duplicated and there's type conflicts.

The only way to fix this is to remove the adapter in the Assets folder to use the package version of the adapter, however this breaks the script references to the CinemachinePostProcessing effect on VCams that were using the adapter from versions 2.2.8 and earlier.

Is there a way to avoid having to fix every reference? We have hundreds.

 

No, this didn't fix the issue. If it's any help, the GUIDs on the files in the CinemachinePostProcessing folder are different than the ones on the same files included in the package for 2.3.3

I also discovered that I get different behavior if I try to do the steps in reverse. After installing CM 2.3.3, if I downgrade CM to 2.2.8 while in 2019.1, put the CinemachinePostProcessing folder back in the project, and then upgrade CM to 2.3.3, the PostProcessing files in the package version will be missing. This feels like a bug, even though it does "fix" the problem, especially given that if I update CM to 2.3.3 immediately after finishing upgrading the project to 2019.1 and without removing the CinemachinePostProcessing folder, the package version will have these files.

 

I started from scratch following the instructions and confirmed that the GUIDs on the package version match the GUIDs on the adapter files I removed. I also checked inside of prefab and scene files for references to this GUID, and everything matches. I still get "The referenced script on this Behaviour is missing" warnings.

I am also noticing that saving VCams into Prefabs with the PostProcessing extension is breaking the prefab system. It is complaining that the extension is not a MonoBehaviour and refuses to save the asset. References to the extension script is removed if you try to save a VCam with this extension into a prefab file. Many of the VCams in the project I'm trying to upgrade are inside of prefab files.

If you try to save a gameobject with a VCam on it that uses the PP extension, the reference will disappear in the prefab editor view. If you try to instantiate the prefab, the reference will be missing. If you load the scene, all references to the PP extension on the VCams will break.

I created a clean Unity project in 2019.1 with the CM and PP packages to confirm this behavior.

 

I tried the first approach (just editing the script) and unfortunately that doesn't work well. I made sure I had write access to the file, I modified the script and sure enough it worked. However when I quit Unity and go back in again, the same bug happens (the PP script turns into a missing script) so it works ONLY for the current session. I had to go back again, edit the file again, remove the bugged script, add them again and then add the profile.

Just thought I'd give a heads up. The second kind of worked but it destroyed all the data on the cameras and our setup so we had to do them from scratch. Also if you at any point decide to stop using the in-game scripts and go back to PackMan's version, you'll have to redo the setup again.

 

Ah, probably Unity being open (I quit it but had a bug report appear so might not have fully exited) while I was moving the packages. Anyway mainly wanted to warn about the first method (with the script edit) that it didn't work for us.

 

Is there an item in the issue tracker for this? I'm eager to update to 2019.1 but I don't trust myself to upgrade Cinemachine manually without breaking everything.

 

Btw, I don't think we can see that page on FogBugz? In either case, looking forward to the patch. I'm eager to get my team onto the new version. Thanks for looking into the issue.

 

Is there any update on this? I cant figure out how to follow the case either, and it has been a few patches and I'm still getting the same problem.

 

Thanks for the update!

 

It doesn't seem to be fixed in 2019.3.0b10.
Do we have to wait for the final version ?

 

I'm also seeing this using 2019.3.0f1, CM 2.3.4 (also tried with 2.4.0 preview 10), PostProcessing 2.2.2 and the workaround you mentioned earlier (https://forum.unity.com/threads/postprocessing-adapter-conflicts-with-cm-2-3-3.664060/#post-4461265)

 

Hey @Gregoryl I updated to Unity 2019.3.0f3 (latest on UnityHub), added post processing to the camera (also tried it on the virtual camera ) and the vignette is not showing in either the game or scene views.

 

Did as you said, added the PP extension, but still doesn't show up.
Some other details: I have a project using the Universal Render Pipeline (with the default UniversalRP-MediumQuality) targeting Mobile.

I thought that maybe it was something with my project settings, but it also happens when I created a new empty project (you can find the empty project here)

 

Hey @gaborkb, thanks for the help. This seems to have done it.
I suspect it might have been the duplicate Post Processing package and maybe something in Cinemachine 2.4.0 as it was released just a couple of days ago.