31-01-2018, 05:45 PM
(31-01-2018, 04:31 PM)izzyschneerson Wrote: Yes, Jose, that is all obvious and i did consider it, but...
i bought the OBI Cloth package for use in an existing (and quite advanced) project... I did not expect a sophisticated package like OBI Cloth to cause such a silly problem.
I need a solution that will allow me to use OBI Cloth in my existing project. If your company cannot provide that, it should warn for that openly in the Asset Store. And it should give me a refund...
Hi,
As I mentioned in the previous post, the solution is to import Obi first, then the StandardAssets.
If you cannot afford to do this and must import Obi in an existing project, an easier solution might be to prevent Obi from importing its own version of the StandardAssets (only used for certain sample scenes). To do so, uncheck the "StandardAssets" foldout in the import popup window when importing Obi:
![[Image: gjm4PAE.png]](https://i.imgur.com/gjm4PAE.png)
We've tested both methods in 2017.3.0f3 with the latest StandardAssets package and Obi Cloth 3.2, it works just fine. In Obi 3.3 we've updated the sample scenes to be compatible with the latest StandardAssets.
regards,