Unigraphics NX3 CRASHING!!!!

[krickard]

I am having a mjor problem with nx3 constantly crashing. And when I say crashing, I mean being completely blown out of the program. With a little research, I know its not specific parts, specific functions, specific hardware (we have plenty of space and speed), and even specific users. We are running on UNIX systems. Is anyone else having this same problem and/or know any solutions?

Any help would be greatly appreciated.

 

[looslib]

Are you running the latest version of NX3?

Is this a new, sudden problem or has it been there for a while?


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

Ben Loosli
Sr IS Technologist
L-3 Communications

 

[krickard]

This is the version: 3.0.2.3

This has been a problem ever since we got it which was around 2 months ago. I don't think it happened the first week, but since that, it tends to go in spikes.

 

[looslib]

What Unix boxes and have you checked the graphics cards to be sure that they are still supported and have the latest drivers?


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

Ben Loosli
Sr IS Technologist
L-3 Communications

 

[krickard]

We are using hp workstation c8000's.

We had our support company install the latest of everthing. I'm not sure how to check the graphics card. I didn't think that a graphics card could crash the software, then again I'm learning a lot of this stuff as I go.

 

[jec3300]

I had the same problem on an XP box and found that the graphics card was not set right. The system would hang or would just crash for no reason. After fixing the grapics card issue the machine is working better.

 

[krickard]

I just talked to our main support person and he said that with UNIX systems, there are no settings for the graphics card, it just is what it is. If anyone knows any different or again experiencing the same problems, let me know. I am trying very hard to get to the root cause of this.

 

[jackley]

We have 2 Sun Blades (1500 and 2000) and a Ultra 60 that we run NX 3.0 (3.0.2.3) and have non stop problems.

From just updating an wireframe extrusion to switching between modes (modeling to drafting and vice versa).

It is very frustrating to say the least.

 

[seb291]

Not to completely change the subject, but ever since we went to NX3 on HPs with UX11. I am having huge processing times and lockups as well. I have two tickets opened one with the GM helpdesk and one with GTAC for two separate issues. We are trying different boxes and different logins to try and find a solution. No matter what improvements we get, they don't compare to the process times of NX2.

 

[wmalan]

And not to change the subject... again, I've been using NX4 since it's release last month every day 10hrs+. Mainly NC programming with some assembly modeling of fixtures thrown in as well. I've not had a lick of problems except for the occasional "internal error" This might happen perhaps once a week. I'm clearly impressed given it's such a fresh release. And the topper is I'm running it on a PC. Pretty impressive.

--
Bill

 

[krickard]

Yeah, I hear that NX4 is supposed to correct a lot of problems that NX3 is having. We recieved our copy about a month and a half ago or so. Unfortunately, we can't move onto it until GM does which will probably be at least another year if not more.

 

[Xwheelguy]

krickard,

Have you checked with your I/T people to make sure they've installed the latest UGS-recommended O/S patches as well? There were at least 3 HP-UX 11 patches that were listed when NX3 first came out in 2004.

Also, have you contacted GTAC about this yet? There are a couple of regular posters from bbsnotes that run UNIX versions and I've yet to read of this recurring amongst the UNIX users, so I'm thinking this may be an isolated occurence.

Tim Flater
Senior Designer
Enkei America, Inc.

http://www.enkei.com

 

[krickard]

This is what I am running.

UG Info:
Version NX 3.0.2.3
Patch MP5, Rev A

System Info:
OS: HP-UX B.11.11 U

 

[blancj8]

I have found that a system reboot is required about every 20 working days. SUN Blade (something) SUNOS 5.8

I came to this conclusion after about three sets of repeated Memroy Access Violation errors that where happening about once a month.
As a matter of fact just yesterday it got so bad I couldnt move a object to a different layer or change its color. Got a system reboot, it pays to be nice to IT, and everything is just fine this morning.

Ya I know its not a fix, but a once a month work around is better than nothing.

Dont let your IT department tell you UNIX doenst need to be rebooted, look at the way CAD users grind on the memory systems compared to say a database host.....

 

[Xwheelguy]

I'm not sure about UNIX but Windows versions create or can create tons of temporary files that might be filling up your hard drive.

I still think the way to go is by calling GTAC if you haven't already.

Tim Flater
Senior Designer
Enkei America, Inc.

http://www.enkei.com