Please find attached, the NXcustom for NX11.0 Revision D.
There have been some changes in the architecture of NX11.0 that required specific changes in how NX is started.
The UGII_ROOT_DIR is depricated and all path's pointing to that folder from your side will need some adjustments.
Additionally it is now possible to deploy a predifined column configuration of the Assembly, Part and Operation Navigator.
More details of the changes can be found in the about.txt
If there are any ideas for improvements, please feel free to contact me directly by Email:
Solved! Go to Solution.
Additional i have a question to the community.
Is there anyone who ever has decided to use the CAMauxiliary (MACH\auxiliary) folder in NXcustom?
This folder contains mostly code and has very little that can be configured. I am considering to remove this in an update.
Are there any issues transferring files from nx9 custom to nx11 custom? I would like to move all my existing customizations to the latest environment without having to recreate. Will I lose any functionality by doing so?
It is possible to do so, but you will miss things.
An upgrade to a higher version will always require a comparison.
I usualy do the following:
In general there have been changes to all the scripts that reside in the NX110custom and the NX110library.
The changes are required to support the new location for executables in NX11.
Because of de deprication of UGII_ROOT_DIR there have also been edits to the NX110env.dat file.
In general it is a good idea to compare everything.
So it is possible, but not with just a copy and paste.
Looks like you are mistaken MACH\custom with MACH\auxiliary
Yes - I responded too quickly. I have removed the post.
I am encountering inconsistent behavior between using the NX11 custom environment from a local drive and a mapped network drive. The two things I have noticed so far when the environment is on a mapped drive:
The setup is I have two machines, each with a out-of-the-box installa