Search Issue Tracker
Fixed in 4.3.1
Votes
13
Found in
4.3.0f2
Issue ID
574555
Regression
Yes
"fence == expectedFence" error after upgrading to RC2
Steps to reproduce :
- import the project attached
- open the "Main" scene
- press play and notice the error in the console "fence == expectedFence"
*Note:
Regression from 4.3b3.
Comments (4)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
achilles117
Nov 22, 2013 21:41
Does this mean GPU skinning does not work at all in 4.3? Should this bug be classified as fixed?
asafsitner
Nov 21, 2013 18:34
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. :(
svf
Nov 21, 2013 12:51
I could only reproduce it while using DirectX 11.
Here are some comments in the forum:
http://forum.unity3d.com/threads/210343-Getting-Error-fence-expectedFence-in-4-3/page2
Jarhead
Nov 20, 2013 19:45
This issue seems to be related to GPU skinning. If you disable GPU skinning the errors will go away.