Anyone else find NX8 to be quirky?

[JimReed]

Has anyone else noticed that once in a while there expression wont update? I have narrowed it down to features that fail during the update. (due to a multitude of things) Normally a dialog box appears upon failure of a feature in the part navigator. Asking you to accept,accept remaining,undo, etc... This fails to appear. If you restart your session, everything works fine. You can manually work through each feature, but why isn't the software continuing to bring up the dialog box?

 

[uwam2ie]

I would contact GTAC
I'm waiting for an update,too

 

[JohnRBaker]

We made these 'update failure' messages optional some time ago (starting with NX 5.0). If you wish to enable them again, go to...

Preferences -> Modeling -> Update

...where you will find several options which can be toggled ON is desired which will control what type of failures you wish to be notified of.

Also note that these options can be preset at...

Customer Defaults -> Modeling -> General -> Update

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

UG/NX Museum:

http://www.plmworld.org/p/cm/ld/fid=209

To an Engineer, the glass is twice as big as it needs to be.

 

[JimReed]

Thank you John. However..... I am aware of this preference setting.(been on UG since V16) The issue we experience is more intermittent. It is very common for us to have the same session open for days. This anomaly may happen twice a day or twice a week. At some point the dialog box just doesn't come up any more. At that point you might as well start a new session and reload. Any ideas?

 

[JohnRBaker]

You're running an NX session on Windows for days at a time without restrting either the Windows session or NX? You have heard of 'memory leakage', haven't you? If restarting the Windows session and/or NX 'solves' the problem, then it might simply be an issue with your system. In that case, the next time this starts to occur, save a syslog (which unfortunately could be humongous if you've actually been running a single NX session for several days) and contact GTAC and heve them look at it for some telltales.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

UG/NX Museum:

http://www.plmworld.org/p/cm/ld/fid=209

To an Engineer, the glass is twice as big as it needs to be.

 

[Cid1979]

John Baker,

It is not memory leakage, I have been on UG since V18, and so far I have never had this problem until I started running NX8, it is not the systems cause I have had NX7.5 open for days and never had a issue like this Jim Reed is right there is something quirky with NX8.

 

[JohnRBaker]

Then call GTAC and report it.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

UG/NX Museum:

http://www.plmworld.org/p/cm/ld/fid=209

To an Engineer, the glass is twice as big as it needs to be.

 

[looslib]

I always recommend that my CAD users log off every night and preferrable reboot. When I get call about some function being flakey, the first thing I ask is when did you last reboot. Then I tell them to reboot and call me back if the problem is still there. I get very few call backs, like 1 in 100 calls.

If you run on Windows, memory leakage is still an issue, even with Win7-64.

While you may be something 'quirky' in NX8, yet it goes away after a reboot, then report it to GTAC so they can investigate it as it will be the only way it gets fixed in future builds.

When I first started investigating the use of Windows NT for UG V16, I had 3 PCs on loan from vendors for evaluation. All 3 systems showed a similar problem. HP sent a tech from Houston to PA to see for themselves what the problem may be. He was there a full day testing and trying different things. In the end, about 3 weeks later, they asked me to try a new graphics driver, which did cure the issue. At the next User Group meeting, HP acknowledge that they had found a bug with the help of a customer in ALL graphics drivers and had worked with the graphics card vendors to fix the problem.

Bottom line is that reporting problems does help everyone even though it may take some time to work through the issue.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli