0 votes
asked in Bug Report by
edited by

Thanks for fixing the exporting and references issue.. But I'm afraid there's another problem.

This now gives a clamp warning and more importantly ALL animations have loop unchecked even animations that are suppose to loop.

Cheers mate!

Aleks

1 Answer

0 votes
answered by Expert (164k points)
selected by
 
Best answer
Hi Aleks,
thank you very much for the bug report. I appreciate that.

You are right, seems like I've introduced a regression by trying to fix the bug that you've previously reported. I'm working on a fix for the next update.

Best regards,
Peter
commented by Expert (164k points)

Hi Aleks,
I've been able to fix the reported issue in UMotion V1.17.

May I ask you to send me a quick email via the email support form? I would like to send you the update to validate everything is working for you, now.

Thank you very much.

Best regards,
Peter

commented by
Man you work hard! I sent the form not sure if it went through as it said there was an error. Email looks like this: a*******@m********s.com
commented by Expert (164k points)
Thanks for sending me the email. I've received the email correctly and am going to send you the update later today.

Best regards,
Peter
commented by
Hey Peter everything is working again. There was a crash with a second export but that's not a  big deal especially considering unity 2019.1 is in beta.

Cheers !
commented by Expert (164k points)
Thank you very much for testing. Did you get a "UMotion detected an unhandled exception" dialog or did Unity as a whole crash/closed? Can you reproduce the crash or did it happen only once?

Best regards,
Peter
commented by
Heres some info:

Windows 10 64bit

FBX binary 2019
Update Existing File
lossless

The crash happens regardless of the settings every second or third export, tried saving/notsaving before export but it didn't make any difference. No dialog from uMotion or Unity.. The Editor crashes and disappears .
commented by Expert (164k points)

Thanks for the additional information.

I've tried the following to reproduce this:

  1. I've created a new Unity project in Unity 2019.1b04 on Windows 10 64 bit.
  2. Imported UMotion V1.17
  3. Opened the example Scene
  4. Loaded the "PickUpAnimation.asset" from the examples
  5. Exported the animation several times (FBX Binary 2019, Update Existing File, Lossless) into the existing RobotKyle.fbx.
For me the editor never crashed. Maybe this problem is related to your specific model? Or maybe some other third party assets or some Unity packages are involved that cause the crash (you could try if the problem also appears in new Unity project to validate that).

You can check Unity's editor log file to get an idea what caused the crash.

Best regards,
Peter

commented by
I will have a look right away and get back to you in a few minutes. I use a clean project for animating with no plugins I have a couple of helper scripts for umotion but I have tried deleting them.
commented by
I only just noticed the awesome "Clear - Keep scene pose".

I can send you the model if you'd like

I sent an email with the log as I don't have much understanding I couldn't find where the crash sits in the log.
commented by Expert (164k points)

Thanks for sending me the log file. This is the last message in the log file (thus might have caused the crash):

Unknown Unity Connect error (400). Please contact support at support@unity.com while processing request "https://core.cloud.unity3d.com/api/projects/5792f803-1e16-4410-8f03-41f7100c6982", HTTP error code 404

