[x3d-public] X3D minutes 5 June 2020: Web3D 2020 papersdeadline, mantis issues, refining some field names

[Joseph D Williams]

➢ It seems like I should be using blender to create X3D.

Get the blender x3d export working, then you will have it, except for the stuff that x3d does and blender doesn’t, or vice-versa. The way it makes stuff, is same data, different names and data structures, and event systems. Well, you could use x3d to create a blender. Lots of work above and under the covers. 
Like the goal vrml and later html adopted, there is enough in x3d for you to build any sort of frontend authoring system you wish for. Look and see that all you need to build you own user interface is in there and please tell if something is missing.
The info you want, maybe, is what is in blender or any other tool that is not in x3d? Or, as we progress, what is not in x3d that you need? Then, maybe that can be worked on.
Thanks, 
Joe

From: John Carlson
Sent: Saturday, June 6, 2020 11:38 PM
To: J. Scheurich
Cc: x3d-public at web3d.org
Subject: Re: [x3d-public] X3D minutes 5 June 2020: Web3D 2020 papersdeadline, mantis issues, refining some field names

Here’s the best looking version of what I like to do:

https://playcanv.as/p/wQgQBgkE/

Ideally, I could send a math equation in MathML by putting MathML into the geometry node, and PBR or material like glass or diamond


On Sun, Jun 7, 2020 at 1:22 AM John Carlson <yottzumm at gmail.com> wrote:
Previous subject:  morphing comparison in X3D and glTF:


http://web3d.org/pipermail/x3d-public_web3d.org/2017-December/008037.html

I would say morphing is doable in X3DOM, but perhaps not other browsers.   The most conformant approach would probably be an IFS where the position and normal are computed in a shader and the mesh is computed in user code, or provided statically.

My question becomes,  Why can’t we provide at least provide for common topologies?  1 surface and 0 edges (sphere), 2 surface (cone), 3 surface (cylinder), 1 surface and one hole(torus), and consider a higher number of holes and surfaces.   I think we have a isocahedron at least...but very slow to open.

It seems like I should be using blender to create X3D.

John

On Sun, Jun 7, 2020 at 12:33 AM John Carlson <yottzumm at gmail.com> wrote:
What people don’t understand is I’m moving every vertex in the mesh with respect to the mesh.   Kind of like particle physics or morphing would be a better description.   I have example videos.

John

On Sat, Jun 6, 2020 at 11:01 PM J. Scheurich <mufti11 at web.de> wrote:

> 1.  User provides a mesh. I have done this before.  It is too slow for
> a 100x100 IFS (20000 polygons I think).
It depend on your graphics card and driver.
For the rasberry PI and some other systems i meshured the performace in
3000 Polygon-Steps
(1 NURBS-Object with uv/Tessellation 0)

https://wdune.ourproject.org/docs/usage_docs/white_dune_rasberry_pi.odp

(in german but page 5 is a readable table).
A raspberry PI (shared Memory graphics card) can do 30000 polygons, a
Intel HD 3000 shared
memory graphics card (this is a common card on older "office"-laptops)
can do 33000 polygons.
There are very much faster graphic cards on "game laptops"....
The fastest graphics card on this list is a very slow (processor)
Mac-book....

The only systems that are not able to do 20000 polygons are a 8 year old
netbook and a
ARM chromebook without a 3D driver.

so long
MUFTI

_______________________________________________
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/20200607/61455749/attachment.html>