Boolean not returning valid part; how to intersect?

naregjan

I already posted this here (this is a duplicate) but this seems like the more appropriate forum. 



I have a boat that I'm trying to model based off of four lofted sketches. I've been trying to hollow it out; I tried using both shell and thickness to do so. In either case, whenever I try to take the top of the boat off using any sort of boolean operation, I get an error. In this most recent iteration, I've got a 10mm thick shell, and when I try to get the intersection with a block I've extruded underneath it, I get an error. Here's the link. 

Why? How should I make it differently?

NeilCooke

@naregjan - it doesn't really matter where you post

That doc was shared with a link which makes it read only - please make it public, thanks.

naregjan

Done!
I ended up just extruding downwards into the shell, but I'm still confused as to why the booleans won't work. 

NeilCooke

Hard to tell, but more than likely due to the sharp point at the bow which may be self-intersecting or degenerate.

naregjan

Hmm. But how is it that it's not degenerate as a body but lopping off the top makes it so? I'm afraid I'm not entirely sure how degenerate geometry comes about. 

tim_hess427

I find myself in the same boat often. Some operation fails and the error message essentially says "Well, that didn't work!", which isn't super helpful. It would be good to have more descriptive error messages and separately, some guidance in the documentation with common things that produce errors. I understand the self-intersecting geometry issue and can usually figure out if that's what's causing an error. But there are often times where the error appears to be something different and I have no guidance on what to change or do differently.

Jake_Rosenfeld

@naregjan & @tim_hess427 please don't hesitate to contact support from the "?" menu of your part studio when something like this happens.  Often it is a problem with our modeling kernel, which we can go on to fix, or we may look into whether the error messaging can be better for a specific scenario if it is legitimately faulted geometry.

S_Regula

tim_hess427 said:

I find myself in the same boat often. Some operation fails and the error message essentially says "Well, that didn't work!", which isn't super helpful. It would be good to have more descriptive error messages and separately, some guidance in the documentation with common things that produce errors. I understand the self-intersecting geometry issue and can usually figure out if that's what's causing an error. But there are often times where the error appears to be something different and I have no guidance on what to change or do differently.

Find yourself "in the same boat". I see what you did there