Hi, all
Anyone else noticed how it takes minutes to calculate collisions for some holes, even when the drill diameter is smaller than the designed hole?
Also, anyone else noticed how poor it is at calculating collisions when using a User Representation?
Also, also, Anyone else find it stupid that it doesn't calculate TRACUT affected MO's properly?
Lastly, is there a way I can use a keyboard shortcut to switch this wonderful feature on and off quickly?
David
Dave,
What version of V5 are you using? We had an issue with collision checking using user representations in V5 R30 SP2.
It is suppose to be fixed in V5 R30 SP5, but Northrop requested a Hot Fix. We just got it, Hot Fix 14 and it fixes the issue.
Is your TRACUT problem only in video replay, or in the C/L output file. or both? Is the TRACUT problem a general error, or specific to a certain type of TRACUT?
I've noticed the collision checking error checking performance issue, but only on non native Catia models. I.E. on a model STEP/IGES from NX or some other platform. I think it has something to do with the resultant model being "dumb" without features to recognize as the holes.
Randy Hitzeman
For Hot Key information, I would seek out Bryan Felsher for
advise.
Randy Hitzeman
Randy
Thanks for the input. I design the parts in CATIA then write the toolpaths for those parts.
I'm running V5R31SP3
My TRACUT problem is that it falsely calculates the collision checking upon any MO that has been affected my a TRACUT. I've seen gouges in simulations that do not register as collisions but are clearly visible if you replay the MO and look the old fashioned way
