In NX I have added some refsets to my assembly to view the components
differently. When I use File > Export > JT and then create a monolithic jt
file, if I load this JT file into standalone Teamcenter Lifecycle
Visualization and I try to change to different reference sets they are not
Solution This is working by design.
For managed Tc data using NX Manager, when a JT file is generated using File >
Save, the translator processes the objects by reference sets. But anytime you
use File > Export > JT (in native NX or NX Manager) the translation is not
reference set based. In this mode all the entities for a part that are visible
in NX session get translated. Same will happen with run_ugtopv only if you use
'-honour_structure' as an argument. This is by design since the translator has
to handle different customer workflows.
Notes and References
Hardware/Software Configuration Platform: INTL64
OS Version: 1064