More controller boxes?
-
I've been making a model, and recently came to a point where I wanted to be able to change the accel in a joint, by having it controllable. Is it any harder to have things like accel, emitter lifetime, min/ max, max accel or any other things of the sorts controllable through code? Not really that necessary, I'm mostly just wondering if it requires a lot of coding, if it's just changing around a few lines of code a bit, or if it's even possible.
-
I don't think so, you can only enter raw ruby into the boxes. nothing like 0.5-getVar("accel")
-
...I meant: would it be harder to make these boxes also include ruby code, maybe in SPIV, maybe sooner, maybe not.
-
From looking at the scrip it would possible, but I don't know enough of script to do it
. -
Its possible. But each field I make script controllable it dramatically adds to the complexity of the SP3 code. And it slows the simulation. Both of these issues will be fixed in SPIV.
I think the best fix going forward is to set the joint parameters in an onTick (or whatever) event. So rather than having a formula in the accel field instead in onTick (or whatever) you can do something like this:
joint.accel=righty*100.0 joint.min=joint.min+10.0 -
@cphillips said:
Its possible. But each field I make script controllable it dramatically adds to the complexity of the SP3 code. And it slows the simulation. Both of these issues will be fixed in SPIV.
I think the best fix going forward is to set the joint parameters in an onTick (or whatever) event. So rather than having a formula in the accel field instead in onTick (or whatever) you can do something like this:
> joint.accel=righty*100.0 > joint.min=joint.min+10.0Great that'll solve some of my problems.
Advertisement