Hi Michael,

Something strange with the extrude here,



I can't have the cap option working with the extrude command, the curve is planar (confirmed by the scaling frame visible in the 3d view).
I can create a surface with the planar command either.

hi paq..

there seems to be something wrong with the curves/profile..






after trimming => extrudes fine

~,
marco

Hi PaQ,

It appears that your curve is not a closed one.
There are two points very close to each other on the top right corner of the curve.

I could create a planar surface after separating the curve and moving the points then joining again...

EDIT : Beaten by Marco ! ;-)

hooray :]]

Ralala, what a stupid mistake, thanks a lot guys !

Yeah, typically when planar doesn't work - somethings not planar :-P

Maybe someday in the near future Michael will put in some diagnostic msgs explaining why a function failed...

-Will

One thing that can help with this is the new object type readout in the last beta.

If you've got a fully closed curve, it will say "Closed Crv" there - this one just says "Curve", which means open curve.

In the future I would like to have an area to put out various warning or error messages so that commands could give more feedback about what has happened. I haven't quite figured out where to put something like that in the UI yet though.

- Michael

Hi Michael,

>> If you've got a fully closed curve, it will say "Closed Crv" there - this one just says "Curve", which means open curve.

Cool tip !!!

Btw can I really trust the object type panel about solids ? I remember having 'visualy' broken solids few days ago that was still listed as solid.

Hi PaQ,

> Btw can I really trust the object type panel about solids ?
> I remember having 'visualy' broken solids few days ago
> that was still listed as solid.

If it says "Solid", then you can be sure that there there are no open edges - that is that every edge in the model is joined to another edge.

But there are potentially other things that can be messed up in a model aside from unjoined edges, like if you have trim curves that have a self-intersection in them, like a small curly-cue loop like this:



Something like that is probably what is wrong when you see a weird visual display, the mesher isn't able to determine the inner/outer regions of that face properly when there is a loop like that.

Unfortunately doing a comprehensive test for things like loops and self-intersections (a surface can have a self-intersection fold in it in a similar way) is a rather time consuming operation so it isn't really feasible for me to attempt to do that level of analysis just on every click of the mouse.


Anyway, when it says "Solid" you can be sure that the topology is set up as a solid with all edges joined into a closed skin.

- Michael

Ok, I understand the self intesection problem and the meshing trouble.
But here's an other example :



For an unknow reason, filleting the last bottom edge of this model make some surface dissapear ... however, the object type panel is still showing this as a solid :S

Of course here I have a good visual feedback and I can fix it, but sometimes this kind of missing surfaces appends in some tiny fillet area, and I only see it after the mesh export (flipped normals) ...

Boy, PAQ, you certainly get the maximum value out of MOI - all of your models are HOTT! ;-)

I was getting this previously but had pegged it down to geometry that I had >mirrored< that would cause things to disappear.

Michael, (hopefully) fixed that for us with that quick patch he put out.

If you didn't mirror the piece that's causing the disapperance, then it must be something else that causes a similar kind of error within the model?

-Will

Hi PaQ, can you possibly send me that model so I can repeat the problem over here?

It looks like you probably got a "disjoint brep" in that situation there, which is a brep made up of more than one boundary skin but still defines a solid volume in separate pockets.

I would guess that if you save that to a file and re-open it that it will end up broken up into different pieces like you would more expect.

Normally there are some volume separation type steps for commands that could otherwise easily create this kind of a thing such as Join or booleans, it looks like I need to add that processing to filleting as well.

So really that looks like a tuneup needed for Fillet actually. If you can possibly send me the pre-filleted shape over here so I can repeat the Fillet and see the problem happen that would make it easier for me to fix it up.

- Michael

Hi WillBellJr, thanks for your comments :o) (my MoI was allready patched for the mirror bug)

Looks like it's a fillet bug finally ;) (confirmed by Michael)

Here's an update of the robot, looks like I don't match the 50's spirit very well :S (that's why I probably like it hehe)

Cool robot! Assimov can sleep in peace ;)