Full Version: Polygonal Converter.

Show messages:  1-20  …  41-60  61-80  81-100  101-120  121-140  141-160  161-180  …  481-483

Wow!
Thank You very much!!!

---

Finally found the time to try this cool script.

It looks great. Thanks a lot, Max! I especially love the minimal number of control points.

A question:

When using the max number of subdivs, you still see seams along the surface edges. Will those be gone in the Quality mode? Would be great if the surfaces would have seamless continuity.

All the best,

Metin

---

Hi Metin,

>>I especially love the minimal number of control points.
Thank you. This was one of the main tasks.

>>When using the max number of subdivs, you still see seams along the surface edges.
I'm working on it. Fast mode will be used for interactive tuning only.

>>Will those be gone in the Quality mode?
Yes. At least I hope so :)

---

Here is the Tetrus stp, from an old topic, for testing purposes, if useful.
Not quite as pretty as the old "t-splines" version.

- Brian

(I bought ViaCad, at the half price special, and used it to convert the stl to stp.
Thanks to those responsible for the tips.)

---

Made a small pdf for the customUI Objects, to be placed along with the tetrus .3dm in the Objects folder, if so desired.
I had to manually set the background color in Moi to white, then reset it to the saved "grey" color rgb.
Is there a script way to temporarily set the background color white, and restore the "grey"?
The porcelain lighting seemed to match the 3 default objects.

http://moi3d.com/forum/index.php?webtag=MOI&msg=5410.6

- Brian

Image Attachments:
Tetrus.png 

---

Hi Brian, check out here for a script that saves the current viewport background color, then sets it to white, then takes a screenshot, then restores the starting color back:
http://moi3d.com/forum/index.php?webtag=MOI&msg=4559.2

- Michael

---

That'd be fantastic, Max, keep up the great work!

---

Thank you Michael.
The script works very well.

- Brian

---

Max,

When I import my OBJ I get a strange error. The mesh is 816 polygons and when I run the Subd converter the mesh just disappear.

Attachments:
Grip.obj

Image Attachments:
GripErrorImport.jpg 

---

I did not think that Moi would import .obj format.

- Brian

---

@ Brian
re:
> I did not think that Moi would import .obj format.

It will if you use Max's importObj script from here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=6674.68

That will import quads or triangles (not n-gons) from an .obj file.

- Michael

---

Thank you Michael.
I did download that last week.
It is hard to keep track... :-)

- Brian

---

Michael
>> That will import quads or triangles (not n-gons) from an .obj file.
importObj supports n-gons :)

Sonk
>> When I import my OBJ I get a strange error.
All polygon points must lay in the same plane, or you will get Geometry error.
In this case script tries to create a curved surface through those points.

>> The mesh is 816 polygons and when I run the Subd converter the mesh just disappear.
I'll check it.

---

Hi Max,

> importObj supports n-gons :)

Oops, I see now I didn't read it close enough - I saw the if (edges.length<5) part and I thought that was the main thing, but now I see that's only a backup path for if the polygon was not planar enough for planarsrf to construct a surface through it. Sorry!

I guess if the n-gon is non-planar then that will be an issue though?

- Michael

---

Hi Michael,
>>I guess if the n-gon is non-planar then that will be an issue though?
Yes, exactly.

Just found a stange obj export bug. When I export "O" letter using n-gon mode, MOI creates four strange polygons instead of normal quads.

f 83/83/83 101/101/101 85/85/85 86/86/86 102/102/102 84/84/84
...
f 97/97/97 103/103/103 98/98/98 99/99/99 104/104/104 100/100/100
...
f 105/105/105 137/137/137 106/106/106 107/107/107 138/138/138 108/108/108
...
f 119/119/119 139/139/139 121/121/121 122/122/122 140/140/140 120/120/120

So importObj can't properly import it.

---

Hi Max - it's not unusual to get n-gons possibly with some of their points nearby each other in various juncture areas. There it looks like it's the cut through the middle to deal with the interior hole in the top surface that is probably introducing the points you don't want. That's just part of how the mesher works... OBJ format does not have the concept of a polygon with a hole in it, so any n-gons that would have internal holes within a single n-gon like the top face there will get divided which can easily introduce additional boundary points.

- Michael

---

Hi!
I'm back (for a while ;)

This weekend I wrote a new beta of subdiv script. Yes :) I finally did it! :)
This version is very unstable, but it works much better with extraordinary vertices. C1 continuous on extraordinary vertices, and C2 on ordinary vertices.
It doesn't support triangles in hq mode yet, so you need to use quads only.
Of course some surface issues may occurs. I think there may be some bugs.
Also I plan to write an optimization block, which can stitch separated ordinary quads to one surface.

---

Extraordinary script! ;)

---

Hi Max,

Sounds incredible!

Just so I understand how this works...

Can I import an OBJ non sub-divided created in a program light Lightwave, and this script will convert it to NURBS? If so-- WOW!

---

Hi Max,

It's late here, so I'll torture your script tomorrow.
I have to say that the results on the provided examples are really amazing.
It's way beyond my expectation, it looks much better on hi-valence point than some commercial plugins Oo

---

Show messages:  1-20  …  41-60  61-80  81-100  101-120  121-140  141-160  161-180  …  481-483