I frequently test changes to object variables in play mode and therefore have come to take it for granted that I can experiment without fear of breaking anything. So, I find myself breaking things quite often with Cinemachine. The “no need to write settings down” selling point goes out the window if you’re like me and constantly forget that Cinemachine breaks the rule everything else follows in play mode.
I appreciate the value of changing shots within their context. So, I’d still like to see it as an option. But, more often than not, I’m just testing potential changes to the player’s free look camera. Generally, when I want to save changes I made in play mode, I copy the component and then paste component as values after stopping.
On a somewhat related note, I’d really like an option to disable the shot editing lines that show up on the game tab. The whole view becomes a minefield when testing free look settings in play mode, requiring constant selecting of some other object in the hierarchy to avoid moving the guides. And, when I’m tweaking settings, I just want to see the game view as it actually is—without a filter and a bunch of lines—so that I can make informed decisions based on what the player—not the camera—sees.
The FreeLook screen guides are much improved too, they just show the guides of the most prominent of three cameras, depending on where you are vertically in the blend. IE if you’re at the bottom, the guides will just show for the bottom camera, etc.
I often find myself reloading scenes just to make sure my setup won’t break (runtime changes break it easily and often). I think this probably should be disabled as a default just not to confuse people.
I agree with it being disabled by default as well. I just had to track down a bug caused by code setting recenter wait time on a free look in play mode. Turns out, it was saved. This is the sort of bug—one that can originate from any piece of code and affect anything else anywhere else—that makes programming frustrating.
Thanks for your input @andrew-lukasik , @OhiraK. We know this is a passionate topic with plenty of good arguments either side. Even Gregory and aren’t totally aligned on it!
My concern with off by default is that there’s super low discoverability. The toggle is hidden away and artists won’t know to look for it. Are more people charmed that their in-play tweaks are saved VS those who find it a nuisance?
Typically, those with save-in-play issues will search for it, hit the forums and find a solution. Nobody searches for ‘camera system where I can save in play mode’ so I’m leaning to it being on and those who have issues will get a solution in 15 seconds if they search for it.
Solid point about discovery. I’m more of a “first, do no harm” and “when in doubt, be consistent” kind of guy, but I certainly appreciate the thought put into it.
I don’t see the option for saving tweaks in playmode, and it doesn’t seem to save them, which is making things very difficult indeed Any ideas how to get this behaviour back?
Any ideas how to get this behaviour back?