Hi, i use Unity 5 cloth for animate 2 simple flags but the console show hundreds of red messages like this: [Physics.PhysX] Call to PxCloth::setExternalAcceleration() not allowed while simulation is running. [Physics.PhysX] Call to PxCloth::getWorldBounds() not allowed while simulation is running. and then in few seconds Unity crash, i try with many versions and beta versions but the problem remains, i not found information about this problem, thanks for your help.
possibly is a error only in the 5.6 beta, I cant use now the 5.5 version because i am using the new HDR cam effect, I hope that in the 5.6 final version the problem will be solved but is worrying that this and other problem like de bad update of the motion vectors in moving objetcs looks that have low priority to fix by Unity.
Hi, in the Unity beta 5.6.0f1 published yesterday (i not understand the letter F in the beta version, looks like a RC or final version) the problem (in my case) is complety solved, thanks.
still throws Call to PxCloth::setExternalAcceleration() not allowed while simulation is running on 5.6 release.
When I try to destroy gameobject wit cloth component (or if any of its children contains cloth component) it leads to crash. It happens all the time. Even if I create a new project and add there empty object with cloth component and try to destroy it in script. Absolutely unusable. Shame on you, Unity Team. Unity 5.6 I had to roll back to 5.5.2 I made a bug report hope it will be fixed.
in my case in the 5.6f02 (beta) "PxCloth::setExternalAcceleration() not allowed" problem dissapear but when a cloth have more than 30 the value in Solver Frecuency the game crash, in 5.6f03 (final) all problems dissapear in my game, when i know that some problems have relation with prefabs i use cloth objects duplicated and not use more prefabs for this.
To sum up: 5.4 -> 5.5 : Cloth can no longer be scaled. 5.5 -> 5.6 : Cloth crashes. I see improvement here!
Yeah I can confirm this aswell. You can't have more than one object with cloth without several crashes, also, using the solver below 30 does not make much sense since the simlation is very strange and buggy (at least on my end) Well, anyone knows if there is hope? I'm obsessed =[
I'm still using Unity version 5.5.1f1, the exact issue is happening to me as well. Could this crash have been in the program this whole time? Kind of frustrating... and I'd like to actually use Cloths. Would a fix be rolled back to 5.5 as well?
Sadly in last version 5.6f3 p02 the problem appear again in my project, i am uninstalling this version and installing a old 5.6 version, is really annoying that after many versions this problem continue, and now i have a new problem with the cloth modifier, cloth constrains editor fail and is impossible edit this, constrains points appear and dissapear all time, possibly i need reinstall v5.5 to edit constrains, the Cloth system of Unity make me waste hours and hours that i might use in other things.
I'm using version 5.6.0f3 and I can no longer play my game (In-editor) without crashing right after I stop. If I don't stop, the PC freezes because this the editor creates around 10k errors in seconds. Should I downgrade to another version?
Have the same problem and I have submited at least three bug reports to unity. Can unity technologies give us a reply on when will you fix the bug. The 5.6.0p3 still have the problem. In what version this bug will be fixed?
I submitted a bug to Unity and they said it was a duplicate of that bug. I'm not even sure it was the same bug since mine is different, but they said it was. And, as you can see, it's only fixed in 2017...
Just an update - this tentatively appears to be fixed in 5.6.1, our reproducible test case is no longer crashing instantaneously.
Scratch that - it's no longer occurring in the editor (yay), but is still occurring in built player runtimes.
This seems like an important thing to fix... Still no word on a rollback patch for 5.5 ... I can still add and use Cloth in 5.5.1f1, but deleting it always causes a crash, no matter the solver count or anything. For that reason I am scared to use Cloth entirely due to not being able to remove the Cloth. Disabling the Cloth causes a crash as well. The only solution was to delete the Game Object, which is horrible
Actually the crash happens on more than deletion/disabling. It seems to be triggered almost arbitrarily in our projects - even objects which aren't changing are tripping it.
According to this thread, it will be fixed in 5.6.1p1: https://forum.unity3d.com/threads/unity-5-6-standard-cloth-component-doesnt-works.465068/
Hi, if some of you continue with this problem read the fixed section in the new 5.6.1p1 version (patch 1, this version is in the section patches) in this readme you can see: " (845868) - Physics: Fixed a crash that occurred while updating active skinned Meshes. " then is possible that this problem is complety solved in this version of the 5.6 branch, good luck.
This problem is still occuring when I try to use the add-on iTween on a plane (with cloth component added). Using version 5.6.1f1.
Not fixed. Still happening on ios in Unity 5.6.2f1. Also I tested unity 2017 and again sometimes game crashes when trying to destroy any gameobject with cloth component.
We are using Unity 5.6.3p3 and we get all kind of weird Cloth crashing errors, which we did not get before that. I guess somewhere Unity team introduced the buggy Cloth code again. I did not see any fixes for Cloth in the next few 5.6 patch releases, anybody having the same issues?
Just started seeing this again in 5.6.4 as well. Somewhere between 5.6.1 and 5.6.3pX was quite stable.
Hey guys I just published an app and im seeing it over here as well Screen Shot 2017-12-14 at 10.40.58 AM.png
I am facing crashing issue in Unity 2017.1.1 . I have reduced external acceleration below 30. still facing the same issue any help???
Getting Access Violation crash in 2017.3.0f3 UnityPlayer!Unity::Cloth::ReadBackSkinnedBuffers+0x57 UnityPlayer!SimulateClothingScene+0x1de UnityPlayer!UpdateClothsJob+0x86
Yep crashes here too. For me I just have to look at the component in the inspector and hit play and the unity scene is completely useless and crashes to error log screen. If I reload that project and hit play the error persists without looking at the component. I managed to get the error to go away by loading another scene and hitting play. It seems that clears the error from where ever it's getting cached.