-
1
- #1
Martynw
Mechanical
- Feb 20, 2007
- 17
Hi all
I have been using NX for 15 years, and are heavily involved in training new users, and rolling out new versions.
Up to NX7.5 adding dimensions although not perfect, was at least a simple process, with MB3 allowing access to 95% of all the editing that was ever required by us. Indeed my standard line during dimensioning training is "its all on MB3".
we don't generally change arrow sizes, gaps, fonts, etc, as these are all pre set from the Seed part.
I am now testing NX9 and are really struggling to see how this is a better approach; it's certainly not quicker for those 95% of changes we make, either on button clicks or time.
As someone experienced in delivering support in a Design environment I know that I am going to take a great deal of flack over this, so I could do with a comprehensive explanation of how this will benefit us.
I work in a design environment, not software development world; do the two ever talk!
Sorry for the rant, but I have to sell this.
I have been using NX for 15 years, and are heavily involved in training new users, and rolling out new versions.
Up to NX7.5 adding dimensions although not perfect, was at least a simple process, with MB3 allowing access to 95% of all the editing that was ever required by us. Indeed my standard line during dimensioning training is "its all on MB3".
we don't generally change arrow sizes, gaps, fonts, etc, as these are all pre set from the Seed part.
I am now testing NX9 and are really struggling to see how this is a better approach; it's certainly not quicker for those 95% of changes we make, either on button clicks or time.
As someone experienced in delivering support in a Design environment I know that I am going to take a great deal of flack over this, so I could do with a comprehensive explanation of how this will benefit us.
I work in a design environment, not software development world; do the two ever talk!
Sorry for the rant, but I have to sell this.