11-05-2020, 08:02 AM
(This post was last modified: 11-05-2020, 08:17 AM by josemendez.)
Blueprints are assets, and their behavior is quite close to that of prefabs: modifying a blueprint at runtime has no effect on existing instances.
When instantiating a blueprint, all per-particle properties stored in blueprint are copied over to the solver arrays. At runtime, the data in the solver arrays is what's being used.
So, no need to mess with blueprints. You could simply set the particle phases of your actors at runtime, using the particle API:
http://obi.virtualmethodstudio.com/tutor...icles.html
Luckily, the actor class has a convenience method for that:
You can see it being used in the ActorSpawner.cs sample script, in the BallPool sample scene: all balls are instantiated from the same blueprint, and their phase set right after instantiation.
When instantiating a blueprint, all per-particle properties stored in blueprint are copied over to the solver arrays. At runtime, the data in the solver arrays is what's being used.
So, no need to mess with blueprints. You could simply set the particle phases of your actors at runtime, using the particle API:
http://obi.virtualmethodstudio.com/tutor...icles.html
Luckily, the actor class has a convenience method for that:
Quote:actor.SetPhase(phase);
You can see it being used in the ActorSpawner.cs sample script, in the BallPool sample scene: all balls are instantiated from the same blueprint, and their phase set right after instantiation.