[x3d-public] visibilityRange for X3DFogObject: specification erratum detected

[Brutzman, Donald (Don) (CIV)]

Andreas and Holger, thanks for these important catches.  Certainly the
upper-bound limit should be positive infinity, not minus infinity.

 

Dick, please let's discuss whether there is any way to remove these
typographical errors while in final stage of ISO editorial review.

 

Andreas, if you have suggested prose for "explain that fogVisibility
corresponds to the visibilityRange field" then please send that.  We can at
least create a Mantis issue for eventual resolution.

 

Thanks everyone.

 

all the best, Don

-- 

Don Brutzman  Naval Postgraduate School, Code USW/Br        brutzman at nps.edu

Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA    +1.831.656.2149

X3D graphics, virtual worlds, navy robotics https://faculty.nps.edu/brutzman

 

From: x3d-public <x3d-public-bounces at web3d.org> On Behalf Of Holger Seelig
Sent: Tuesday, October 17, 2023 9:21 AM
To: Andreas Plesch <andreasplesch at gmail.com>
Cc: X3D <x3d-public at web3d.org>
Subject: Re: [x3d-public] visibilityRange for X3DFogObject

 

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/Pa
rt01/components/environmentalEffects.html#LocalFog

 

--

Holger Seelig

Leipzig, Germany

 

holger.seelig at yahoo.de <mailto: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
<mailto:andreasplesch at gmail.com> >:

 

https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-IS.proof/Pa
rt01/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/Pa
rt01/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/Pa
rt01/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 <mailto: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/20231018/19051569/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5464 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20231018/19051569/attachment-0001.p7s>