Priority not working?

I'm having a strange issue with the vcam set to the highest priority not becoming live.

In this case, one vcam is set to 0 (VCamMainFloater) and another vcam (TargetingVCam) set to 1, but VCamMainFloater remains live.

The only difference between the two cameras is that VCamMainFloater is a free look camera and the other is a normal virtual camera.




I've upgraded to 2018.2 and I'm using Cinemachine 2.1.13.

I created a simple script to make sure there are no other vcams in my scene. In fact, I'm using this iterator to flip all vcams back to priority 0;

Code (CSharp):

1.  public void DebugVCams()
2.         {
3.             int n = CinemachineCore.Instance.VirtualCameraCount;
4.             for (int i = 0; i < n; i++)
5.             {
6.                 CinemachineVirtualCameraBase vcam = (CinemachineVirtualCameraBase)CinemachineCore.Instance.GetVirtualCamera(i);
7.                 Debug.Log(vcam.gameObject.name + ", Priority= "  + vcam.Priority.ToString());
8.             }
9.         }

Here are the results. I don't understand why VCamMainFloater is live.

 

yes, that's the problem. thank you.

 

I have the same problem and all the vCam are on the default layer which is visible. Is there any other reason why priority not working on highest vcam?

 

No.I'm not using timeline CM track. Another thing is that the wrong vcam is always the lowest vcam in Hierarchy.

 

What version of CM are you using? I'm using ver2.2.8
Do you have debug text on in brain? Yes.
Do you have more than one Brain in your scene? No I have only one CM Brain.

 

What are Near Camera and Far Camera? They are non-CM camera watching other layers.

What vcam to you want to be Live? CM vcam F

What vcam is being Live in its place? SideRoom Hallway VCam

 

In fact I change the vcam F's priority to 11 , the Brain still turns to VCam who's priority is 9 just like Vcam F is inactive but it is certainly enable.
Then I create another new vcam while the game is running ,the new vcam becomes live with priority 10.
If I press solo VCam F becomes live.

I use timeline but I'm sure I never use cinemachine tracks.

 

I also thought it before, after the Priority 9 Vcam is live I made an editor button to print every vcam's prioriry, and the result showed vcam F's priority is 11.So I'm really confused.

 

Code (CSharp):

1.  
2. public void RecoverEnvironmentLevel(Transform pivot, Transform environment)
3. {
4.       if (pivot != null && environment != null)
5.       {
6.             environment.SetParent(pivot.root);
7.             pivot.parent.SetParent(transform);
8.             pivot.localEulerAngles = Vector3.zero;
9.        }
10. }

I found this weird result may have something to do with this method.
Maybe vcam's hierarchy level change will make it ignore current highest priority?

 

Ahem... Any one still having similar issues now? Cos I am...

 

Hello,

I do have a similar issue that is driving me crazy... I'm using Cinemachine 2.7.1 in Unity 2019.4.18 LTS, and it seems my cinemachine brain doesn't always go to the higher priority Cam. It's been happening for a few days I think (maybe after a Unity update), and for example, it regularly stays stuck on my aim cam despite its priority beeing lower than the main one. I "fixed" it by having the priority difference higher (used to be 10 vs 11, changed it to 8 vs 12) and it works somehow better but it's still quite buggy and quite often goes to (or starts the scene with) the wrong cam, despite the priorities being set as intended...
I checked everything you mentionned here, it doesn't seem to apply...

 

Just had this issue with a lower priority camera being active instead of a higher priority one.

More info:

In our game we switch between different Cameras depending on the characters abilities. Previously we were hiding them, but the input was not sent to the hidden cameras during blending (which makes sense), so we opted for a priority system: 0 if deactivated, the actual value if active and let cinemachine brain take care of the active camera.
This created the issue that sometimes cinemachine brain remains stuck in a priority 0, instead of the default camera which has priority 1. This tends to happen when the user dies and we disable any active abilitites and their cameras, while putting for a few frames a WarpBehindPlayer camera (for positioning after respawning).
I'm using Unity 2020.3.15f2 and Cinemachine v2.6.5.​

How I reproduced it faster:

After investigating ways to reproduce it, I came up with a brute-force to reproduce it easily (25%) in my project using 3 camera DefaultCam, CamForBlend, CamSpammer.
I subscribe to the m_CameraActivatedEvent and when CamForBlend is activated I activate on one frame and deactivate on the other the CamSpammer. If sometime during the next x frames I deactivate the CamForBlend at the end of the sequence, the CamSpammer will remain active, even though it has a lower priority.
​

My current fix/hack is:

If I detect that there is no active blend and the current camera has a priority of 0 for 2 frames, I lower it to -1. Unity will detect the priority change and will fix the camera. The weird part is that it goes through the CamForBlend before returning to the default one, as if they had the same priority.
​

 

just sent the small test project.
Thank you for looking into this issue.

 

I know this is an old thread, but I was trying to debug this for a while, until I realized that in my case the CM Brain actually was selecting and using my dialogue camera at high priority, but my dialogue system was setting Time.timeScale to zero, so the camera blend was not taking effect. Answer: CM Brain's "Ignore Time Scale" needed to be set, to allow the camera to move to the right position.