2
\$\begingroup\$

After updating Unity to the new 2017.1.0f3 version, I can't see which line in a source file an exception occurred on.

Example: Example

I can't see the source of the error by double-clicking in the console either, which would usually redirect me to the source file in Visual Studio. I can still see exceptions from the Unity and Mono API.

I have managed to temporarily fix it by going to the PlayerSettings and switching "Scripting Runtime Version" from "Stable (.NET 3.5 Equivalent)" to "Experimental (.NET 4.6 Equivalent)".

This happens to all MonoBehaviour scripts.

|improve this question
\$\endgroup\$
  • \$\begingroup\$ What's the number at the right-hand side of that highlighted line? (514) \$\endgroup\$ – Alexandre Vaillancourt♦ Jul 15 '17 at 17:04
  • \$\begingroup\$ 514 lines long script? Looks very scary. \$\endgroup\$ – wondra Jul 15 '17 at 17:55
  • \$\begingroup\$ The number on the right shows how many time the same exception has occurred, and since itoccurs every frame, it shows a large number \$\endgroup\$ – Daniel Jul 16 '17 at 15:02
  • 1
    \$\begingroup\$ This looks like a bug to report via Unity's issue tracker - It's not clear that fellow engine users will be able to solve this. \$\endgroup\$ – DMGregory♦ Sep 16 '17 at 12:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.