- General
-
Bugs
0
Fixed
Losing ability to edit curves
We're having trouble finding the spot where this happens, but "over time" we lose access to curve editing in the Director window in our project. In the following image I've created a new cutscene, but this occurs for any cutscene that we load as well.
All of the functionality of adding curves for position, rotation and scaling via inspector still exist, the right mouse menu pops up on the Curve Clip with all available options, but no ability to actually see the curves. Take note that we've installed Pro Cams in our main project as well. Closing and reopening the Director window, the scene, or Unity itself has no effect.
Note that the project in question is in Perforce, should read-only functionality be cramping Cinema Director's style.
When creating a blank project and installing just the unity package, it indeed shows up as normal as the cutscene is created.
All of the functionality of adding curves for position, rotation and scaling via inspector still exist, the right mouse menu pops up on the Curve Clip with all available options, but no ability to actually see the curves. Take note that we've installed Pro Cams in our main project as well. Closing and reopening the Director window, the scene, or Unity itself has no effect.
Note that the project in question is in Perforce, should read-only functionality be cramping Cinema Director's style.
When creating a blank project and installing just the unity package, it indeed shows up as normal as the cutscene is created.
Customer support service by UserEcho
Controls are instantiated by looking up the loaded assemblies and finding the matching control for it's game object. It's possible that the loading of assemblies inside of the DirectorEditor.dll is failing due to Perforce. Does this happen when you load Director into your project locally? You could also try checking out the dll (Cinema Suite/Cinema Director/System/Editor/DirectorControl/DirectorEditor.dll).
Adam has confirmed that it happens outside of perforce (i.e. on his local project which he was using for demoing purposes), after he reloaded Unity a couple of times. I'm going to try to do the same myself, I realize this isn't a lot to go on.
I've loaded up the "Director Basics" scene in our main (p4) project to provoke some errors, the first image is when I try to resize the Curve Clip on the Splash Camera Group:
And here's what happens when scrubbing across the same Curve Clip:
If I can get this issue to reproduce while using a local project I'll be sure to let you know how I did it.
cheers,
b.
Assets/ThirdParty/Cinema Suite/Cinema Director/System/Editor/Controls/TrackControls/ActorCurveTrackControl.cs(12,39): warning CS0436: The type `CinemaCurveTrackControl' conflicts with the imported type `CinemaCurveTrackControl'. Ignoring the imported type definition
I noticed that DirectorEditor.dll has a fully-fleshed out definition for CinemaCurveTrackControl, and for some reason we had a CinemaCurveTrackControl.cs file:
public class CinemaCurveTrackControl : TimelineTrackControl
{
}
Once I removed that source file, the Curves are editable once again!
So the question is how did this get generated? (that's a hypothetical question, I'll be trying to figure out why on our end here). Once Adam gets in on Monday I'll see if this file was generated on his machine as well.
I will confirm this with Adam's build when he gets in on Monday, but at least we know what to look for if this pops up again. I really doubt Unity is generating stubs just to mess with us but stranger things have happened.
Thanks for your attention on this, and letting me talk it out here :)