[x3d-public] Fluid example from the web:

[Joseph D Williams]

➢ Here’s an interactive fluid example

Somebody wanted to make some waves! Surfing Duckies …
Doesn’t even register for cpu or gpu in any browser here. Amazing, truly, but that scene is only a bitty patch of water and a picker and propagation model and four duckies and the walls. Fine, well I want the duckies to make waves as they follow the picker over to the froggy, who has a message for them. 


➢ three.js examples (threejs.org)

Any of those could have an x3d implementation using canonical encodings. Sure, it is appropriate for hosts to expose current and legacy web of the gl, and maybe more, to a script running in the browser but still, we are looking for best practices of organizing data for authoring and vizualization, not just for transport, but for live realtime connected scenegraph authoring (typing numbers, operating controls, even) and realtime-anytime interactions with other authors and simulations. This means more than just spraying binary data and meta for viz, composing, and animation frames from workstation to workstation finally to make a video. Mainly, we want to be able to jam with the numbers some machine or human may give us. 

x3d can do any of that? If not, then what is missing for nodes and fields, or scripting? 
So, to me, even if the stage, the water, the water waves, pick interactions, and the duckies were produced in a set of scripts all assembled from an assortment of data packages to keep it responsive, then we need a node or set of related nodes that provide necessary inOut for those scripts. The script then becomes part of the prototype node(s) which produce the interactions.  

Thanks,
Joe



From: John Carlson
Sent: Monday, March 14, 2022 2:47 PM
To: X3D Graphics public mailing list
Subject: [x3d-public] Fluid example from the web:

Here’s an interactive fluid example using three.js:  https://threejs.org/examples/?q=water#webgl_gpgpu_water

On phone, drag your finger along the top of the water.

Enjoy!


On Mon, Mar 14, 2022 at 4:36 PM John Carlson <yottzumm at gmail.com> wrote:
I’ve renewed my membership.  I think I will restrict my activities to JSON, which is very extensive.  I will also work on fluid visualization, with JSON using particles (which may include complex geometry, I understand).

I can really only work 2-3 days a month.   Thanks for understanding.

I will look a bit into how glTF and fluids work together now.

John

On Fri, Feb 25, 2022 at 3:36 PM John Carlson <yottzumm at gmail.com> wrote:
I am considering postponing renewing my membership until I can see if I can get anything done after my surgery.   They say recovery takes six weeks.  I’m guessing my renewal may coincide with my surgery date, but that’s not firm yet. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20220318/b9d6b320/attachment.html>