- Home /
Error : * Assertion at ..\mono\mini\unwind.c:616, condition `cfa_reg != -1' not met
Help Me Guys I Just Updated To Unity 5.6 And This Error Pops Up Every Second! I Can't Play test Please Help Quickly!
The Error is : * Assertion at ..\mono\mini\unwind.c:616, condition `cfa_reg != -1' not met
Guys does Reinstalling Fix This Error? Or Still No Hope?
$$anonymous$$ee to please we need some help I have a school project I must finish
That makes three of us, I guess you still have this issue. Can we get on Skype the three of us to try to sort this out?
Answer by Rabee_Kiblawi · Apr 01, 2017 at 09:22 PM
I found the solution , Go to control panel > region > Administrative > Change System local > change it to English (US )
I'll be damned, you indeed found the solution sir. BRAVO!
Totally works! thank you!
but how did you know that?
I cannot find where is the control panel could someone guide me please thanks.
Answer by RobAnthem · Dec 29, 2016 at 08:28 PM
You have a file in a folder called mono/mini/unwind.cs, at line 616 of this file, you are throwing an error. The var cfa_reg is not meeting the required condition of being NOT -1. I.E., cfa_reg probably either doesn't exist, or is greater than, or less than -1.
I don't know, its referring to a C class file that I would need to see to help you fix. C has literally nothing to do with Unity, it was built using C++, and provides scripting wrappers for C#, Java, and UnityScript. It is more than likely some sort of plugin you are using that is causing the error.
interesting..........i might look into my plugins and check what's causing the error
The unwind.c file is part of the mono framework. It's basically a stack "unwinder" which is most likely used when it needs to perform a stacktrace. Here's a link to the current source file of the mono framework. Note that the line number has moved slightly since Unity uses a quite old mono version.
From that assert we can't say anything about the origin of the actual problem. Asserts are usually safety nets which indicate an unexpected state. The cause of this could be anything unless you are familiar with the source code of the framework ^^. Asserts are usually the result of a bug of some sort.
An assert basically is a way to say: "whenever i get to this point a certain state has to be met, if not we can't continue". Again: asserts are not "normal exceptions". Their condition should never be false. If it is it usually indicates either an oversight of the programmer(s) or some sort of corrupted data / code.
so, i know is there'sn't any fix?
i tried : Rebooting, Re-Writing All $$anonymous$$y Game Script (877 script! c# & js), deleting and re-installing unity 95 times in one day!, re-creating my game from scratch,
Nothing WOR$$anonymous$$S!
now it switched form line 616 to 20? what the hell how am i supposed to continue my development? (switching to UE4 until this's fixed! )
Answer by alsharefeeee · Apr 02, 2017 at 12:14 PM
Guys please vote on this issue we need unity to solve it:
https://issuetracker.unity3d.com/issues/compile-error-each-time-i-load-a-custom-package-or-plugin
Here is the forum link for it: https://forum.unity3d.com/threads/what-is-this-cfa_reg-1-not-met.462693/#post-3005873
Answer by Andrew915 · Mar 08, 2017 at 02:53 PM
i have now the same problem in some computers and other works fine , i don't know if it is a bug in the framework that unity5.6 works on or something similar to that ,
Computers that unity5.6 works on is running windows10 Computers that unity5.6 doesnt work on is running 8.1 and windows 7
No, i used to run unity on win7 64bit and win8 and 8.1 it's not a os problem!
Answer by xCyborg · Mar 23, 2017 at 02:32 PM
Thank goodness I'm not the only one, I've been banging my head against this for months now, bookmarking this post.
If anyone made a breakthrough let's post here.
Good luck.