Hi Jacobo,

> They started implementing one of the different approaches
> they were researching (some of them suggested in the
> forum). That was I think like almost two years ago, and it
> hasn't been implemented yet.

I would not be surprised if it turned out to be much more difficult than they initially expected.

Right now the primary way that "all quad" meshes are created by people is by arranging edge flows by hand in a sub-d modeling program, using the modeler's judgment and experience in how to best arrange the topology.

It's very difficult to replicate things that are based on that kind of intelligent judgment just with a list of exact instructions like a computer program is made up of.

The process for doing sub-division smoothing is fairly finicky too, it's quite easy to get a lot of messy results (with stuff like lumpy areas) in the subdivided results if the topology is not really well spaced and well formed. So I mean it's not even just having something technically "all quads" that's the problem - the thing you're looking for is more like "all quads with optimal edge flow topology same as hand drawn"...

- Michael

What? Aren't we in 2012 yet? I've grown up with the idea that by now machines would be smarter than humans. Damn TV. I'm disappointed... :)

Seriously now. At this point I'm not looking for an "all quads with optimal edge flow topology same as hand drawn"... button (well, yes, I'm looking for that, but only if I was the only one who knew about it :). In this particular case I'm looking for things that pretty much exist, because I've seen them somewhere else, but what would make the difference for me is to have some of those things combined together in certain way.

Groboto for example generates a mesh far from ideal, or not even valid depending on what you want to do with it later on, but good enough for certain things that I would be doing with it in some cases. If the time saving to model with Groboto instead of in a poly modeling package is worth it, I can deal with that resulting mesh. Best case scenario (on paper), a huge time saver. Again, just in certain situations when that's what I need. It's all very case specific, and there's not one solution for every situation, but that's what I'm trying to evaluate. The same thing applies to Moi...

Thanks again for your support. Very appreciated!

Hi Jacobo, yeah I understand what you're saying but it's not that great of a situation for me to put out something that is too half baked and would generate bad results in a lot (or maybe even the majority?) of cases even if it would be useful in some other kinds of specific special cases as well...

Right now I'm just not confident that I could make an all-quad mechanism that would not generate nasty results really frequently. I think that there would be a huge amount of time involved in making one that is very robust.

It requires such a different approach to forming the mesh that it is not really all that related to the current tessellator.

- Michael

Also meanwhile there are retopology tools out there that are targeted at reworking a mesh to solve this specific problem...

Have you looked at 3D-Coat's auto retopo function?

Maybe taking triangulated output from MoI and taking it through 3D-Coat's auto retopo mechanism would produce some of the "good enough for a particular use case" type result that you're asking about.

- Michael

Hi Michael,

I've already tried 3D Coat (which is a great piece of software), and somebody is already using it in production, but retopo is actually one of the parts of the process that could be avoided in certain situations (insist, in certain situations). I just was curious about what would involve to implement such thing. As I said, I'm evaluating options, trying not to discard them too soon when they don't seem possible, and see how far things can get in certain aspects. Not that "I need that or I won't be able to continue with my life", just gathering information.

Moi with its current exporting to poly features already helps to speed up a lot certain tasks.

Thanks!

Hi Jacobo,

> but retopo is actually one of the parts of the process
> that could be avoided in certain situations (insist, in
> certain situations).

Why though? If it can pump out an all quad mesh for you how and you were saying that an all quad mesh could help you in certain situations, it is a tool that could help you get the kind of output that you are asking about...

Why rule it out if it can get you the type of output that you are requesting here?

- Michael

No, I'm not ruling out anything. As I said, we're already using it. Just considering different options that can help in certain situations. I don't want to be misunderstood. I would need to explain the whole thing to give you an idea of why this would help in certain cases and how compared to other solutions.

It's not a big deal though, just curious.