>> I am a bit paranoid when it comes to creating a new projection like this
>> on
>> a partition.
>> you are creating new clusters on lots of objects,
>> if you add or remove members from the partition, they will not have the
>> proper projection,
>
> Fair point. So you suggest that if a projection has to be created,
> then it should be done directly at the object level? Since every
> object has its own cluster with its own set of UVs, I would assume
> that partition or no partition should not change anything....
[rob] I dunno if it is a problem, though. We do it a lot here to cheat
motion blur by reprojecting a rgb render via camera projection to a pass.
>
>
>> some objects might allready have a camera projection,...
>
> Is it a problem? I usually name those projections extremely carefully,
> to make sure there is not confusion.
>
[rob] Again I don't see a problem especially if you keep sanity with good
naming.
>
>> If you can try the texture space generator node, set to screen.
>> this way without creating any new projections you'll map the image to
>> screen
>> space.
>
> Ugh.... the camera is moving, I don't want the texture to slide.
>
[rob] Again, camera projs at partition level with branch materials are used
a lot here and we don't see issues (apart from we have to make all ref mods
local). I would guess that it's not that.
At the risk of stating the obvious, Bernard, what do progress reports say?
_rob
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
