Managing big lists of values is slow on grasshopper, doing everything inside a c# script let the simulation works realtime even with big meshes and high droplets count.Īdded comments inside the c# script so anyone could reverse engineer it and maybe learn how to do stuff… Used a c# script for most of the work, used Parallel.For for increased speed using multithreading. Waves keeps a constant volume (conservation of energy… ? maybe not…) Here a small “simulator” using points as droplets.ĭroplet fall speed is equal to wave propagation speed, so when a droplet is below Z=0 it is projected to XY plane and its Z value used as radius of the wave. I’d have to dig in deep to understand it myself at this point. The thread gets into the weeds offering a “Ripple Preview” feature and ripple patterns that span multiple panels, along with other refinements. Some of the later posts in that thread (June 7 and after) mention extremely long elapsed times for high resolution models, which is probably the reason for the Data Dam. Then adapted it to code posted here, with other changes including:īeginning in ripples_2019Jun06a.gh and ripples_2019Jun06b.gh, a switch between “Config” (cyan group) and “Scale” (yellow group) is offered with a ten second (!) Data Dam that delays putting into effect any parameter changes. I modified code from found here:įirst to get this simple demo: damped_sine_crv_2019Jun05a.gh (5.5 KB) I said it couldn’t be done using Graph Mapper. I’ve played with Image Sampler to get a boat wake surface, with good success, though can’t find it on the forum at the moment.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |