Under review

Crash in Unity 2018.4

Anonymous 2 months ago updated by Peter - Soxware Developer 5 days ago 7

Hello I noticed That Your asset totally crash unity 2018.4.30 . The only way to turn on project again, was removing Umotion folder

UMotion Version:
Unity Version:
Under review

Hi,
thank you very much for reaching out.

I just did a quick test: I've downloaded the latest Untiy 2018.4.32f1 version, created a new project and imported the latest UMotion version (V1.24p01) from the asset store. Everything seems to work fine, nothing is crashing for me. I tested this on a Windows 10 PC.

Can you provide some further information to your issue?


  1. What operating system have you been using?
  2. What UMotion version have you been using? Have you tried updating to the latest version?
  3. When you say "crash", what happened exactly? Have you got any error messages?
  4. Does this issue also happen in a new empty Unity 2018.4 project for you?
  5. Can you provide a minimal project that I can use to reproduce this issue? You can send it to me via the email support form (or request a link to my Dropbox via email if the file size is too big).

Thank you very much.


Best regards,
Peter

Hello

1. Windows 10 64 bit

2. Newest umotion clear install.

3. I tried 3 times during importing assets probably .dll Unity just crash, 

4. Not it works in empty project so it is probably conflic with some other asset, but we are using like 50 asset store asset here so It could be anything.

5.We will see what we can do.

3. I tried 3 times during importing assets probably .dll Unity just crash,


So it happens while importing the asset and Unity closed without any dedicated error message? If that's the case than the problem is somewhere inside Unity's native code where we do not have any access to (no UMotion code is executed at this point). So it might be a bug of the Unity package importer.

5.We will see what we can do.

Thanks, if you find a way to reproduce this at a small scale, let me know.

Best regards,
Peter

I am having this same problem on Unity 2018.4.3f1. When I updated to the latest version of Umotion Unity gets stuck on a crash or infinite loop importing Umotion. If I had stop Unity with ALT-F4 and then reload Unity the same thing happens. I am not able to start Unity and I have to hard stop it with ALT-F4. The only way I can get Unity to work is delete the Umotion folders. I do not have this problem with any other assets. I am currently on Windows 10 Version 1909 OS Build 18363.1440.

Hi,
I'm sorry to hear that you are experiencing a similar problem as the OP. I'm here to help.

Can you please send me the editor log of the crash, it might give us a hint of what is causing the crash? If you want to send it in private, please use the email support form.

I just tried it and in a fresh Unity 2018.4.3f1 project UMotion can be imported without such a crash. Please note that no UMotion code is being executed on import, so the problem must be somewhere outside of UMotion. This might be a bug of Unity's asset import pipeline that only appears under certain configurations or of any asset/package installed in your project that hooks into the asset import pipeline. Please try if importing UMotion in a fresh Unity 2018.4.3f1 project works for you, too. Updating to a newer release of the Unity 2018.4 branch might help in case this is a Unity bug. Updating your packages / third party assets that interact with the import pipeline might help in case it's a bug in their code.

Please let me know if I can help you any further.


Best regards,
Peter

I tested it on a new project and I was able to import Umotion on a fresh new project. This kind of sucks because I do not know how to fix it and I really want to be able to Umotion Pro. I am assuming it is a conflict with some other add in or Unity crashing after so many add ins.

In case you haven't tried, you might want to try this:

1) Inside your Unity project, close any editor windows of third party assets.

2) Close Unity

3) Restart your PC.

5) Open your Unity project and try installing UMotion straight away (without doing anything in between). This might help if the extension that causes the issue is only loaded with an opened editor window.

In case the issue is still happening, checking the editor log (after the crash happened) might give us a glimpse of what part of unity/which asset might be causing the issue. If you want to send it in private, please use the email support form.

Another way to find the cause would be to duplicate the whole Unity project folder. Then remove third party assets that might cause the issue, and try to import UMotion again. If the crash still happens, go on with removing stuff. The last thing you removed before it worked, was most likely the cause.

Best regards,

Peter