Beginning with 5.6 betas, I noticed whenever I imported some plugin or assets from the asset store I have a compile error and the asset doesn’t load.
This is what I have:
Assertion at …\mono\mini\unwind.c:620, condition `cfa_reg != -1’ not met
Just one line, no info on any line, column or file. Just this, the asset files are there but it’s nor loaded.
This happened when importing the Standard Assets, post-pocess stack, Anima2D, AssetBundle Graph tool and all other asset store packages.
I filed a bug (Case 875075) but I want to make sure it is reproducible and if others have it too.
Could you please file a bug report with a reproduction case as well and reply with the case #? More information on the matter will help resolving it faster.
I filed a bug (Case 894721) Consistent mono compiler assertion error with all C# scripts
And there is also (Case 875075) that I’m following with Audrius from QA Team from time to time.
But both cases cannot be found on fogbugz for some reason (No case was found associated with the ticket).
What happened
Create an empty project, add a C# script, assertion error occurs apparently in Mono and file is unable to be compiled and can’t enter playmode or clear the error from the console until I delete all C# files.
This only happens with C# scripts and not with Unity scripts.
This has been happening since the first beta of Unity 5.6, it’s completely absent from previous versions.
How we can reproduce it using the example you attached
Apparently this depends on the user and machine, for me this occurs consistently across projects, I tried both 32 and 64 bit editors, safe mode, with administrator privilege, reinstalled many times, replaced script with an empty class, without success.
Windows 10 14393.0 64 bit, all betas of 5.6 including release candidate.
Yes, it’s because Unity is using the Mono bleeding edge version (4.8) to compile C# scripts instead of standard Mono, I need to reset this.
Can someone confirm if there was a .Net 4.6 scripting back-end player setting in previous 5.6 beta that is no longer exposed?
I think I may have changed it a while ago.