# Assets often break when imported to open project

**URL:** <https://forums.unrealengine.com/t/assets-often-break-when-imported-to-open-project/377180>\
**Category:** World Creation\
**Tags:** arrays, physx, open-project, unreal-engine, question\
**Created:** [November 23, 2016, 1:30am UTC](https://forums.unrealengine.com/t/assets-often-break-when-imported-to-open-project/377180 "2016-11-23T01:30:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![unit23](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/unit23/32/1146013_2.png) [@unit23](https://forums.unrealengine.com/u/unit23)\
**Post date:** [November 23, 2016, 1:30am UTC](https://forums.unrealengine.com/t/assets-often-break-when-imported-to-open-project/377180/1 "2016-11-23T01:30:30Z")

</div>

Assets which are added to a project in UE 4.14, break in various ways.

**Case A**  
For instance the FaunWarrior from the market store breaks his PhysX cloth when migrated from a 4.13 to a 4.14 project. Asset not yet upgraded.

**Case B**  
The OldVillage pack from the market breaks all assigned mesh arries from the Blueprint folder when content was imported to an open project.

Probably affects all PhysX models, and they are rare.

 ![116033-faunissue.jpg](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/7/f/27f9892182a4082fca9164637dd8543f475f7fee.jpeg)

While Case B can be circumvented with importing while the target project is not open, the PhysX asset breaks in both cases.

---

<div class="post-metadata">

**Author:** ![MGGeymonat](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/mggeymonat/32/1115483_2.png) [@MGGeymonat](https://forums.unrealengine.com/u/MGGeymonat)\
**Post date:** [November 23, 2016, 2:56am UTC](https://forums.unrealengine.com/t/assets-often-break-when-imported-to-open-project/377180/2 "2016-11-23T02:56:07Z")

</div>

I can confirm the cloth sim error has been happening to all my characters (using apex cloth simulation) in 4.14, I’ve tried updating my maya physx plug-in and re exporting the clothing asset and the meshes into unreal, but the issue remains.

Also just to clarify the error seems to be that simulated vertexes with 0 weight (so they just deform from skinning) are sticking to the world origin for some reason.

---

<div class="post-metadata">

**Author:** ![unit23](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/unit23/32/1146013_2.png) [@unit23](https://forums.unrealengine.com/u/unit23)\
**Post date:** [November 23, 2016, 1:23pm UTC](https://forums.unrealengine.com/t/assets-often-break-when-imported-to-open-project/377180/3 "2016-11-23T13:23:54Z")

</div>

Noticed there is a new feature for Apex clothing, see the news here, and the option is in the mesh panels, [4.14 Released! - Announcements - Unreal Engine Forums](https://forums.unrealengine.com/showthread.php?128759-4-14-Released)!

Ignore this comment, if you’re already aware.

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_280dd372](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_280dd372](https://forums.unrealengine.com/u/anonymous_user_280dd372)\
**Post date:** [December 1, 2016, 6:18pm UTC](https://forums.unrealengine.com/t/assets-often-break-when-imported-to-open-project/377180/4 "2016-12-01T18:18:06Z")

</div>

Are both of you using marketplace assets?

If so, please try contacting the creator and if they cannot resolve the issue, please email [marketplace-support@unrealengine.com](mailto:marketplace-support@unrealengine.com)

-

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_280dd372](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_280dd372](https://forums.unrealengine.com/u/anonymous_user_280dd372)\
**Post date:** [December 13, 2016, 6:37pm UTC](https://forums.unrealengine.com/t/assets-often-break-when-imported-to-open-project/377180/5 "2016-12-13T18:37:17Z")

</div>

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will follow up.

-
