just for completeness: you could also add a script_controller that randomized a vertexcolor chanell based on grid faces and have material that reads …

Cool stuff you are developing here! Georg

yes, I forgot about this fact. having a internal linkage to update the spinnerranges after (re-)selection might be much more work. Though we could sto…

couldn’t you just do the range adjustment like Paul mentioned some threads before: [path_to_spinner].range = [newmin, newmax, 0] ? I must admit I d…

not sure if this is related, but I had problems setting spline knotpoints by a customAttribute function. I ended in baking the spline animation with s…

n ode ? … where does this code get loaded into the system ? … well, my pflow-lights-hack is a hack and not really an end-user-plugin. You need to…

With particleFlow-Node selected: $.lightData.params.lightNum.range = [0,1000,200] where [min, max, default]. Hope this helps, Georg

hm. You only have a scene where this is part of pflow? Then it might be $pflow.[path_to_custom_attribute].lightNum.range=[0,1000,0] But this is onl…

cool! (message is too short)

cool, somebody really uses this! The 100 is currently hardcoded in the setup script: spinner lightNum “Number of Lights ” range:[1, 100, 10] type:#i…

Or maybe even postprocess your vrml file with python.

you can use a script-controller to call the function. But this might be ending slow. Georg

Hi Harry, I think the problem is the (missing ?) accumulation of rotations in your script. You just check for the difference between past and future….

Looks funny and usefull the same time. Can you upload it at scriptspot? I will probably forget to download it in 95 min, when rapidshare allows it aga…

Any ideas? You could add a button to pick the base grid and another to pick the object/a group of objects to be instanced to the points. But this w…