// used by...

[uwam2ie]

Is there a trick or a workaround to get rid of features parameters from features copied with the option "instance of the orginal" especially the used by parameters in the parameter dialog.
thx in ad

 

[JohnRBaker]

Sorry, but that's what the Expression Transfer Mode 'Instance of Original' results in. If you had not wanted that level of integration, try using the 'Link to Original' option instead.

John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

 

[hudson888]

Remove parameters after you create the instance geometry will do it.

Otherwise I could but presume that you want the ability to copy with some sort of timestamp order. In that case your could experiment using instance feature instead under NX-5.

Best Regards

Hudson

 

[MSPBenson]

This has caught me out using offset surface as well.
If you pick more than one surface using the one feature for connected surfaces option ug will create some offset surfaces. It will even create more than one feature in the tree with this option selected.
There is then no way of breaking the linked expressions between the offset surfaces even though they have seperate expressions.
This is in NX4.
You really should be able to remove the link.
If your offset is early on in your tree you then can't remove parameters of just that feature. A real nightmare.


Mark Benson
Aerodynamic Model Designer

 

[hudson888]

Mark,

Yes I know what you mean and have some similar experiences, you can often copy a dumb (unparameterized) version of the faces and try using replace feature to defeat the tyranny of unwanted associativity.

My main problem with offset surfaces is that even after you remove the parameters they won't co-operate with being edited. You can extract another as a either surface type, but not the same as the original and that will work but never the original entity. I can see that they're different, more accurate than the extracted and more complex than the original, but there is nothing else that I'm able to get a handle on as to why this behavior occurs.

Best regards

Hudson