Hello. I updated Vuforia earlier today to work with Cylinder targets and have been having some major problems ever since.
The problem occurs after I've changed code in MonoDevelop. What normally happens is I'll make my code changes, switch back to Unity, then all the scripts will compile automatically and I can press the Play button and run. However, since this update, that is turning into a major issue. Now, when I switch back over to Unity after changing code one of two things happens either A) Unity immediately crashes and brings up a bug report or B) Unity will get stuck in compilation. This is represented, since I'm OSX, as the spinning beach ball. Either way, I cannot get ANY code changes to reflect without having to restart Unity.
Now this is a major holdup because I can't go through the process of force quitting and restarting Unity every time I want to make a change. I'm not certain if the actual crash/hang up is during script compilation or asset importing, but as of right now I can't make any changes without a force quit and reboot. Please help, we need this cylinder stuff in the new SDK right away.
Thank you-
Mike
- Development OS (Mac OS X, Windows, Linux): OSX - Mobile OS and Version: not relevant - Mobile Device Manufacturer and Model name: not relevant - Do the Vuforia Sample Applications show the same behavior?: I haven't changed any of the samples.
Unity 4.2 Crashing After Every Code Change With new Vuforia SDK
Just a heads up I noticed that the last shared line between a successful compile and an unsuccessful one is this:
Begin MonoManager ReloadAssembly
Unity 4.2 Crashing After Every Code Change
UPDATE:
Unity 4.2 Crashing After Ever Code Change
Which scripts are you modifying when the crashes occur?
Does this occur when modifying non-critical scripts, like the CameraDeviceMenu.cs?
Did you maintain an earlier installation of Unity that you can work with?
Unity 4.2 Crashing After Ever Code Change
I've seen this happen when modifying any script in the game, including my own new scripts that are specific to the game. However, this does tend to happen more often when modifying a script like DefaultTrackableEventHandler.cs or QCARBehavior.cs.
Unity 4.2 Crashing After Ever Code Change
The problem occurs after I've changed code in MonoDevelop
Unity 4.2 Crashing After Ever Code Change
I've been working with Unity for a while now and haven't seen anything like this before. In fact, the Vuforia packages are the only plugins where I can even see the Unity popup telling me that it's compiling.
Unity 4.2 Crashing After Ever Code Change
We're pursuing this issue on our side as well and will update this thread with any info we gather.
Unity 4.2 Crashing After Ever Code Change
I find some solve this problem which help me. When you save script in MonoDevelop, make sure that no objects are selected in Unity3d and after save refresh you script in Inspector by press 'Reset' menu. I think it problem with sync Inspector and MonoDevelop.
Unity 4.2 Crashing After Ever Code Change
I've confirmed that islavik777's advice works for me as well.
Unity 4.2 Crashing After Ever Code Change
I am experiencing the exact same issues using Unity 4.2.0f4 with Vuforia 2.6.7
Importing Vuforia into a blank project causes compile time to increase from instantaneous to ~5-10 seconds, even with very slight script changes.
Unity 4.2 Crashing After Ever Code Change
Unfortunately I have to agree with MerlinMo here. Even if I have no GameObject selected in my heiratchy I still get Unity to crash. It DID compile a couple of times but went back to crashing every time soon after.
Unity 4.2 Crashing After Ever Code Change
OK just a quick update for a workaround that so far has worked.
1) Go to Unity->Preferences->General and turn off Auto Refresh
2) Update code in MonoDevelop normally.
Unity 4.2 Crashing After Ever Code Change
Thanks Mike for this great tips, if I may just slightly correct the procedure:
Unity 4.2 Crashing After Ever Code Change
Thanks for the workarounds! This issue has been bugging me for weeks.
I noticed that It does only occur on my Windows PC, not on the Mac!
Unity 4.2 Crashing After Ever Code Change
@jank, I can't confirm this. to me it happens on a MBPr constantly.
The strange thing is, that I have 2 almost identical machines (one at home, one at work) and just one of them seems to crash constantly, while the other one doesn't at all.
Unity 4.2 Crashing After Ever Code Change
I cannot tell for sure yet, but chances are that this bug will be fixed in the next 4.2.1 release of Unity.
Fingers crossed!
Unity 4.2 Crashing After Ever Code Change
I am in touch with Unity and they are aware of the issue, but so far to my knowledge this has not yet been resolved successfully.
N
Unity 4.2 Crashing After Ever Code Change
I can definitely confirm that it's happening on a MacBook Pro because that's the exact machine I'm using heh. Sounds like it could be inonsistent between computers but once you have the problem it's there to stay.
Unity 4.2 Crashing After Ever Code Change
Not fixed for me in 4.2.1f4.
Although something seems to behave differently when importing, it still freezes.
Unity 4.2 Crashing After Ever Code Change
Thank you for the info, this bug was actually the only reason I was going to try an update so you've saved me the time heh.
Unity 4.2 Crashing After Ever Code Change
Nope, 4.2.1 is just as bad. Worse when importing assets it seems. My newly installed 4.2.1 has crashed 8 times today alone.