<div dir="ltr">X3DOM has primitiveQuality:<div><br></div><div><a href="https://doc.x3dom.org/tutorials/basics/runtimeConfiguration/index.html">https://doc.x3dom.org/tutorials/basics/runtimeConfiguration/index.html</a> </div><div><br></div><div>John <br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, May 31, 2020 at 4:55 PM John Carlson <<a href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I believe there are now "tesselation" or "geometry" shaders now. Do the browsers support them?<div><br></div><div>Thanks,</div><div><br></div><div>John</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, May 31, 2020 at 10:54 AM Don Brutzman <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">1, Well said Joe, also thanks to John and Mufti for sharing.<br>
<br>
Following that sense of things, I refined the warnings/hints for geometry fields in X3D Tooltips. For example:<br>
<br>
==================================<br>
* X3D 4.0 Tooltips, Sphere, radius<br>
<a href="https://www.web3d.org/x3d/content/X3dTooltips.html#Sphere.radius" rel="noreferrer" target="_blank">https://www.web3d.org/x3d/content/X3dTooltips.html#Sphere.radius</a><br>
<br>
[radius accessType initializeOnly, type SFFloat CDATA "1"] (0,+∞)<br>
<br>
Size in meters.<br>
<br>
Warning: simple-geometry dimensions are initializeOnly and cannot be changed after initial creation, avoiding the need for potentially expensive tessellation at run time.<br>
<br>
Hint: for size animation, modify the scale of a parent/ancestor Transform node instead.<br>
==================================<br>
<br>
Questions/improvements/suggestions always welcome. In some sense this file is a kind of context-sensitive FAQ for X3D scene graph.<br>
<br>
----<br>
<br>
2. Meanwhile, there is a relevant Mantis issue pending for X3D 4.0:<br>
<br>
* Mantis 1280: Add quality parameter for Geometry3D primitives<br>
<a href="https://www.web3d.org/member-only/mantis/view.php?id=1280" rel="noreferrer" target="_blank">https://www.web3d.org/member-only/mantis/view.php?id=1280</a><br>
<br>
PDF attached for those without direct access.<br>
<br>
Previous thread:<br>
<br>
* [x3d-public] Add quality parameter to Geometry3D primitives<br>
<a href="https://web3d.org/pipermail/x3d-public_web3d.org/2020-February/011748.html" rel="noreferrer" target="_blank">https://web3d.org/pipermail/x3d-public_web3d.org/2020-February/011748.html</a><br>
<br>
Defining something like "subdivision" field as mentioned there does not pass common-sense test. Any mechanism must be sensible to new authors, since primitive nodes are typically what they learn first.<br>
<br>
Of note is that browsers are welcome to substitute any geometry they wish at run time, including parametric surfaces (as long as geometric results are a Sphere with correct radius, for example).<br>
<br>
Suggested approach, if included:<br>
================================<br>
[initializeOnly] SFString primitiveQuality "MEDIUM" ["LOW", "MEDIUM", "HIGH"]<br>
<br>
The /primitiveQuality/ field is an authoring hint regarding tessellation resolution expected for this geometry. Browser implementations may vary.<br>
================================<br>
<br>
All feedback welcome. Will put this on next Friday's agenda for X3D Working Group resolution, either reject or accept with modifications.<br>
<br>
<br>
On 5/30/2020 7:33 PM, Joseph D Williams wrote:<br>
> * … during models lifetime<br>
> <br>
> So much is true, please notice the access type of the field.<br>
> <br>
> If it is initialize only, then it is set when the node is initialized or replaced.<br>
> <br>
> This has been used as a clue that the browser has to completely redraw the node if the field is changed.<br>
> <br>
> Of course the sphere’s shape can be altered by xyz scaling in the parent transform so you can change the shape to most anything without a hole but not the initialized radius in parent space or the number of points in the shape without redrawing it.<br>
> <br>
> Thanks,<br>
> <br>
> Joe<br>
> <br>
> *From: *John Carlson <mailto:<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>><br>
> *Sent: *Saturday, May 30, 2020 3:47 PM<br>
> *To: *J. Scheurich <mailto:<a href="mailto:mufti11@web.de" target="_blank">mufti11@web.de</a>><br>
> *Cc: *X3D Graphics public mailing list <mailto:<a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a>><br>
> *Subject: *Re: [x3d-public] Sphere subdivision in to X3DV4 standard<br>
> <br>
> Surely you can apply transforms such that the radius changes?<br>
> <br>
>> But according to the X3D standards, a sphere may not change its single<br>
>> parameter (radius)<br>
>> during models lifetime.<br>
<br>
<br>
all the best, Don<br>
-- <br>
Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a><br>
Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<br>
X3D graphics, virtual worlds, navy robotics <a href="http://faculty.nps.edu/brutzman" rel="noreferrer" target="_blank">http://faculty.nps.edu/brutzman</a><br>
</blockquote></div>
</blockquote></div>