Dear Jose,
Thank you very much for your last quick response, and for your kind disposition to help us.
I'm sorry to bother you again, but we really need your help.
It seems that we are not doing well in reassigning the new Blueprint to the "Obi SkinnedCloth" component, because after the process the dress behaves as if it were completely flexible (and ends up falling off completely). However, the original blueprint had a rigid zone (with skin radius = 0) and another flexible zone.
![[Image: blueprint_obi2.jpg]](http://www.nexar.cl/dudas/blueprint_obi2.jpg)
Therefore, we wanted to ask you for help with the following questions:
- How could we save the new Blueprint (with the updated properties and groups) in a different file, so that we could open it later? Currently we are only creating it as a memory object.
- What is the right way to reassign the new Blueprint to the "Obi SkinnedCloth" component, and force it to reload?
(As we didn't find the "set" option for the "blueprint" property of the "Obi SkinnedCloth" class, we changed the "m_SkinnedClothBlueprint" property from protected to public, and re-assigned it to the new generated blueprint).
- Currently we have initially deactivated the components "Obi SkinnedCloth" and "Obi SkinnedCloth Renderer", and, in addition, the component "Obi SkinnedCloth" already has in the editor defined the reference to an existing blueprint, which we update with the new values, and after that we activate both components. But it seems that this is not working...
Is there a correct way to pause the Solver, or do we just have to deactivate these components while updating the blueprint, and then reactivate them, in order to force the reading of the new blueprint?
Thank you in advance, for your patience and for your help!
PD: De antemano, le agradeceremos poder recibir su ayuda, pues esto es lo último que nos falta para terminar.
Thank you very much for your last quick response, and for your kind disposition to help us.
I'm sorry to bother you again, but we really need your help.
It seems that we are not doing well in reassigning the new Blueprint to the "Obi SkinnedCloth" component, because after the process the dress behaves as if it were completely flexible (and ends up falling off completely). However, the original blueprint had a rigid zone (with skin radius = 0) and another flexible zone.
Therefore, we wanted to ask you for help with the following questions:
- How could we save the new Blueprint (with the updated properties and groups) in a different file, so that we could open it later? Currently we are only creating it as a memory object.
- What is the right way to reassign the new Blueprint to the "Obi SkinnedCloth" component, and force it to reload?
(As we didn't find the "set" option for the "blueprint" property of the "Obi SkinnedCloth" class, we changed the "m_SkinnedClothBlueprint" property from protected to public, and re-assigned it to the new generated blueprint).
- Currently we have initially deactivated the components "Obi SkinnedCloth" and "Obi SkinnedCloth Renderer", and, in addition, the component "Obi SkinnedCloth" already has in the editor defined the reference to an existing blueprint, which we update with the new values, and after that we activate both components. But it seems that this is not working...
Is there a correct way to pause the Solver, or do we just have to deactivate these components while updating the blueprint, and then reactivate them, in order to force the reading of the new blueprint?
Thank you in advance, for your patience and for your help!
PD: De antemano, le agradeceremos poder recibir su ayuda, pues esto es lo último que nos falta para terminar.