Getting Error fence == expectedFence in 4.3?

Getting Error fence == expectedFence in 4.3?

Just downloaded 4.3 and opened an existing project and started receiving the above error in the editor and when the game is running.

Any ideas what a fence is and how to disable it in 4.3?

 

I'm having the same issue, but was able to get a few extra bits to the error logged as follows.

Code (csharp):

1.  
2. fence == expectedFence
3. UnityEditor.DockArea:OnGUI()
4.  

Code (csharp):

1.  
2. fence == expectedFence
3. UnityEditor.AssetPreviewUpdater:CreatePreviewForAsset(Object, Object[], String)
4.  

 

So... is no one from Unity going to acknowledge this? It seams to happen anytime I click a prefab with an animation or if a GameObject has an animation and is playing.

 

Same here

 

A bit more information if anybody (Unity?) can figure it out

fence == expectedFence
UnityEditor.Handles:Internal_DrawCameraWithGrid(Camera, Int32, DrawGridParameters)
UnityEditor.HandlesrawCameraImpl(Rect, Camera, DrawCameraMode, Boolean, DrawGridParameters, Boolean) (at C:\BuildAgent\work\d3d49558e4d408f4\artifacts\EditorGenerated\EditorHandles.cs:758)
UnityEditor.HandlesrawCameraStep1(Rect, Camera, DrawCameraMode, DrawGridParameters) (at C:\BuildAgent\work\d3d49558e4d408f4\artifacts\EditorGenerated\EditorHandles.cs:778)
UnityEditor.SceneView:OnGUI() (at C:\BuildAgent\work\d3d49558e4d408f4\Editor\Mono\SceneView\SceneView.cs:913)
System.Reflection.MonoMethod:InternalInvoke(Object, Object[], Exception)
System.Reflection.MonoMethod:Invoke(Object, BindingFlags, Binder, Object[], CultureInfo) (at /Users/builduser/buildslave/monoAndRuntimeClassLibs/build/mcs/class/corlib/System.Reflection/MonoMethod.cs:222)
System.Reflection.MethodBase:Invoke(Object, Object[]) (at /Users/builduser/buildslave/monoAndRuntimeClassLibs/build/mcs/class/corlib/System.Reflection/MethodBase.cs:115)
UnityEditor.HostView:Invoke(String, Object) (at C:\BuildAgent\work\d3d49558e4d408f4\Editor\Mono\GUI\DockArea.cs:231)
UnityEditor.HostView:Invoke(String) (at C:\BuildAgent\work\d3d49558e4d408f4\Editor\Mono\GUI\DockArea.cs:224)
UnityEditor.DockArea:OnGUI() (at C:\BuildAgent\work\d3d49558e4d408f4\Editor\Mono\GUI\DockArea.cs:661)

 

I'm getting this too.

fence == expectedFence
UnityEditor.DockArea:OnGUI()

 

Same here! Unity's been spewing those since I updated to 4.3. I didn't know about this thread before so I opened this one: http://forum.unity3d.com/threads/21...quot-expectedFence-quot?p=1417415#post1417415.

But it's apparently the same problem. Although I have no idea how to fix this. So much for keeping the console clean...

 

Same issue here. My patience with Unity updates is, to say the least, frayed:

Code (csharp):

1. fence == expectedFence
2. UnityEditor.DockArea:OnGUI()

Code (csharp):

1. fence == expectedFence
2. UnityEditor.AssetPreviewUpdater:CreatePreviewForAsset(Object, Object[], String)
3. UnityEditorInternal.InternalEditorUtility:ProjectWindowDrag(HierarchyProperty, Boolean)
4. UnityEditor.DockArea:OnGUI()

 

Do you mean to say you're a bit... on the fence about those updates?

[SUB]Sorry.[/SUB]

 

I'd be a little more ok with it if the stupid error output anything relevant. At least point us to where it's failing so we can fix it our selves or better report the problem. These internal errors NEED to be more detailed.

 

I'm getting this too.

 

Getting this as well, wonder what should be done to fix it...

 

Yep, here too. No info with the error, it's a pain

 

Same here, It's not a big issue but just too annoying.
I think they just rush this release just for 2D toolkit, and they don't really care much about other stuff.

 

Same problem here.
Is it usual for an official response to lag so much?

 

Thats really not true. Just look at the vast number of changes in the release notes:

http://unity3d.com/unity/whats-new/unity-4.3

Indeed, the fact they have changed so much because they care about it is one possible reason why there are plenty of issues with 4.3.

 

You are the BEST!

 

Any response? I've had the same issue, and also !query->pending

 

Thank you, thank you! I'll be here all week...

 

Same problem here

 

Actually just to be safe I also submitted a bug report about this. It happens in a totally empty scene as soon as I drop a character with an animator on it.

 

Happens to me also. But only if did 'Use DirectX 11'.

Can anybody confirm that it is actually related to DX11?

 

nope, we're using XAML and we also experience this bug.

 

You're right, it doesn't happen in DX9. Only in DX11. Great catch!

 

Lohoris2, I found out that if I deploy using 'Master' or 'Release', I don't get fence == expectedFence error anymore. Looks like it only appear when I choose to deploy using 'Debug'.

 

I am experiencing this issue as well, would love to know what this means.

 

Come on Unity what is a fence and why does unity expect one?

 

Unity have opened up voting for issues. If you would like to vote this issue up here is the link
http://issuetracker.unity3d.com/iss...ls-expectedfence-error-after-upgrading-to-rc2

 

Ok, as per Jarhead that error is related to GPU skinning: http://issuetracker.unity3d.com/iss...ls-expectedfence-error-after-upgrading-to-rc2

And after disabling GPU skinning (in Player Settings) the error does seem to be gone. Why don't we all vote up that bug so it gets fixed?

Update: Hah, Robin you beat me to it...

 

I'll just add that selecting multiple files with animations caused the Unity Editor to crash for me.

Disabling GPU skinning and/or DirectX 11 while selecting ONE animation asset doesn't show the error, but selecting multiple animation assets still crashes the editor.

 

So does GPU skinning not work at all in 4.3? Why is the bug classified as fixed?

 

Probably because the bug has been fixed in the current development build at UT just not released yet, it should be out with the next release.

 

And 4.3.1 is out. It indeed fixes the issue for me!

 

It didn't fix the !query->pending error though...

 

Fixed the issue for me as well!

You can verify it is working by finding the MeshSkinning.SkinOnGPU call in the profiler. It is there with GPU skinning on. When turned off, you do not see that call.

The function is called under MeshSkinning.Update in the hierarchy.