algorithmic modeling for Rhino
I am intrigued by Pachyderm. Thanks for creating and sharing it.
Oddly, I am experimenting with not a room but a portable semi-transmission-line speaker enclosure. I want to see what's going on in it.
The Pachyderm case is pretty much a boilerplate tutorial thing, largely copied from Gediminas Kirdeikis's excellent videos.
I made truncated copy of the speaker cone, and divided it, evaluating the surface and creating vectors and normals to run the simulation. The surface is offset the speaker cone so that there's nothing co-planar.
It does solve, but it works with only about 100 sound sources. I wish I could see the wavefront a little better. Increasing the bounces makes it go wrong, as well, with the following error.
"1. Solution exception:Index was outside the bounds of the array."
Also, I tried adjusting the voxel grid depth. Set to on zero, it doesn't run. Other values don't seem to help the problem.
Is there is anything I could set to get more rays or bounces without throwing an exception?
I've added blurry Cloud objects, and set the gradient transparency, but what other kind of visualization should I be doing for the most fun--err, um most helpful data assessment for further consideration?
Thank you for the reply, I will experiment with different pachyderm modes.
Though, I apparently also am not allowed very many sound sources. What I hoped to do, was offset the cone from the speaker cone, and use that subdivided reference object for creating equally distributed normals.
Respectfully, I feel that the tutorial's creator was trying to help people.
There shouldn't be a limit on the number of sources, but each source adds another simulation, which can really add up in terms of ram memory. Maybe it has something to do with grasshopper. However, if you use the Pachyderm for Rhino animation tool, you should be able to have as many sources as you like. (How many did you want?)
Respectfully - regarding the tutorial's creator - perhaps he was trying to help. I don't have a problem with that. I do have a problem with having to correct his mistakes - which is the position I'm in in this thread. In the meantime, others have done very good tutorials, and they are good because they worked directly with us. I helped Isak Worre Foged, and I did it without asking for anything in return. Seek out his tutorials for a much better understanding of how these tools should be used. I don't know why GK has never reached out to me. As it is, his tutorial teaches at least one serious untruth about scattering. Now I have to clean that up when I run across it, or people who make mistakes using that information will blame me for that. (This has happened once already.)