Full Version: Elephant Repository

Show messages:  1  …  402-421  422-441  442-461  462-481  482-501  502-503

Hi Drillbit,
yes I had got a result also by tweaking the rectangle sizes.
Cheers
Barry

---

Barry / Psygorn,

I am unable to repeat the pattern on half issue that you have experienced.
Nevertheless I made a small change to NOD file scaling original rectangle
rather than generating a 2nd rectangle, though it is unlikely that this is the problem.

What is more likely is that the issue is copying of point field into 4 quadrants
prior to generating the voronoi pattern. This should be possible to do with a
single "MovePts" node but it fails to work, necessitating the use of 2 such nodes in series.

It would appear that this 2nd move (copying) is not registering for you.
I am not sure if the reason I have not experienced the same problem is due to the fact
that I am using beta version for Mac M1 processor.

There is one more thing I could try: converting points to point object and then copying them
into quadrants before reconverting back to point field. I imagine that this would radically
increase the computation load since new geometry would be generated with each "MovePts"
operation.

But first let me know if problem persists with this new NOD file

Have a great weekend
James
https://www.instagram.com/nodeology/

Attachments:
voronoiTorus.nod

Image Attachments:
voronoiTorus.jpg 

---

Thank you James.

For what it is worth, my computer is still generating half of the torus with unperforated inner and outer skins.

- Brian

---

Thank you James,

However, as bemfarmer mentioned the issue still exists!

---

Hello James,

I tried to recreate one of your works.

you can see it here: https://www.instagram.com/p/CCo6mQUJxkN/

But I ran into that problem.

you can see the Error here: https://moi3d.com/forum/index.php?webtag=MOI&msg=9581.240

Attachments:
Generating Random Irregular Smoothed Solids with qHull3d.nod

---

Psygorn,

Try this version.
I have repeated original point field via math operation to x & y data.

It works for me...but then again so did my last NOD file.
I have been unable to reproduce the error that everyone else seems to have.

James
https://www.instagram.com/nodeology/

Attachments:
voronoiTorusXYobj.nod

---

Hi James,
still the same issue.
I think its the voronoi node I can only generate in a rectangle up to 100 x 100.
If I take your original nod and just adjust the Y constant from 200 down to 100 all works fine.
The photo shows the results when reducing the Y value.
Cheers
Barry

Image Attachments:
Screenshot (669).png 

---

Thanks Barry,



Actually that rings a bell.
Try replacing your voronoi.js file in extensions folder with the one attached.
It is possible that mine is an updated version
See how this works with my first version of NOD file

James
https://www.instagram.com/nodeology/

Attachments:
voronoi.js

---

Hi James,
no go with that voronoi node.
Your original nod file works by reducing the X & Y constants to X 35 Y 50 plus reducing the voronoi space to 0.5.
Cheers
Barry

Attachments:
James Voronoi Torus.nod

---

Barry,

That's odd!
If you look at attached image, you can see that the dimensions of generated voronoi are well over 100 units.
Did you shut down Moi3d.app & restart before reloading NOD file?

James

https://www.instagram.com/nodeology/

Image Attachments:
voronoiDimensions.jpg 

---

Hi Pilou,

And how did you do that?

---

Hi James,
yes my mistake hadn't closed moi your new voronoi node works thank you.
Do you have the same issue with the randompts not updating in the panel ?
Many thanks
Barry

---

Barry,

I'm not sure what you mean.
Hasn't the issue of unpatterned half torus been solved?

James
https://www.instagram.com/nodeology/

---

Hello again James,

I'd be happy if you guide me here as well. :-)

Happy weekend :-)

---

Psygorn,

Replace voronoi.js file in app support/Moi/nodeeditor/nodes/extensions/
with file attached.
James
https://www.instagram.com/nodeology/

Attachments:
voronoi.js

---

Hi James,
yes the torus node works perfectly.
My query is the randompts inputs do not update in the info panel but updates correctly in the model.
See photo.
Also could you upload the extendsrf nod please Wayne as removed it.
Again many thanks.
Cheers
Barry

Image Attachments:
Screenshot (670).png 

---

Hi James .

I also show it that way, but it's easy to fix. The files are different, the difference is only two lines, attached a screenshot. Now everything works well.

Image Attachments:
compare.PNG 

---

Barry,

Ahh yes, I've never notice the the info panel does not update properly.
This must be a glitch in the script.

James
https://www.instagram.com/nodeology/

Attachments:
ExtendSrf.js

---

Hi James,

And thank you. it works fine.

---

Hi Barry-H.

Now the data will be updated, I added the necessary lines in the script.

Attachments:
randompts.js

---

Show messages:  1  …  402-421  422-441  442-461  462-481  482-501  502-503