Cinemachine plugin is throwing some errors in console, such as:
“Assets/Cinemachine/PostFX/CinemachinePostProcessing.cs(160,22): error CS0246: The type or namespace name `PostProcessVolume’ could not be found. Are you missing an assembly reference?”
Besides that, Cinemachine editor menu options do not exist. It’s like the entire Unity install has no idea Cinemachine exists. Yet it sits in the Assets folder.
This is a total fail. I can’t even break Cinemachine because it doesn’t show up.
Actually, it’s a lot of assets, including Post Processing, and other asset store assets. They are installed properly but not showing up in the editor at all. Should Post processing be installed from the package manager? The way I understand package manager is that it is for Unity Technologies assets, and not for 3rd-party asset store assets. This seems very unstable to have multiple assets not registering. I was just using these in 2017.3 fine in this same workspace. It’s 2018.1 that is causing the hiccup.
With 2018.1, some assets got moved from Asset Store to Package Manager. Both Cinemachine and Post Processing are Unity assets, and have been moved to the Package Manager. While it is possible to use the asset store versions (perhaps with some hiccups, which are resolvable), we recommend to switch to the Packman versions.
The best way to do that, if you’re migrating an existing project, is as follows:
Open an empty scene in your project (you can just create a new one, no need to save it)
Delete the Cinemachine asset from your project, and all satellite packages (including CinemachineExamples, and the CinemachinePostProcessing adaptor code)
Import Cinemachine from packman. You will then see the Cinemachine menu.
If you need them, import the CinmachinePostProcessing and Example assets from the CM menu.
If you follow this procedure, none of the metafile IDs will change, and your existing project should remain functional, with all the new CM stuff.
It’s likely that an analogous procedure will work with PostProcessing, but I’m not 100% sure. It’s also possible that the asset store version of post will just work.
As always, make a full backup before doing this, just in case.
To test this, I created a completely new project just now, and everything installs fine.
The broken project (that caused me to post this thread) is different only in that yesterday I did a reimport of all assets, using the “reimport” menu item. This was because I was concerned something might have gotten corrupted.
I can submit the broken project as a bug report. My theory is that “reimport” does not work in 2018.1 and breaks some kind of metadata associations in the editor. It’s really screwy, that’s for sure.
Since I’m just starting this particular project, I can go with the completely new project that works. But in my opinion, it’s good for people (or Unity) to note that this could be a bug.
To summarize, the only thing I can point to that was different in breaking the project was doing an asset “reimport” within 2018.1.
For the broken project, I mean that Cinemachine does not show up when installed with packman, but neither does Gaia, NGUI, and many 3rd-party assets that should have menu items.
Do you recommend I submit a complete bug report with a copy of the corrupted project? I’ve created a completely new project and started over because I don’t want to work in a corrupted workspace, and I was just beginning this project anyway. I’m concerned though that this could happen to devs who are in the middle of something.
I had this happen to me actually. I installed from the pack manager cinemachine, and some other assets, did not show up. I removed them, reinstalled, then restarted the project when they didn’t show up again. Somehow it worked itself out, I’m not sure exactly how, but I haven’t tried to reproduce it.
@anon_73193665 i once had a somewhat similar problem with Gaia on windows
It turned out it tried to show it self on a 3th screen/monitor that wasn’t connected any more.
I changed so many things trying to figure out what was wrong im not sure how i solved and fixed it.
My guess is i found out days later when i did install the 3th screen/monitor. maybe this is helpful.
C:/Users/Developer/AppData/Local/Unity/cache/packages/packages.unity.com/com.unity.cinemachine@2.2.0/Runtime/Behaviours/CinemachineStoryboard.cs(85,33): error CS0115: `Cinemachine.CinemachineStoryboard.ConnectToVcam(bool)’ is marked as an override but no suitable method found to override
I got that error after importing from package manager. Any solution?
I’ve just had these errors crop up (on building in VS to attach to Unity) in a project that was working fine a few hours ago. Not sure what I changed, but it would only have been local stuff, no package installs. Tried restarted Unity & VS, no joy. All works fine in Unity itself, I just can’t compile in VS and therefore can’t debug
I removed Asset Store version of Cinemachine and installed Cinemachine 2.2.0 through Package Manager of Unity 2018.2.
Then I got “Cinemachine.Timeline.CinemachineTrack’ is inaccessible due to its protection level” error at my below code line :
Please let me know if there is a way to create CinemachineTrack from script with Cinemachine 2.2.0 .
Thanks
Edit: and also “CinemachinePostProcessing.cs” is missing in the Cinemachine 2.2.0 package. If it’s intended, I’d like to know how to add postprocessing effect to my CinemacineVirtualCamera too. thank you.