.[CEF] Unrecognized Content-Security-Policy directive 'child-src'. in https://assetstore.unity.com/packages/tools/utilities/anti-cheat-toolkit-10395
[CEF] Unrecognized Content-Security-Policy directive 'child-src'. in about:blank
[CEF] Unrecognized Content-Security-Policy directive 'child-src'. in about:blank
[CEF] Unrecognized Content-Security-Policy directive 'child-src'. in about:blank
[CEF] Unrecognized Content-Security-Policy directive 'child-src'. in about:blank
[CEF] Unrecognized Content-Security-Policy directive 'child-src'.in about:blank
[CEF] Unrecognized Content-Security-Policy directive 'child-src'. in about:blank
[CEF] Unrecognized Content-Security-Policy directive 'child-src'. in about:blank
[CEF] Unrecognized Content-Security-Policy directive 'child-src'. in about:blank
[CEF] Refused to load the script 'https://static.ads-twitter.com/uwt.js' because it violates the following Content Security Policy directive: "script-src 'self'  'unsafe-inline' 'unsafe-eval' *.unity.com *.unity3d.com *.cloudfront.net www.google-analytics.com www.googletagmanager.com tagmanager.google.com cdnjs.cloudflare.com d6tizftlrpuof.cloudfront.net *.optimizely.com cdn.heapanalytics.com heapanalytics.com *.adroll.com *.hotjar.com www.googleadservices.com connect.facebook.net *.doubleclick.net *.resonai.com storage.googleapis.com gen-as-admin-int.storage.googleapis.com gen-as-admin-stg.storage.googleapis.com gen-as-admin-prd.storage.googleapis.com unity-assetstorev2-stg.storage.googleapis.com unity-assetstorev2-prd.storage.googleapis.com *.naver.net *.bizographics.com prf.hn *.qualtrics.com". in https://assetstore.unity.com/packages/tools/utilities/anti-cheat-toolkit-10395
[CEF] Refused to load the script 'https://js.adsrvr.org/up_loader.1.1.0.js' because it violates the following Content Security Policy directive: "script-src 'self'  'unsafe-inline' 'unsafe-eval' *.unity.com *.unity3d.com *.cloudfront.net www.google-analytics.com www.googletagmanager.com tagmanager.google.com cdnjs.cloudflare.com d6tizftlrpuof.cloudfront.net *.optimizely.com cdn.heapanalytics.com heapanalytics.com *.adroll.com *.hotjar.com www.googleadservices.com connect.facebook.net *.doubleclick.net *.resonai.com storage.googleapis.com gen-as-admin-int.storage.googleapis.com gen-as-admin-stg.storage.googleapis.com gen-as-admin-prd.storage.googleapis.com unity-assetstorev2-stg.storage.googleapis.com unity-assetstorev2-prd.storage.googleapis.com *.naver.net *.bizographics.com prf.hn *.qualtrics.com". in https://assetstore.unity.com/packages/tools/utilities/anti-cheat-toolkit-10395
[CEF] Unrecognized Content-Security-Policy directive 'child-src'. in about:blank
[CEF] Unrecognized Content-Security-Policy directive 'child-src'. in about:blank
[CEF] Unrecognized Content-Security-Policy directive 'child-src'. in about:blank

According to the log file, Unity tried to request information from "https://assetstore.unity.com/packages/tools/utilities/anti-cheat-toolkit-10395" and that seemed to failed with the error message above. Did you have the Asset Store window opened at the time the editor crashed?

Best regards,
Peter

commented by

I did have the asset store open last night, I might have had it open on another unity project. I just tried exporting with 1 project open and no asset store window anywhere.

If I export current clip only then it never seems to crash, crashes only when exporting all animations (35 animations with about 300 bones on the model) I also forgot to mention every successful export I get 34615 warnings from uMotion. They look like this


Animation curves for the root transform are not exported into the FBX file.

Ignoring component property ".head__eEyesClosed(18)0"' 


I assume those warnings are harmless? 

commented by Expert (164k points)

crashes only when exporting all animations

So it still crashes even when the asset store window is closed? If so, could you send me a Unity project that includes just your model (without textures if you want) and your UMotion Project file (via the email support form)? Maybe it's somehow related to your specific use case.

I assume those warnings are harmless? 

Yes they are (they shouldn't lead to a crash or the like).

 Animation curves for the root transform are not exported into the FBX file.

This means you have created keys on the topmost properties named ("Position", "Rotation", "Scale"). They don't get exported to *.FBX. So to get rid of those warnings, just delete all the keys in those properties.

 Ignoring component property ".head__eEyesClosed(18)0"' 

This indicates that you have some blend shape properties in your model that are also not exported (because they are not supported by *.FBX). Again, deleting all keys in those properties should fix the warnings. You could also just remove the related "Custom Property Constraint" in Config Mode. This will remove the property on all your animations.

Best regards,
Peter

commented by
Hey dude i sent you a email
commented by
Hey mate just thought I'd say I can live with the bug. Its quite predictable so if you cant fix the bug it doesn't bother me, I love uMotion and the crash hasn't changed my opinion.

Soxware Support

Here you get official product support by the developer and the community for all Soxware Products for Unity®.

Post as guest, login via Facebook or create an account.

Ask questions, report bugs or provide feedback. Please use the correct category and always post in english.

For private email support, please use the Support Form to create a support ticket.

Copyright © 2017 Soxware Interactive | All Rights Reserved | Impressum

...