I'm strictly a Leopard shop on account of my ageing G5s*. Current Position value is evaluating as zero for all iterations when coming from Iterator Values patch inside a 3D Transform patch. When pulled in from level above it spreads 0 to 1 as it should. Likewise for current index values but not demoed in composition.
Simplified composition attached. Perhaps somebody can confirm on SL? If somebody confirms on 10.5 or 10.6 I will log a bug. *(Soon as next-gen intel's are in the MacBookPro I move up a level). On 4 March 2010 02:13, Christopher Wright <[email protected]> wrote: > Has anybody noticed this? I'm not wise enough to know if this is a >> necessity or a bug. If you publish an input to above the 3D Transform patch >> but still inside the Iterator patch and bring the "Position" or "Index" in >> this way it works. If you put an Iterator Values patch inside the 3D >> transform doesn't seem to pass the values. Comp to demonstrate attached. >> > > Have you tested this on 10.5 and 10.6? (I tried it on 10.5, and it seems > to do what you want, which makes me think its a 10.6 regression -- don't > have a 10.6 machine handy to rest right this moment to see if it's > different). > > If the behavior is different, please make a simplified composition that > doesn't use any 3rd party plugins, and submit it with a bug report. > > > -- > [ christopher wright ] > [email protected] > http://kineme.net/ > >
Iterator variables patch inside a 3D Tranform patch is iffy.qtz
Description: application/quartzcomposer
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [email protected]
