Join our MCAD Central community forums, the largest resource for MCAD (Mechanical Computer-Aided Design) professionals, including files, forums, jobs, articles, calendar, and more.
I worked for a company several years ago and I painfully wrote a mapkey
to replace and old start part with a new custom start part. Unfortunatly
I did not keep a copy,
Has anyone found a simple way to do this in Pro-E WF4?
Just replace the file in \PTC\proeWildfire4.0\templates\inlbs_part_solid.prt and inlbs_asm_design.asm and sheetmetal if you use it inlbs_part_sheetmetal.prt.
Are you talking about implementing a new start part for new parts or updating an old part to be built an a new start part? The former is easy (see above) the latter is less so.
To update an existing part to a new start part, the easiest way is to create a new part based on the new start part and copy the features from the old to the new. This can be done via a UDF or a simple copy -> paste special operation.
I have some parts which must be 'converted' to a new start part. Changes have been made to parameters, model accuracy, layer names and possibly other things as well.
I don't think copy/paste or UDFs will work, because the parts contain external copygeometry features. These can't be included into copy/paste operations or UDFs (as far as I know).
What would be a good practice to reduce the amount of recreating and/or repairing features to a minimum?
<div id="swiffout"></div>I have tried using an external inheritance feature. So far that is the only way to get all features into the new part without errors and endless repairs.
But external dependencies to the original part are not allowed and -must- be removed. So basically I want to 'dissolve' the external inheritance feature into normal features to get rid of the dependency to the original part. Is this somehow possible?
- normal copy and paste does not work (fails due to external copygeometry features in the part)
- external copygeometry for the entire part is not allowed (entire part history (feature tree) must be kept and no references to the original part are allowed)
- UDFs don't work (fails due to external copygeometry features in the part and user defined transitions in rounds)
- External inheritance feature doesn't work(no references to the original part are allowed)
Why is it so hard for PTC to make commands that actually provides the functionality they should instead of almost the way they should....
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
