[x3d-public] Shadows

[Michalis Kamburelis]

>From Castle Game Engine / view3dscene side, I can go for "SFfloat
shadowIntensity" with this interpretation too :)

Compared to my earlier proposal "SFBool shadows", the
"shadowIntensity" is obviously more flexible, I can see the
advantages. And with shadow maps, it is easy to support any
intermediate value, e.g. allow 0.5 of the light to reach the surface.

With shadow volumes it's not possible (at least not easily) but then
the implementation can always go with simple Andreas' wording """0
means no shadows, 1 means full shadow.""". We would need to say what
happens for intermediate values in this case, e.g. "if implementation
only supports 0.0 and 1.0, then any value >= 0.5 behaves like 1.0,
otherwise (value < 0.5) behaves like 0.0".

Regards,
Michalis

pon., 5 paź 2020 o 04:49 Andreas Plesch <andreasplesch at gmail.com> napisał(a):
>
> As motivation to make Shadows a high priority for the next version let
> me share Holger's cool idea to use Sponza for shadows:
>
> https://create3000.github.io/media/examples/Navigation/NavigationInfo/example.html
>
> I could adopt it pretty much as is for x3dom:
>
> https://raw.githack.com/andreasplesch/x3dom/scopedLights/test/functional/scopedLights/inline.html
>
> (without the nice ParticleSystem, and with slightly changed
> intensities and locations).
>
> The main required field for both x3dom and x_ite to enable shadows is
> shadowIntensity. 0 means no shadows, 1 means full shadow.
>
> -Andreas
> --
> Andreas Plesch
> Waltham, MA 02453
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org