NX 5 Move Command
NX 5 Move Command
(OP)
We upgraded from 3 to NX5 and now the "move" command available from the right click menu will take about 10 seconds to display the dynamic positioning tool. Even worse, if the command is canceled it takes even longer.
When it is "thinking" about this operation ugraf.exe is using 99% cpu and the memory usage just barely trickles upward.
We use dual core cpu's, XP64, 3G ram, quadro 1400, NX 5.0.3.2.
Any suggestions?
When it is "thinking" about this operation ugraf.exe is using 99% cpu and the memory usage just barely trickles upward.
We use dual core cpu's, XP64, 3G ram, quadro 1400, NX 5.0.3.2.
Any suggestions?





RE: NX 5 Move Command
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/
RE: NX 5 Move Command
RE: NX 5 Move Command
That said, is your assembly large? Now I just tried this using NX 5.0.4.1 on an assembly with over 11,000 components and while it did take perhaps a second or two longer for the dialog to come up than when I tested this on an assembly with only a dozen of so components, it was still fast enough that I wouldn't have thought twice about it. Now there is one issue, if it is a large assembly with a really deep tree (many sub-assemblies inside sub-assemblies inside sub-assemblies, etc,) when you move a selected component that is part of a sub-assembly, the system has to first set that sub-assembly to be the Work Part, which can take a little extra time, but again, in my 11,000 component assembly, even if I pick as deep as I can (at least 4 levels down), it still only adds a second or two at most to the dialog coming up.
One more thing that it might be. If you have lots of inter-part relationships and you're using Partial Loading and you're NOT loading inter-part date, if you are selecting components several levels deep in the assembly structure, it is possible that when they set the sub-assembly to be the Work Part they extra time will be taken to fully load and perhaps even update inter-part links that will also get loaded at that instant under those conditions.
Anyway, unless it's some sort of inter-part updating thing, I can't think of anything that would case a 'Move Component' command to be anywhere near as slow in coming up as you seem to be telling us that it is.
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/
RE: NX 5 Move Command
When does it hit the streets and what's new?
RE: NX 5 Move Command
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/
RE: NX 5 Move Command
Doc
http://www.goodrich.com
RE: NX 5 Move Command
If you have the links set to update automatically try turning on delayed update and see if that helps. It may not do anything or be only a partial solution, but the thread reads like until 5.0.4 there is every reason to proceed cautiously.
Best Regards
Hudson
P.S. I'm not observing the same thing testing smaller assemblies under 5.0.3.2 on Xp 32Bit.
RE: NX 5 Move Command
You need to realize when using inter-part links you need to make sure it is a solid model and will not move or be deleted, renamed or the like.
Doc
http://www.goodrich.com
RE: NX 5 Move Command
So if there is any way to determine whether a bug does exist that can be addressed I would really encourage PLMS to get on to it. I'm not in a position to test it myself nor do I know whether problems that some posters are reporting can be reproduced. Maybe if those of you who do have the problem can send in your parts to GTAC we're all going to thank you for doing so in the long run. All I know is that problems with Wave Linked geometry are pretty much your worst nightmare in NX.
Best Regards
Hudson
RE: NX 5 Move Command
We are in the process of uploading and turning on Team Center.
Doc
http://www.goodrich.com
RE: NX 5 Move Command
Good Luck
Hudson