Thanks Chris, the creation argument of [part_head] in my patch was a little too high to be able to work with [part_render]. Before you came with the little help, I decided not to use that object anymore, because I couldn't get it to work. Now I get the picture, and with this also the use of [part_size].
Many thanks, Yorick 2007/5/13, chris clepper <[EMAIL PROTECTED]>:
Have a look at example 07.render.pd in the particle folder. I don't think size works with lines and points but it does with Geos. On 5/13/07, yp_ < [EMAIL PROTECTED]> wrote: > Dear list, > > I've been playing around with possibilities of GEM particles, and don't > seem to understand the function of the object [part_size]. Or more exact: I > can't manage to create a patch where this object takes any effect on the > output. Could anyone help me out with this? I've searched the archive but > didn't find anything closely related to an explanation of this object. The > reference doesn't help me out either, but maybe I'm not using it in the > right sequence of particle-objects. The [part_info] object does output 10 > for size when I input 10 in [part_size] but the gemwindow keeps showing the > same results as with an input of 1. > > I'm using OSX 10.4.9 > Same (non-)results on Intel as on other macs > > I'm searching for a way to easily get results in between the 1pixel > lines and the filled surfaces when working with particles, to open a > graphical playfield (like the blurry screensavers on macs). I had a feeling > part_size could help me out here, but maybe this object only affects the > gravity, like 'mass' in pmpd? > > Best regards, > Yorick > > _______________________________________________ > [email protected] mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > >
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
