Robert,
All right, thanks a lot for your input!
--
Alexandre Vaillancourt
2015-02-05 4:20 GMT-05:00 Robert Osfield :
> HI Alexandre,
>
> It's a while since I touched the code, but I think with the
> ViewDependentShadowMap the casters also normally need to be a receiver as
> it'll self shadow,
HI Alexandre,
It's a while since I touched the code, but I think with the
ViewDependentShadowMap the casters also normally need to be a receiver as
it'll self shadow, but there may also be the constraint that the actual
rendering of objects is done via the shadow receivers pass. I vagually
recall
Thanks Robert,
The shadow technique being used is ViewDependentShadowMap.
I understand that trying to find where the issue comes from is like
searching for a needle in a stack of hay. I'm trying to figure out myself
how the system is being programmed as I'm not at all familiar with that
aspect of
HI Alexandre,
On 4 February 2015 at 13:23, Alexandre Vaillancourt <
alexandre.vaillancourt.l...@gmail.com> wrote:
> I've been told that objects that were casting shadow were automatically
> set to receive shadows as well, and that it was an implementation
> constraint that was not avoidable.
>
>
Hello,
I've been told that objects that were casting shadow were automatically set
to receive shadows as well, and that it was an implementation constraint
that was not avoidable.
Has this constraint been resolved, making it so that if we want an object
to cast and receive shadows we have to set
5 matches
Mail list logo