erpj
Aerospace
- Jul 15, 2011
- 24
Hi everyone,
I have to manage a very large assembly on which multiple designers are working concurrently (each has its own subassembly). However, I often need to dig in some specific components to modify some features. However when I try to let's say double-click a hole to modify its size, NX hangs for what seems like eternity.
The status bar just shows "updating objects" for ~4 minutes
and then it shows "Done updating features for XXXXXX" (while the progress bar is ~100% full) for an extra 4 minutes.
I don't have this problem if I only open the single component by itself and modify it, but I really need to keep the top assembly opened.
Is there some setting I can use to correct this behavior (delay feature, etc.)? How can I see what NX is doing when it is “loading” something? Some sort of “verbose loading report" would allow me to understand why and where NX gets stuck…
thank you,
Etienne
Etienne
NX8.5.3.3 + TC9.1.2.2
I have to manage a very large assembly on which multiple designers are working concurrently (each has its own subassembly). However, I often need to dig in some specific components to modify some features. However when I try to let's say double-click a hole to modify its size, NX hangs for what seems like eternity.
The status bar just shows "updating objects" for ~4 minutes
and then it shows "Done updating features for XXXXXX" (while the progress bar is ~100% full) for an extra 4 minutes.
I don't have this problem if I only open the single component by itself and modify it, but I really need to keep the top assembly opened.
Is there some setting I can use to correct this behavior (delay feature, etc.)? How can I see what NX is doing when it is “loading” something? Some sort of “verbose loading report" would allow me to understand why and where NX gets stuck…
thank you,
Etienne
Etienne
NX8.5.3.3 + TC9.1.2.2