Unfortunately, private patches are considered unsupported, so I wouldn't expect to get an answer, unless another user has it figured out.
I will say that in SL, if I place an image in the mask, I don't get an error like that, but rather, QC goes into a state of insanity. If I have an output on the Hit Test connected to an Image With String, and then a Billboard, to test hits, and then connect an image to mask, the actual Billboard connected to the image with string blanks out. Then, at that point, if I restart the Viewer, the Sprite renders twice as large as it's supposed to! If I do it again, it's twice as large as the last time. At that point... I just stopped. The hit test is extremely useful, especially because it works in Z as well as X/Y. QC would be very limited (almost useless?) if there were none of the "private patches", so it would really be nice to see them become something officially supported and documented, instead of being tossed aside in favor of newer, official, features that still don't actually work. -George Toledo On Sun, May 16, 2010 at 7:03 AM, 00:00:01s (dev) <[email protected]> wrote: > Hi List! > > I'm trying to figure out the Mask Image input for the (private) Hit Test > patch in QC3.1. Should I feed it with a special kind of image? > Any image I tried (different color modes, with/without alpha) throws an > exception: > > -------- > 0x954f8692: GFException > 0x954fa2d5: GFThrowException > 0x954b3a3b: -[QCImageManager > createPixelBufferFromProvider:withFormat:transformation:bounds:colorSpace:options:] > 0x954b3966: -[QCImage > createPixelBufferForManager:withFormat:bounds:colorSpace:options:] > 0x9559128a: -[QCHotZone execute:time:arguments:] > 0x95467ae4: -[QCPatch(Private) _execute:arguments:] > 0x95467ea6: -[QCPort _execute:arguments:] > 0x954679f1: -[QCPatch(Private) _execute:arguments:] > 0x95467ea6: -[QCPort _execute:arguments:] > 0x954679f1: -[QCPatch(Private) _execute:arguments:] > 0x95467d73: -[QCPatch(Extensions) executeSubpatches:arguments:] > 0x95467ae4: -[QCPatch(Private) _execute:arguments:] > 0x95466158: -[QCContext renderPatch:time:arguments:] > 0x95465eaa: -[QCGraphicsContext renderPatch:time:arguments:] > 0x95464daf: -[QCOpenGLContext renderPatch:time:arguments:] > 0x95464c4e: -[QCPatch(Runtime) render:arguments:] > 0x0000e352 > 0x954ebd83: -[QCView render:arguments:] > 0x954eb8bd: -[QCView startRendering:] > 0x0000da47 > 0x954eb5eb: -[QCView startRendering] > 0x94e2ef84: -[NSToolbarButton sendAction:to:] > 0x94e2ef15: -[NSToolbarButton sendAction] > 0x94e2e496: -[NSToolbarItemViewer mouseDown:] > 0x94ce8af7: -[NSWindow sendEvent:] > 0x94cb56a5: -[NSApplication sendEvent:] > 0x0000e41d > 0x94c12fe7: -[NSApplication run] > ------------- > > Is this a known bug, or am I doing something wrong? > > Thanks! > > Sebastian. > > > 00:00:01s (dev) > [email protected] > > _______________________________________________ > 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/gtoledo3%40gmail.com > > This email sent to [email protected] >
_______________________________________________ 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]
