01-06-2020, 07:50 PM
(This post was last modified: 01-06-2020, 07:51 PM by josemendez.)
Hi there!
You're getting the constraints from the blueprint, not the actor, at runtime. Blueprints are assets, and they work just like prefabs: once you instantiate a blueprint, the instances (actors) are no longer "tied" to it. So changing a blueprint at runtime will only affect all instances created from that point on, existing instances will be unaffected. See:
http://obi.virtualmethodstudio.com/tutor...cture.html
Step #2 of what happens when an actor is added to the solver is key here:
So do the same, but this time get the constraints from the actor instead (rope.GetConstraintsByType()).
You're getting the constraints from the blueprint, not the actor, at runtime. Blueprints are assets, and they work just like prefabs: once you instantiate a blueprint, the instances (actors) are no longer "tied" to it. So changing a blueprint at runtime will only affect all instances created from that point on, existing instances will be unaffected. See:
http://obi.virtualmethodstudio.com/tutor...cture.html
Step #2 of what happens when an actor is added to the solver is key here:
Quote:The actor makes a copy of all constraints found in the blueprint, and updates their particle references so that they point to the correct solver array positions.
So do the same, but this time get the constraints from the actor instead (rope.GetConstraintsByType()).