Author Topic: Unity crash on script compile if playmode on  (Read 3793 times)

Baburo

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 3
    • View Profile
Unity crash on script compile if playmode on
« on: October 29, 2013, 04:08:35 AM »
Hi.
First of all, thanks for the latest additions to NGUI, I'm loving the post 3.0.0 features.

So, I updated our project from 2.x.x version to the latest 3.0.3c and I do realise that it's not a stable version but I wanted to report this bug if it was not known yet.
Previously I had no problems with leaving the play mode on while I edited my scripts. And when I was done editing, I would return to Unity, stop the play, and press play again to test new changes.
But after the 3.0.3c update Unity crashes every time I do this.

Of course it would be smart to stop Unity before changing the code but I guess the habit of leaving the play mode on while looking(and editing) the code, is buried way too deep into my brain because I've had 10 crashes already this morning.  :-[

Cheers.

Edit: And to be exact, Unity does not crash on the "Compiling scripts" phase, but a phase after that, which seems to just flash so quickly that you don't have time to see what it is.
« Last Edit: October 29, 2013, 04:13:39 AM by Baburo »

ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: Unity crash on script compile if playmode on
« Reply #1 on: October 29, 2013, 04:27:53 PM »
Are you sure 3.0.3 caused this? I highly doubt it. A Unity version update might -- going up to 4.3 beta for example. I've never seen any issues, and I modify functionality at runtime all the time. You need to test it in a clean project with only NGUI on, and if you still encounter it, let me know the steps so I can reproduce it.

Baburo

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 3
    • View Profile
Re: Unity crash on script compile if playmode on
« Reply #2 on: October 30, 2013, 03:28:51 AM »
I guess I need to check it further then. But this started occurring when I updated NGUI to 3.0.3 so that's where I drew my conclusion. I'll try and test it out with a clean project and come back to this.