Section must be closed for this feature 1

[treddie]

Gawd this is annoying! I never used to have this problem before. I have a lens shape I am revolving about a horizontal revolution axis. So I created half of the lens cross-section above that axis. Problem is, where the horizontal edge of the revolve feature (it lies on the axis of revolution), meets one of the curved lens edges, Creo keeps telling me, "Section must be closed for this feature". So it shows me that the point is bad. So I go and try to use the "Coincident" constraint to make that corner aligned, but Creo keeps telling me, "Constraint already exists". But it DOESN'T exist since Creo does not show any constraint symbol at that corner. So I thought maybe there were stray lines somewhere, or too many constraints, but there are no extra lines and nothing seems to work.

What the Hell is going on?! I've just wasted an hour on this. This seems so stupid.

HELLLLPPPP!

 

[treddie]

I found it! It was a stupid tiny line segment out in the middle of nowhere that was causing it. PTC really needs to get their act together...All they had to do was stop showing the dumb red x at that corner where there was no problem at all and get smart and show a nice big box around the stray line that wasn't anywhere NEAR that corner! WTF?!

Sorry for the rant...I would have been to bed an hour ago if not for this.

 

[mjcole]

Hey man if you don't rant while using Pro/E it's pretty Hard to Stay Sane.

I gotta go prevent my car being towed but look for the 4new icons I believe started in WF4 they are sketch analysis tools One will highlight Closed areas with shaded color. Another Shows Open sections or unattached points, The Next colors overlaping entities either colinear lines or ones that cross each other. Lines curves what have you the fourth and last checks all the requirements for a feature and gives you a report card. Check those UI babies out and save the rants for Microsoft.

Another thing to try is use Trim-Corner and go around your sketch profile/s

Catch you later.

"It's not the size of the Forum that matters, It's the Quality of the Posts"

Michael Cole
Boston, MA
CSWP, CSWI, CSWTS
Follow me on !w¡#$%
@ TrajPar - @ mcSldWrx2008
= ProE = SolidWorks

 

[treddie]

Thank you for the great tip and setting me straight! That will DEFINITELY be in my mental toolkit from now on.

Still, it seems that there is a disconnect in Creo where it recognizes a problem but forces the user to have to manually hunt for the REAL problem when it should really be an automatic thing. AND easy to implement. After all...Creo recognizes the problem...Now all it needs to do is stop being "lazy" and complete the thought. 10 steps to do what could be done in 1. Or as in this case zero!

But...Fingers do need exercise, I guess. The forgotten muscle group.

Thanks again, because I am always frustrated when I think I'm not given the tools necessary to quickly get past a roadblock.