[x3d-public] X3D meeting agenda 18 FEB 2022: SpotLight angles, Volume Rendering component

[Michalis Kamburelis]

Vince,

Sure, we can go over view3dscene nodes. Reading your links, I can
submit these corrections:

Looking at view3dscene nodes listed on
https://docs.google.com/spreadsheets/d/1jXu52t7_5kdQY8CtEJBM8oU6PxzwQz93/edit#gid=140823416
:

1. We have support for these nodes (they miss "x" in the respective column):

  Collision
  ComposedShader
  FloatVertexAttribute
  NurbsSet # though that's a bit unfair, and we just don't do (because
we don't have to) do anything to support this node

2.  We do not (and never did) support these nodes (their "x" in the
respective column should be removed):

  PackagedShader
  ProgramShader

3. In your description on
https://drive.google.com/file/d/1Ka1lR9laQiMPitRQWj3HULU2CKHqPFKF/view?usp=sharing
, I suggest these edits:

- Linus Desktop -> Linux Desktop :) We don't usually call it "Linus'
Desktop" unless someone wants to praise Linus Torvalds in this
imprecise way :)

- We also support macOS, albeit it often lags in official releases.

- "scripting uses the CastelScript language" -> while this is true for
view3dscene, I would say more: "view3dscene allows to specify scripts
using CastleScript https://castle-engine.io/castle_script.php . Castle
Game Engine additionally allows to write code in Object Pascal that
interacts with X3D and other models."

- "CGE supports 3D scene authoring viewable in view3dscene." -> this
may be confusing. Castle Game Engine editor actually creates designs
that are more than X3D. So they are not viewable in view3dscene. It's
the other way around -- "view3dscene allows to view various model
formats, including X3D and glTF. Castle Game Engine editor allows to
compose these models into larger designs, in JSON format specific to
CGE."

Regards,
Michalis

pt., 18 lut 2022 o 16:09 vmarchetti at kshell.com <vmarchetti at kshell.com>
napisał(a):
>
> If there is time after Mantis discussion, a possible topic is review the node inventory and browser review information for view3dscene:
>
> view3dcene information review :
> https://drive.google.com/file/d/1Ka1lR9laQiMPitRQWj3HULU2CKHqPFKF/view?usp=sharing
>
> Node inventory : https://docs.google.com/spreadsheets/d/1jXu52t7_5kdQY8CtEJBM8oU6PxzwQz93/edit?usp=sharing&ouid=113910437446121064118&rtpof=true&sd=true
>
> (inventory based on the existing inventory: https://www.web3d.org/specifications/X3dNodeInventoryComparison.xlsx
>
>
> Vince Marchetti
>
>
> On Feb 15, 2022, at 11:53 PM, Brutzman, Donald (Don) (CIV) <brutzman at nps.edu> wrote:
>
> Regular Friday meeting 08-0900 Friday, call information below.
>
>
> Videoconference Connectivity:
>
> https://us02web.zoom.us/j/81634670698?pwd=a1VPeU5tN01rc21Oa3hScUlHK0Rxdz09
> https://zoom.us/j/148206572  Password 483805
> https://www.web3d.org/member/teleconference-information
>
>
>
> Spiraling questions about SpotLight field relationships and default values, beamwidth and cutoffAngle
>
>
>
> X3D4 Architecture, Lighting component, clause 17.4.4 SpotLight
> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/lighting.html#SpotLight
>
>
> excerpted
>
> SpotLight : X3DLightNode {
>
>   SFFloat [in,out] beamWidth        π/4      (0,π/2]
>
>   SFFloat [in,out] cutOffAngle      π/2      (0,π/2]
> }
>
>
> X3D4 Architecture, Lighting component, Figure 17.1 — SpotLight node
> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/lighting.html#f-SpotLightnode
>
>
>
> [x3d-public] Defaults of SpotLight.cutOffAngle, beamWidth changed (maybe by mistake) in X3D 3.3
> https://web3d.org/pipermail/x3d-public_web3d.org/2022-February/016744.html
>
>
>
> Mantis 441: 17.4.3 SpotLight -- Default Values (resolved 2009)
> https://www.web3d.org/member-only/mantis/view.php?id=441
>
>
> Michalis has agreed to walk us through this.  Goal outcomes for confirmation:
>
> is figure OK?
> Is relationship correct, typically beamWidth <= cutoffAngle
> Should we modify default values?
> Should we improve prose for clarity?
>
>
> = = =
>
> Working on Mantis issues for Volume Rendering component
>
> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/Architecture.html
>
>
>
> X3D4 Architecture, Volume rendering component
> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/Architecture.html
>
>
> Nicholas and Michalis: please comment on following issues:
>
>
> Mantis 917: Table 41.7 Volume rendering component support levels - ShadedVolumeStyle shadows support unclear
> https://www.web3d.org/member-only/mantis/view.php?id=917
>
>
> and
>
>
> Mantis 709: 41.4.4 ComposedVolumeStyle - Remove reference to ordered field
> https://www.web3d.org/member-only/mantis/view.php?id=709
>
>
> Can we remove ‘ordered’ field from table?
>
> = = =
>
>
> Other topics of group interest… are always welcome.
>
>
> Membership has value! Please consider joining Web3D Consortium.
>
> https://www.web3D.org/join
>
>
> Thanks for all preparations and inputs.  Have fun with X3D!   8)
>
> 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
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
>