[x3d-public] X3D Agenda 19 June 2020: Mantis issues
GPU Group
gpugroup at gmail.com
Fri Jun 19 07:36:28 PDT 2020
Some Mantis issue comments from Doug Sanden, not entered in mantis
-Doug
MANTIS
1303 optional support for WebMercator datasets
- Menlo Park example coordinates are sufficient to elliminate variants
since the ORM is specified already, and Menlo Park is not on the equator or
prime meridian, for WM any variant that has the same Menlo Park coords
would not be a variant. Therefore spec wording in draft is sufficient.
1302 geoSystem is difficult to define and parse, consider
alternative approach
- separating geoSystem from an MFString with embedded meaning tokens itno a
GeoSystem node would reduce scene file clutter - the node could be DEF/USEd
- mapping plane Set member / instance number (an ordinal int) - would be
handy to have that separated from rest of geosystem, since we cannot route
struct tuples (p[3], gyosystem #. maping plane set member #} or other
complex key-value hierarchies in web3d simple field types
So if there's an area of interest with mupltiple mapping plane set members,
it would be nice to define the all of the parameters once, except the
member number which would be different for each
- and that might mean in general separateing mapping plane step from
geodetic ./ geocentric part of geoSystem
Q. what does Walmsley's JSON schema look like for geoSystem
1301 check geospatial navigation to see if NavigationInfo modes
are sufficient
- freewrl > tried adding a few more lines to GeoViewpoint for walk surface
1293 HypersurfaceSensor/MultiTouchSensor for multi-touch
environments
- freewrl implemented (but not yet the AppendixG web3d mouse method which
looks more fun)
- could be called 'MultiDragSensor' in web3d abstract node terms, since
emits tracking points and transform parts?
1281 TwoSidedMaterial deprecation by adding Appearance
backMaterial field
- backMaterial seems comprehensive and allows no front material or
different (unlit, material, physical) front/back
- supporting both in same version could lead to conundrums:
TwoSidedMaterail as shape.material and shape.backMaterial non-sensical
1277 Provide displayBBox field on X3DBoundedObject nodes to
display bounding boxes, rename bboxDisplay for consistency
- freewrl implemented, took 4 days
1269 glTF physically based rendering PBR, advanced material
textures and lighting
- freewrl implemented except EnvironmentLight. and direct gltf loading
- freewrl: no objection to EnvironmentLight - (freewrl needs work)
related: MultiTexture conundrum not solved:
--Lighting model implies texture is an input to lighting so comes first,
-- Multitexture implies Lighting comes first, so REPLACE can replace
pre-PBR technique: put (1,1,1,1) as placeholder for texture, in Lighting,
and modulate output diffuse component with Multitexture
post-PBR method: Physical lighting doesn't have compoentents, so can't
post-modulate to solve conundrum
Options:
1) Multitexture's a priori Lighting would be Gouraud / vertex shader
lighting, multitexture applied before Phong/frag lighting
2) Multitexture not applied to Physical
1264 NavigationInfo type TURNTABLE HELICOPTER GAME FREEFLY
- only x3d-public comments
1) Joe: should specify what motions to restrict / allow when a given type
is the only one in NavigationInfo
2) Doug: avoid mention of specific input devices - as WALK, FLY EXAMINE
avoid,
3) Joe: put any desktop/other recommended input device mapping in AppendixG
HELICOPTER - like WALK with convienient height adjustment
GAME - like WALK with convenient lookaround and strafe (avatar X motion)
FREEFLY vs FLY?
1257 Inline allowed to load additional model types
- x3dom BufferGeometry node tactic for gltf looks promising for freewrl -
avoids reworking spaghetti C code
3 uses cases for .gltf:
1. efficiency of loading binary buffers ready for opengl
2. convenience of loading a gltf directly
3. advanced node types in gltf - PBR, EnvironmentLight, etc
If you don't need #1 or #2, then upstream tools could export enhansed v4
x3d nodes directly, so scene authoring can be done OR a small offline tool
could convert gltf to x3d, so scene authoring can be done on the nodes.
In all use cases, it helps if the advanced node types are supported in x3d
close or 1:1.
1255 Projective Texture Mapping Component (PTM)
- freewrl implemented, X_ITE implmenented
.MANTIS
On Fri, Jun 19, 2020 at 8:10 AM GPU Group <gpugroup at gmail.com> wrote:
> Q. what does Walmsley JSON look like for geoSystem?
> Q. Did he use json in an SFString field for hierarchical key-values?
> Thanks,
> -Doug
>
> On Thu, Jun 18, 2020 at 8:55 PM John Carlson <yottzumm at gmail.com> wrote:
>
>> For 1302 geoSystem, I recommend looking at JSON schema as created by Roy
>> Walmsley and copied into the automatically generated schemas wholesale.
>>
>> If we can convert JSON Schema to XMLSchema, that might be a good solution.
>>
>> Idk. Maybe try it on a small scale first.
>>
>> John
>>
>> On Thu, Jun 18, 2020 at 9:42 PM Don Brutzman <brutzman at nps.edu> wrote:
>>
>>> We meet at our regular time and Zoom coordinates, Friday 08-0930 pacific
>>> (your time zone may vary).
>>>
>>> ---
>>>
>>> 1. *Participation Information*
>>>
>>> [1] Web3D Teleconference Information
>>> https://www.web3d.org/member/teleconference-information
>>>
>>> Please use the following link for all Web3D Consortium Meetings.
>>>
>>> Join URL:
>>> https://us02web.zoom.us/j/81634670698?pwd=a1VPeU5tN01rc21Oa3hScUlHK0Rxdz09
>>>
>>> Meeting ID: 81634670698 Meeting Password: 483805
>>>
>>> One tap mobile
>>> US (New York) +1 929 205 6099,,(nine-digit number from Join URL
>>> above)#
>>> US (San Jose) +1 669 900 6833,,(nine-digit number from Join URL
>>> above)#
>>>
>>> ---
>>>
>>> 2. *Related work*
>>>
>>> We hope to review and accept Pull Request 8 next week to integrate
>>> Physically Based Rendering (PBR) and lighting with glTF support.
>>>
>>> Efi, Thanos, Dick and Don have nearly all node and node type
>>> architectural relationships defined for an upgraded Sound component that
>>> includes spatialized sound capabilities matching W3C Web Audio API.
>>>
>>> We plan to submit a draft specification for review to Web3D Consortium
>>> Board of Directors and membership on 30 June. Following that review the
>>> draft document will be released publicly for comment in time for SIGGRAPH
>>> 2020.
>>>
>>> Implementations to date include X3DOM, X_ITE and Titania, Castle Game
>>> Engine view3dscene and FreeWRL, with possible implementation interest noted
>>> by at other major codebases.
>>>
>>> Ongoing releases include X3D4 XML Schema, X3D Unified Object Model
>>> (X3DUOM), X3D XML Schema and DOCTYPE, X3D Ontology, X3D JSON encoding,
>>> X3DJSAIL (Java), X3DPSAIL (Python x3d.py).
>>>
>>> Summary of current and planned X3D4 nodes and fields is available in
>>>
>>> [1] X3D4 Tooltips
>>> https://www.web3d.org/x3d/content/X3dTooltips.html
>>>
>>> ---
>>>
>>> 3. *Mantis Issues*
>>>
>>> Dick and Don continue making steady progress applying approved changes
>>> to the X3D4 Specifications and related assets.
>>>
>>> [2] Mantis: View All Issues
>>> https://www.web3d.org/member-only/mantis/view_all_bug_page.php
>>> then select "X3D Project" in upper right corner.
>>>
>>> Reportedly each member and invited expert either has full access into
>>> these Mantis issues, or else is being assisted. POC is Executive Director
>>> Anita Havele if difficulties persist.
>>>
>>> Draft specification available to members in Github version control:
>>>
>>> [3] Github Web3D Consortium
>>> https://github.com/Web3dConsortium
>>>
>>> [4] Github Web3D Consortium: ISO-IEC 19775-1 - X3D Architecture and base
>>> components, Part 1
>>>
>>> https://github.com/Web3DConsortium/X3D/tree/master/ISO-IEC19775/ISO-IEC19775-1/ISO-IEC19775-1v4.0/ISO-IEC19775-1v4-WD1/Part01
>>>
>>> This week we are reviewing a large number of issues that are quite close
>>> to resolution. Each issue has enjoyed scrutiny and dialog on the
>>> x3d-public mailing list and X3D Working Group reviews. We seek to
>>> determine consensus on as many as possible in order to allow including the
>>> corresponding changes in the forthcoming X3D4 draftrelease.
>>>
>>> Issue list follows, full issue list attached.
>>>
>>> Id Summary
>>>
>>> 1310 near and far clipping planes currently not directly
>>> specified
>>>
>>> 1309 NavigationInfo avatarSize parameters need to be split
>>> into separate fields
>>>
>>> 1308 creaseAngle support by Triangle nodes
>>>
>>> 1307 X3DParticleEmitterNode mass and surfaceArea accessType
>>> initializeOnly rather than inputOutput?
>>>
>>> 1304 allowing animation of Cone, Cylinder bottom/side/top:
>>> accessType inputOutput
>>>
>>> 1303 optional support for WebMercator datasets
>>>
>>> 1302 geoSystem is difficult to define and parse, consider
>>> alternative approach
>>>
>>> 1301 check geospatial navigation to see if NavigationInfo
>>> modes are sufficient
>>>
>>> 1300 Consistently unify metadata model for GeoMetadata and
>>> HAnimHumanoid info array
>>>
>>> 1299 Annotation Component deferral
>>>
>>> 1293 HypersurfaceSensor/MultiTouchSensor for multi-touch
>>> environments
>>>
>>> 1292 numbering of z order of layers in LayerSet
>>>
>>> 1283 XML encoding: change X3D4 MetadataSet default
>>> containerField='value' ?
>>>
>>> 1281 TwoSidedMaterial deprecation by adding Appearance
>>> backMaterial field
>>>
>>> 1277 Provide displayBBox field on X3DBoundedObject nodes to
>>> display bounding boxes, rename bboxDisplay for consistency
>>>
>>> 1276 name types: whitespace constraints, NMTOKEN and SFString
>>>
>>> 1275 whether CollisionCollection and RigidBody implement
>>> X3DBoundedObject node
>>>
>>> 1273 https level support requirements should match http level
>>> support
>>>
>>> 1272 glTF import needs to include metadata import
>>>
>>> 1271 add visible field to X3DBoundedObject
>>>
>>> 1269 glTF physically based rendering PBR, advanced material
>>> textures and lighting
>>>
>>> 1268 add height and width attributes to root X3D node
>>>
>>> 1267 Strategies to Improve X3Dv4 Audio and Sound Component
>>>
>>> 1266 Make RGB and grayscale textures treatment consistent
>>>
>>> 1265 Text size clarification, relative to baseline
>>>
>>> 1264 NavigationInfo type TURNTABLE HELICOPTER GAME FREEFLY
>>>
>>> 1263 Log capability to record event streams
>>>
>>> 1262 new field /refresh/ for Inline, ImageTexture etc.
>>>
>>> 1261 PointSet field for Normal node
>>>
>>> 1259 Scanning profile needed?
>>>
>>> 1258 Layout component needs to be consistently implemented
>>>
>>> 1257 Inline allowed to load additional model types
>>>
>>> 1255 Projective Texture Mapping Component (PTM)
>>>
>>> 1252 PointProperties node specification;
>>> PointSet/LineSet/IndexedLineSet can contain Normal
>>>
>>> Today Dick and I located a large number of editorial comments from an
>>> in-depth review by Roy Walmsley. We are going through each one-by-one and
>>> will elevate any that are functional, rather than simply editorial.
>>>
>>> Thanks for all scrutiny, feedback and implementation efforts. Have fun
>>> with X3D4! 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
>>> http://faculty.nps.edu/brutzman
>>> _______________________________________________
>>> x3d-public mailing list
>>> x3d-public at web3d.org
>>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>>>
>> _______________________________________________
>> 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/20200619/d69fe916/attachment-0001.html>
More information about the x3d-public
mailing list