Hi,
Does anyone have any insight on how to debug assertion failures? These normally seem to be unity bugs, and often have very strange reproduction steps and are hard to identity without further information on the problem. Often all you get is "errorA" or " sourcePoint->w > 0.0f" etc...
Is there a way to get Visual Studio to break on assertion failures, or to at least find the source code?
A project which is running on UWP using Visual Studio (2017) and breaking successfully on other Exceptions (in user code) seems to not catch these exceptions or reveal where they are thrown from.
Cheers,
Jethro
↧