Showing results for 
Search instead for 
Did you mean: 

Enhancement request for dialog memory of CAM objects

Esteemed Contributor
Esteemed Contributor

In another thread it was determined that the dialog memory is no good for CAM object dialogs, like operations, geometries, methods, etc.


All these dialogs are not updated automatically, so the dialog memory grows significantly, which in turn slows down the user-interface of NX immensely or results in strange problems.


Clearing the dialog memory once a week is not a good solution either, since you may want to keep the settings of the modeling and drafting dialogs.


The solution would be to be able to disable the dialog memory for CAM objects, since these are static and even checking an old part results in the dialog memory file size to increase.


If you find this useful, get yourself added to ER#7301405 by GTAC.


The ER text is below.


o Short Description of desired enhancement:

disable dialog memory for dialogs of CAM objects, like operations, geometry, program groups, tools, methods, etc.

o What activity in your process is NX not able to currently handle?

as above

o What result are you trying to achieve?
to prevent dialog memory build up in manufacturing 

o Do you currently have a workaround?


o Do you have a proposal for the solution you envision Siemens providing for this capability?

o What is the level of productivity gained from such an enhancement?

o Customer Comment

It would be best to disable dialog memory for dialogs of CAM objects, like operations, geometry, program groups, tools, methods, etc.
All these dialogs support customization, so dialog memory explodes and slows down NX immensely.

Since the dialogs are customized by the administrative user, they should always look as he has decided.

the problem is that the dialog memory file explodes in size.
The users using only CAD have a really small dialog memory file of less than 2MB, the CAM users have dialog memory files of 50MB and above.

The huge size of the dialog memory significantly slows down NX performance in respect to switching applications and opening dialogs.

As you say, the CAM object dialogs are configured by the administrative user and also the show and hide state of the blocks.
The dialog memory remembers more than necessary, so disabling it at all for CAM objects would be the best.

I think the problem is that the CAM object dialogs are static and the way they look is not easy to update between NX releases.
Sure there is the option to automatically update dialogs of old parts if opened in a new release, but that is also more time consuming than the benefit you get.

In CAM we also have to work with dialogs created 10 or more releases in the past, so this is increasing the size of the dialog memory file, which in turn slows down NX.

It all boils down to performance issues and even strange behavior of NX, if dialog memory is corrupted.
Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.1, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 ( | TcVis 10.1
Development: VB.NET, Tcl/Tk Testing: NX12.0 Preparing: NX12.0

Employees of the customers, together we are strong Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide

Learn online

Solution Information