Hello all. Right now I'm playing around with taking an image and mapping it to a series of objects using two iterators to lay out a grid. You can see what I've done with it so far here: http://www.andrewohlmann.com/?p=273. The image is resized before it enters the iterator— a 1024 object plot comes from a 32x32 image. At that resolution, I can put the composition in a trackball and enjoy a reasonable framerate. A problem happens when I go higher though, whether I use spheres, sprites, or Kineme GL Points. A 33x33 pixel image (with 1089 objects) makes the rendering time skyrocket. You can see the result here: http://imgur.com/w1My8.png
Am I butting up against a weird cliff-like limitation of my graphics card (early 2008 macbook x3100, 144 mb iirc) or is this a problem with Quartz/iterators? Or maybe my computer? I've never encountered behavior like this before. Thanks.
_______________________________________________ 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]
