[x3d-public] visibilityRange for X3DFogObject

[Holger Seelig]

There is also LocalFog derived from X3DFogObject, it has the same issue:

lists limits for the visibilityRange as 0 to minus infinity, for the
abstract node.

https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-IS.proof/Part01/components/environmentalEffects.html#LocalFog

--
Holger Seelig
Leipzig, Germany

holger.seelig at yahoo.de
https://create3000.github.io/x_ite/

> Am 17.10.2023 um 16:26 schrieb Andreas Plesch <andreasplesch at gmail.com>:
> 
> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-IS.proof/Part01/components/environmentalEffects.html#X3DFogObject
> 
> lists limits for the visibilityRange as 0 to minus infinity, for the
> abstract node.
> 
> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-IS.proof/Part01/components/environmentalEffects.html#Fog
> 
> list limits for the visibilityRange as 0 to plus infinity, for the
> concrete node.
> 
> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-IS.proof/Part01/components/lighting.html#t-foginterpolant
> 
> assumes a positive visibilityRange (and probably should explain that
> fogVisibility corresponds to the visibilityRange field).
> 
> So I think the abstract node also should list 0 to plus infinity as
> limits (unless there are historical reasons).
> 
> This is not critical for implementations since Fog is the only
> concrete node inheriting from X3DFogNode but should be addressed.
> 
> Apologies if this is already addressed in the very latest versions.
> 
> -Andreas
> 
> -- 
> Andreas Plesch
> Waltham, MA 02453
> 
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20231017/96ba0dba/attachment.html>