I should add; do not place the composition importer patch in an additional
"macro layer" when attempting this or rendering itself gets much glitchier,
and breaks in a worse way than this. This can be seen by taking the previous
attachment, selecting the composition importer and creating a new macro.

-GT

On Mon, Sep 20, 2010 at 9:50 PM, George Toledo <[email protected]> wrote:

> There have already been bugs filed on the fact that the shadow option on
> Lighting cancels iterations created by the iterator.
>
> When looking at the mesh loader/renderer system a few minutes ago, I had a
> kind of mental leap where it occurred to me that it might be possible that a
> QC Composition that uses an Iterator may:
>
> 1: Not "lose it's iterations" when in a Lighting Environment with shadows
> enabled if loaded as a distinct composition via the Composition Importer,
> within that Lighting environment.
> 2: Shadows might actually work with said composition when loaded this way
> as well.
>
> My results are that a composition that uses iteration will indeed continue
> to perform "correctly" in iteration function when inside of a Lighting
> environment with shadows enabled, if loaded with the composition importer.
>
> Further, shadows "sort of" work in a wrong way.
>
> Shadow will successfully happen upon a sprite placed behind a composition
> that uses iteration and is loaded with a composition importer, that reflects
> geometry of the loaded scene. See the attachment where I use the Random
> Nested Iterator, loaded via composition importer, and it creates a "shadow
> grid" on the Sprite placed "behind".
>
> The problems are that it will texture the scene that is being loaded with
> the composition importer with shadow, and also not seem to create shadows
> that are placed as one would normally expect on the Sprite behind the
> Composition Importer renderer. Moving the x/y/z params on the Lighting
> environment should show both the unexpected placement of shadow, as well as
> the incorrect rendering of shadow on the loaded composition.
>
> I report this to the list because it could possibly be of benefit when for
> "some reason" one needed to have an iterated function happening within a
> Lighting environment with shadows enabled, if these visual problems didn't
> matter. Perhaps it may also point to some kind of solution to fixing the
> problem with using iteration and the shadow option in Lighting, if it will
> work in this one scenario.
>
> George Toledo
> [email protected]
> www.georgetoledo.com
>
> The information contained in this E-mail and any attachments may be
> confidential.
> If you have received this E-mail in error, please notify us immediately by
> telephone or return E-mail.
> You should not use or disclose the contents of this E-mail or any of the
> attachments for any purpose or to any persons.
>
>


-- 
George Toledo
[email protected]
www.georgetoledo.com

The information contained in this E-mail and any attachments may be
confidential.
If you have received this E-mail in error, please notify us immediately by
telephone or return E-mail.
You should not use or disclose the contents of this E-mail or any of the
attachments for any purpose or to any persons.
 _______________________________________________
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]

Reply via email to