[.toe] file 3D Physarum
🕑 Added 2024-04-07 10:19:40 +0000 UTCIn this tutorial I am covering the 3D Physarum simulation and component I have recently developed.
The file attached is the official release 2023.11340.
This file is for Patreons only please do not share.
Hope you like it! if you have any questions feel free to ask
Vincent Houze TD talk: https://youtu.be/EDtf0hN66CY?si=GHH_nO9jRPBQX5pf
Comments
יובל כהן
Hi Ive talked about it in the video tutorial its not only you .I’m still not sure why this is happening. But try the other algorithm with the toggle parameter, tue angles one. In my opinion it works better. Anyway I,m gonna do a revisit on that soon and try to improve it.
Function Store
hey, not sure if it's just me, but it seems to me that the simulation converges to some state where after a while the initial space it fills becomes almost empty. is there a way to solve that? amazing job btw
meta jon
yes. anyway thanks a lot :). learned a few things discovering your .toe files!
Mini UV
Yea its seems these errors are because you have to update td. Unfortunately i cant really do something about it.
meta jon
parent.PointRender.par.Resolutionh/w; docsHelper has a problem; Compute Shader Compile Results: ERROR: /project1/3DPhysarum/compute:77: 'sTD3DInputs' : undeclared identifier ERROR: 1 compilation errors. No code generated. ; parent().par.Rotatematricesanglesdifferentalgorithms; op('Data/out1')['Count']; I really tried to trace back all of these but for me its nearly impossible haha. If you can help I would appreciate it but maybe it's not working with 2022 :/. Thanks for everything
meta jon
all parent.par.Tx/y/z
Mini UV
Can you let me know what errors are you getting with the 2022?
meta jon
because I haven't bought the update yet and my update plan stopped 2022 :D.
יובל כהן
It was built in the latest td release, haven’t tried it on other versions. Why do you need 2022 specifically?
meta jon
Hey any change to get this in 2022 running? awesome work btw!!!
Mini UV
The cause of the error is that the GLSL material does not know about the mTDImageOutputs but the renderTOP does. It should still work with the error. Let me know please if it still working for you although it throws this error. To be more specific do you see the instancing of the particles on the renderTOP? And the conversion to the 3D texture? Or it’s completely gone?
Simon Alexander-Adams
At least in 2023.11600 you still get the error on the GLSL material. Interestingly enough the tool still works as far as I can tell even with the compile errors, but it would be useful to sort out "ERROR: /project1/3DPhysarum/position_to_3d_texture1/write3DPixel:26: 'mTD3DImageOutputs' : undeclared identifier " Edit - actually it isn't working fully, the Position to 3D texture tool seems to be broken. Throws the error for me in 2023.11340 as well.
Atakan Kızıltan
I updated TD and it worked. Thank you.
Atakan Kızıltan
It does not work. I have 2 different errors: - td.CameraCompt has no attribute 'PivotDistance' - All GLSL nodes get error because of "RROR: /project1/3DPhysarum/glsl8_compute:7: 'sTD3DInputs' : undeclared identifier "
Mini UV
I just added to the post at the bottom(:
Dean Cheesman
Can you share a link to the Vincent talk you referenced?
Mini UV
Hi, try to reset the simulation by pressing the reset button in the component parameters. Let me know if it works.
Atakan Kızıltan
Camera and physarumGLSL get error. ============= Compute Shader Compile Results: ERROR: /project1/3DPhysarum/compute:77: 'sTD3DInputs' : undeclared identifier ERROR: 1 compilation errors. No code generated.