Attached is what this looks like with the current new mesher. It seems better to me, what do you think?

There is one major area that is not handled completely - larger areas that have rather subtle shallow curves may not pick up as much detail as you would want. I might try a couple of ideas on fixing this part up too.

- Michael

Thnx Michael,

it looks now far more like what I had in mind :-D

Thor

Hi Michael,

maybe this helps you a bit:
http://graphics.cs.uiuc.edu/~garland/papers/ssq.pdf

Best regards,

Thor

> maybe this helps you a bit:
> http://graphics.cs.uiuc.edu/~garland/papers/ssq.pdf

Hi Thor, it's very interesting, but it is a method that builds a quad mesh from a triangle mesh.

I'd expect this kind of functionality to be added to whatever program you're using that works on meshes. I'm probably not going to add a lot of mesh to mesh processing type functionality into MoI.

- Michael

Did you notice the Moai statue on page 7 of the PDF ? ;-)))

Yes, Moai is everywhere, it's the new wave :D

I'm still in the process of working on the vertex alignment for ngons. It's one of those things where it seems like every step uncovers two more steps of other stuff before it is done. But it is moving along.

- Michael

Actually, it samples surface shape/topology So while the examples that paper is using are triangular meshes being turned into quads, it could be working with nurbs too. There is another paper by the same author on user-directed remeshing that yields models with good edge flows ( Needed for 3D animation ). Basically a automated version of Silo's topo brush.

Both would be killer features. Don't dismiss them because the examples are tri based. :)

> Both would be killer features. Don't dismiss them because the examples are tri based. :)

Don't get me wrong, I don't doubt that they would be useful. But reading a research paper and making a fully functioning production ready implementation are two totally different things...

It's just far beyond the scope of what I will be able to accomplish anytime soon.

Since the technology is not specific to NURBS and works on triangle meshes, why wouldn't you want to have this functionality available inside a polygon modeler where you might be importing a bunch of other triangle-based models already? It seems like it would be a lot more useful and more general purpose if it was implemented over there rather than only as a specialized NURBS export option.

- Michael

I`ll check that with the silo guys :-D

Thnx for the tip Michael,

Thorsten

I still have a bunch of things to fix, but ngons with aligned vertices are starting to work, here are a couple of tests (Steph's cannon and church). There is still some work to do, for instance there are some messed up parts on the interior walls of the church, but this should give a good idea of how it's going to work.

Now ngons that are adjacent to one another will share the same points along trim curve boundaries.

So it would be good to know if this is better than the previous versions.


These have no texture coordinates, I temporarily removed those to reduce file size.

I also removed the text on the floor of the church - several of the letters had some small extra loops in them which interferes with the meshing. If Steph has the original curves for these it would be good to know if the loops were in the original curves, or if they were created due to some bug in a trim or boolean operation.







Edit: removed church one, there seems to be some problems in the original model.

- Michael

Transmited to Steph :)

From Steph
The letters of the floor Church were simple Text curves (format 3dm) from Rhino 3D imported in Moi
Extrude + Chamfer ---> seems that gives problem :)

For the Gun : points are not yet "auto welded", good matching surfaces, all normals are in the same way :)

For the church : here an Avi video with some bugs:) http://stephlx.free.fr/MoI/bugObj.avi 13 meg :)

For the Old Door : after export Obj in C4D no possibility to "auto weld" points of the fence, too numerous points, no enough Ram !!! (2 Gigas:)

Various complaints :)
Infinite grid on the "2D views"
Scale Tool ( I suppose 1/100, 1/1000...or unity cm, m, inch ...) ?
Text cotation (?)

>> So it would be good to know if this is better than the previous versions.

Some good news and some less good ones... ;-)

The cannon :
- No more missing geometry in Modo ! Cool
- Normals of some faces still pointing in the wrong direction (Modo) I had to flip them manually (or use a double sided material).
- Not new, but once the vertices are merged some visual artefacts appear (due to smoothing). Most of them disappear when I change the smoothing angle of the mesh but I can't get rid of some of them (Modo, Hexagon, Vue)

The church :
- Some missing geometry in Modo (mostly pieces of the ground)
- For some parts, it seems that two polygons (or two objects) are created for the same faces, pointing in opposite direction. It's also the case in the Demo version of Cinema4D 9 but it's less noticeable there as it doesn't generate visual "problems" on screen.
- Face with inverted normals as for the cannon
- I could not merge the vertices of the model in Modo and Hexagon. Both programs have frozen and I had to kill them.
- Same smoothing artefacts than for the cannon

Just let me know if this is clear enough. If needed I can send some screenshots tomorrow (or maybe record some Wink presentations to explain the problems I encounter)

Cya

Thanks Schbeurd for testing in Modo.

The church is fairly messed up from my own bugs right now so I want to focus more on the cannon at the moment.

Tomorrow can you please post a screenshot showing some of the faces that are in the wrong direction? I'd like to closely inspect those areas to see if I can figure out what might be happening there.

- Michael

> For the church : here an Avi video with some bugs:) http://stephlx.free.fr/MoI/bugObj.avi 13 meg :)

It seems that the duplicate surfaces are in the original file.

There are also some other loops in trim curves that are causing the meshing problems. These don't seem to be the result of a chamfer, it looks like a trim or boolean between an extrusion and the arch. If Steph has any of these original curves or objects from before the trim or boolean, those could help to track down what is causing those loops. It is hard to figure out what is causing them just by looking at the loop afterwards. If I can get the objects involved _before_ the operation that causes it, it is better.





- Michael

From Steph
Arch are just curves extrude + sculpt with bolleans function
Only "text" were import from rhino 3D
All the rest is 100% Moi

> Arch are just curves extrude + sculpt with bolleans function
> Only "text" were import from rhino 3D

Does he have the original curves before they were extruded?

If I can get the original curves that were used to create the extrusions, then I might be able to repeat the boolean and see what is happening that causes the loops. It is hard to try and figure out what caused the loops by just looking at the final result.

- Michael