Official Introducing Cinemachine 2.7.1 (and 2.7.2)!

Hello friends!

We're delighted to announce that Cinemachine 2.7.1 has now been officially published to Package Manager.

Note that 2.7.1 has not yet been verified, so approach it will appropriate caution. The 2.7 series, which will be the verified version for the upcoming 2021.1 and backwards compatible as far as 2019.4, includes some nice improvements which I'll detail below. You can read the complete changelog here.

To add Cinemachine 2.7.1 to a project, open the Package Manager (Window > Package Manager), find Cinemachine in the list, and click Install on 2.7.1.



To add to a project that currently contains Cinemachine, open the Package Manager (Window > Package Manager), find Cinemachine, and click Update to 2.7.1.

In either case, don't forget to check out the included Samples to see what Cinemachine can do!

Changes from 2.6.3 to 2.7.1

The first change - which might alarm you! - that you'll notice right away is that the Cinemachine menu has vanished. Fear not, the functionality isn't gone; we're simply giving you back some top-level menu real-estate, and integrating Cinemachine more directly into traditional Unity workflows. Cinemachine objects are now created just like any other GameObject: from the GameObjects menu (and in all the other places that GameObjects are generally created).





Next, we've introduced a new and improved 2D confiner. CinemachineConfiner2D provides a way for the user to limit the camera into an area defined by a polygon. This is useful for ensuring that the camera moves only in ways that properly support your game.

The new confiner has a number of advantages over what came before. It's faster, and better at dealing with damping in corners and undersized behavior (camera window is bigger than the original confining area). It also works with both Orthogonal and Perspective cameras.



Note that the confining area may not be precise everywhere due to computational costs, but it will be a close approximation. This is expected at edges that are not perfectly horizontal or vertical. Moreover, the extremities of acute angles may be hard to reach.

The next big items are a pair of often-requested lens improvements, allowing Cinemachine to control and report on more aspects of how the Camera behaves.

• The Virtual Camera Lens can now override orthographic and physical camera settings.

• The Virtual Camera Lens inspector now respects the display of Horizontal FOV from the Camera.

Finally (and not counting the usual batch of bug fixes), you'll find a new option in the ImpulseListener called ApplyAfter. This allows you to choose whether a confiner also confines impulses and noise.




As always, we hope you get great use out of the new version and all these improvements. If you have any questions, problems, complaints, ideas, or praise, don't hesitate to post in this forum! We always love to hear from our friends and users.

[EDIT]
We just released 2.7.2 with some incremental improvements.

Improvements to the new CinemachineConfiner2D, some new samples, and a list of bug fixes.

Details in the release notes.
[/EDIT]

 

Thanks very much for the report @voyagecreations and welcome to the forum! In general, we recommend you create a separate thread for a support request. Putting all 2.7.1 support questions in this thread will get messy very fast. That said, I'll ask the team to investigate.

 

@voyagecreations , can you please look at this thread:

https://forum.unity.com/threads/cinemachine-2-7-1-dolly-camera-with-track.1011802/

Thank you.

 

https://forum.unity.com/threads/introducing-cinemachine-2-7-1.1010914/
See the "Changes from 2.6.3 to 2.7.1" section part-way down the post.

 

Well, we only test on the LTS version of 2019 so no guarantees, but my gut feeling is that you should be ok.

 

It's not obvious that the errors are from Cinemachine. The one you quoted is not.

It sounds as though your project got corrupted somehow, possibly because of import problems. You may have installed some mutually incompatible packages.

The first thing to try is Reimport All. If that fails, then we can look at the package manager to figure out which packages you don't need.

 

If your game is taking place on a plane, draw the confiner on that plane. If the camera's local Z axis is normal to that plane, then the camera's view will be confined correctly to the drawn shape. If the camera is looking obliquely at that plane, then results will degrade but can still be usable.

What are you finding to be difficult about drawing the shape?

 

Can you show an example of this? We recommend setting the Damping parameter to non-zero (0.5 is nice) so that you don't get snapping in corners.

 

Can you clarify? It's not clear from your picture. How is it off?

 

You are not wrong. Can you show me the full inspector for your vcam?

 

This is a clue:



Can you lower the FOV of the vcam until this warning goes away?

 

For best performance, you should set the Max Window Size to the largest window size you expect to have. For perspective cams, Window size in this context means how big the camera window would be on the confiner plane.

 

@Anhella have I got a video for you!

 

@Lars-Steenhoff sorry, I think I missed your question. You want to change the look of the gizmo? I think you'll find what you're after under Packages/Cinemachine/Gizmos.

 

@Anhella

I think you'll get more help on your support questions if you open them in a fresh thread and provide more specific detail. This thread is really about the 2.7.1 release.

@Lars-Steenhoff

I'd suggest that maybe the same would be helpful for you as well (a dedicated thread). I've checked and I guess you're right...it seems like the icon is resistant to change, though I'm not immediately sure why that is. Possibly something to do with package integrity. Anyway, if you ask in a new thread, I suspect one of our engineers will be happy to explain.

 

Yes, packages are read-only, and Unity magically undoes any changes you make to them. You can customize a package by first embedding it into your project (copy it from the package cache to you project's Packages folder), then changing it.

 

Please start a new thread by pressing this button:

 

Whew, it's getting a bit crowded in here! We've created a new read-only thread for release announcements here. Please create new threads for feature requests, bug reports, or general discussion. Thanks!