Release Notes

NX 1953 Release
Notes
2 NX 1953 Release Notes PDF, NX 1953 Series
© 2020 Siemens
Welcome to NX
December 2020
Dear Customer:
We are excited to introduce the latest release of NX, which builds upon the continuous release process
with significant new and enhanced functionality in all areas of the product, as well as several new
design tools, to help you work more productively and efficiently to build your 3D digital twin.
Design
To optimize product development, we have invested in all aspects of modeling, including core
functionality in Modeling and Drafting. Importantly, with this second release of the new sketch tool,
we continue our drive to make it easier for you to create designs. We've added functionality to
reduce the time and effort needed to define constraints and rules to control your sketch, and to
automatically predict relationships between geometry so you can make changes to your sketches
faster and with more confidence. To help you apply the new approaches to your workflows
seamlessly, we have included a number of video tutorials that you can access directly from NX. We
have put the legacy sketch tool under an early access feature.
In addition, this release includes major Convergent Modeling enhancements that allow you to mix
features and convergent bodies in the same model.
This release also brings some exciting new design tools, including:
• Model Based Definition (MBD), which features unique rules-based MBD and PMI creation and
validation technologies.
• Algorithmic Modeling, which allows you to develop math-based designs quickly.
• Staged Model to streamline the process of building in-process designs.

Manufacturing
New, highly automated operations and powerful enhancements for CAM and CMM inspection
programming, additive manufacturing, and data management help part manufacturers accelerate
the production of higher-quality precision parts:
• CAM
The new Deburring operation automates one of the most-used operations, reducing
programming time by up to 95%. NX automatically identifies parts’ edges (modeled or
unmodeled) and creates optimized multi-pass toolpaths to machine the specified chamfer size.
The Adaptive Milling operation, a high-speed machining cycle expanded to support boundaries
used for programming of prismatic parts, replaces the Trochoidal operation. The new Pinch
Turning operation balances the cutting forces of two opposing cutting tools and minimizes parts
deflection, allowing deeper cuts for higher productivity and accuracy.
• CMM Inspection Programming
NX 1953 Release Notes PDF, NX 1953 Series 3

© 2020 Siemens
New CMM inspection programming functions enable automated creation of tactile scanning
paths on planar part regions. NX generates optimized, high-speed inspection paths using only the
planar face as input, significantly reducing programming time. The enhanced 5-axis inspection
programming functions for Renishaw Revo enable precise control of the tilt and advance angles
of inspection paths, simplifying the programming of complex geometries, such as airfoil sections.
• Manufacturing Data Management

The seamless integration between NX and Teamcenter enables CNC programmers to use
components, such as cutting tools, fixtures, and machine models managed in the Manufacturing
Resources Library (MRL). Using Active Workspace embedded in NX, programmers can now drag
resources from the MRL directly into NX CAM, accelerating programming.
• Additive Manufacturing
Continued investment improves the NX Additive Manufacturing solution for build setup and
printing. With new coating, slicing, and supports enhancements, it is easier than ever to set up
your build tray. Support for varying printer types has also increased. New coating capabilities
support easier programming of parts with multiple plied layers, while CLI slicing gives customers
support for a wider range of print technologies. Furthermore, new support profiles and
traceability save time, ensure compliance with company standards, and allow for better
management of support attributes.
We are confident that the new capabilities in this release will allow you to work more productively than
ever before, and to achieve your product requirements while staying at the forefront of industry trends.
For more information about this release, see the What's New Guide included with the NX help.
–Your NX team

© 2020 Siemens
Contents
Welcome to NX 3
NX System Information
Customer support ───────────────────────────────────── 1-1
Platforms ─────────────────────────────────────────── 1-1
NX central runtime directory ───────────────────────────────── 1-1
System requirements guidelines ─────────────────────────────── 1-3
Operating system requirements ─────────────────────────────── 1-6
Supported hardware and graphics ───────────────────────────── 1-11
NX Open programs on Linux ───────────────────────────────── 1-12
Initializing the JVM ─────────────────────────────────────── 1-13
NX variables in the ugii_env.dat file ──────────────────────────── 1-15
Browser requirements ────────────────────────────────── 1-17
Browser requirements ───────────────────────────────────── 1-17
Licensing Caveats ──────────────────────────────────── 1-18
General licensing caveats ─────────────────────────────────── 1-18
Licensing caveats for Windows ─────────────────────────────── 1-19
Licensing caveats for Linux ────────────────────────────────── 1-20
Product compatibility - supported release combinations ──────────── 1-21
NX compatibility with Spreadsheet ───────────────────────── 1-24
NX applications unsupported on specific platforms ─────────────── 1-25
Support for touch enabled devices ────────────────────────── 1-26
NX Caveats and Product Notes

Teamcenter Integration for NX ───────────────────────────── 2-1
Product Notes ────────────────────────────────────────── 2-1
Caveats ────────────────────────────────────────────── 2-2
Fundamentals ─────────────────────────────────────── 2-2
Product Notes ────────────────────────────────────────── 2-2
Caveats ────────────────────────────────────────────── 2-4
Documentation Notes ───────────────────────────────────── 2-6
Customer Defaults ───────────────────────────────────── 2-6
Customer defaults ──────────────────────────────────────── 2-6
Design (CAD) ──────────────────────────────────────── 2-6
Modeling ───────────────────────────────────────────── 2-6
Staged Model ─────────────────────────────────────────── 2-6
Assemblies ──────────────────────────────────────────── 2-7
Product Template Studio (PTS) ──────────────────────────────── 2-8
Animation Designer ─────────────────────────────────────── 2-8
Drafting ────────────────────────────────────────────── 2-9
Layout ─────────────────────────────────────────────── 2-9
Technical Data Package (TDP) ───────────────────────────────── 2-9
NX 1953 Release Notes PDF, NX 1953 Series 5

© 2020 Siemens
Routing ───────────────────────────────────────────── 2-10
Routed System Designer ─────────────────────────────────── 2-10
Ship Structure ───────────────────────────────────────── 2-12
Sheet Metal ─────────────────────────────────────────── 2-12
Structure Designer ─────────────────────────────────────── 2-14
Human Modeling ─────────────────────────────────────── 2-14
PCB Exchange ────────────────────────────────────────── 2-15
Manufacturing (CAM) ────────────────────────────────── 2-15
Manufacturing Product Notes ──────────────────────────────── 2-15
Manufacturing caveats ──────────────────────────────────── 2-25
Additive Manufacturing ──────────────────────────────────── 2-33
Additive Manufacturing Process Simulation ──────────────────────── 2-35
CMM Inspection Programming ─────────────────────────────── 2-36
Manufacturing Planning ──────────────────────────────── 2-46
Line Designer ────────────────────────────────────────── 2-46
Fixture Planner ───────────────────────────────────────── 2-50
Assembly Line Planner ──────────────────────────────────── 2-52
Knowledge Fusion and DesignLogic functions ────────────────── 2-54
Product Notes ────────────────────────────────────────── 2-54
Validation ───────────────────────────────────────── 2-56
Check-Mate and Requirements Validation ───────────────────────── 2-56
Tooling Design ────────────────────────────────────── 2-56
Mold Wizard ─────────────────────────────────────────── 2-56
Progressive Die Wizard ──────────────────────────────────── 2-57
Press Die Checker ─────────────────────────────────────── 2-57
Data translation ────────────────────────────────────── 2-58
Product Notes ────────────────────────────────────────── 2-58
Caveats ───────────────────────────────────────────── 2-60
Mechatronics Concept Designer ─────────────────────────── 2-69
Product Notes ────────────────────────────────────────── 2-69
Automation Designer ────────────────────────────────── 2-70
Product Notes ────────────────────────────────────────── 2-70
Caveats ───────────────────────────────────────────── 2-72
Programming Tools ─────────────────────────────────── 2-75
NX Open ───────────────────────────────────────────── 2-75
Release upgrades ─────────────────────────────────────── 2-76
Product Notes ────────────────────────────────────────── 2-79

© 2020 Siemens
1. NX System Information
Customer support
Customers covered by valid maintenance agreements are eligible to receive customer support. If you are
a customer of one of our partners or resellers, please contact them first to determine your first line
support provider.
Our Customer Support team has the following mission: To increase our customer’s productive use of our
software by providing responsive and specialized support. You can find your local Customer Support
contact information and additional support information on Support Center.
Platforms
NX central runtime directory
Central runtime directory concept
To help you find executables and libraries, and distinguish them from configuration files more easily, a
central runtime directory that contains DLLs (or so's, or dylib's), executables, and JAR files is now used.
The central runtime directory will be updated as NX supports more and different applications.
Scripts that are used to wrap executables have not been moved and they are still in their original kit
locations with the configuration files.
NXBIN directory
The central runtime directory, NXBIN, is created on all platforms at the UGII_BASE_DIR\nxbin location
during the NX installation. Depending on what was selected to be installed, libraries and executables
from different kits are consolidated into the central runtime directory during the install process.
The new NX runtime directory does not contain all binaries and executables. Only the most frequently
used files from the following directories have been moved:
• UGII
• UGMANAGER
• STEP203UG
• STEP214UG
• PVTRANS
NX 1953 Release Notes PDF, NX 1953 Series 1-1

© 2020 Siemens
• MACH
Other files will also be moved over time. However, some applications, such as NX Nastran, will not be
moved.
While NXBIN does not contain all of the executables and DLL's, it does contain a large quantity and is a
prime location to search for an executable or library.
UGII_ROOT_DIR obsoleted
UGII_ROOT_DIR has historically been used to find the following in the UGII directory:
• Libraries and executables
• Configuration files
With the creation of the central runtime directory, there are two different locations for these files (nxbin
and ugii), so the concept of UGII_ROOT_DIR is obsoleted. Use the UGII_BASE_DIR variable instead when
you write custom application code and scripts.
While the NX install no longer sets UGII_ROOT_DIR, the definition on the system will remain to support
earlier releases. If your code or scripts rely on UGII_ROOT_DIR, modify them to ensure they still work in
this release.
Teamcenter code and scripts
To provide backward compatibility with released versions of Teamcenter, all executables called directly
by Teamcenter code or scripts are wrapped.
The wrapper executables just correct the settings of the UGII_BASE_DIR, PATH, and LD_LIBRARY_PATH
variables that are set by the Teamcenter scripts and code, and then start up the real executable from the
NXBIN directory. This enables support for the new runtime concept, while allowing NX to run with
existing versions of Teamcenter.
These new wrapper executables must remain in the ugii and ugmanager directories since that is where
Teamcenter code expects to find them. Two processes are shown for executables invoked from the ugii
and ugmanager directories.
Executables are still in the UGII, UGMANAGER, STEP203UG, STEP214UG, and PVTRANS kits.
Teamcenter code migration to the new central runtime directory structure is scheduled in a future
Teamcenter release.
1-2 NX 1953 Release Notes PDF, NX 1953 Series

© 2020 Siemens
System requirements guidelines
Defining the minimum system requirements is difficult because key requirements, most notably
memory, can vary dramatically from user to user. The following are general guidelines that you should
consider before purchasing a system.
Processor performance
Although raw processor speed has a major impact on system performance, other factors also contribute
to overall performance; for example, the type of disk drive (SSD, SCSI, ATA, or Serial ATA), disk speed,
memory speed, graphics adapter, and bus speeds. The general rule is that "the faster the processor, the
better the performance is," but this only applies when comparing like architectures. For example, it is
difficult to arrive at performance expectations for an Intel processor when compared to an AMD
processor just by looking at their respective processor speeds. There is also a general trend today to de-
emphasize processor speeds and move to multi-core processors, which actually can have lower
processor speeds.
NX takes advantage of modern processors, and if a processor does not have the required functionality,
you will see the following error message and NX will not run on the installed CPU:
This processor is too old and not supported anymore
SMP
Symmetric Multiprocessing (SMP) is supported in NX mostly via Parasolid, although a small number of
NX capabilities have some threading. In general, it is not possible to quote a figure for the general
performance improvement achieved by using SMP, since this improvement depends on the nature of the
operations you are performing. You need to evaluate your actual performance gains using your own
models. Functional areas that are SMP enabled in Parasolid include:
• Validity checking
• Boolean operations
• Wireframe
• Rendering
• Hidden line rendering
• Closest approach
• Faceting
• Mass properties

© 2020 Siemens
SMP is enabled by default with the variable UGII_SMP_ENABLE, which is located in the ugii_env_ug.dat
file.
Multi-Core
Multi-core processors are similar to SMP because there are two or more actual processor cores but they
are delivered in single processor packages. Siemens Digital Industries Software has found that multi-
core performance characteristics are similar to SMP. The one advantage of multi-core processors over
SMP is that this technology has proliferated much faster than SMP and is now common in workstations,
servers, and laptops.
Multi-core technology is complex and, depending on the configuration, can actually have a negative
impact on performance. This is due to the potential conflict of multiple cores sharing system resources,
such as cache, memory, and bus bandwidth, as well the need for the system to manage and control an
increasing number of cores. Increasing the number of cores does not always translate into better
performance. Although additional cores can improve NX performance, processor speed is still a vital
measurement of NX performance.
Many systems enable you to turn off cores via the bios, which can enable you to compare performance
with a different number of cores that are active. Some users may find that turning off some cores will
actually improve performance. One micro-architecture (Intel) even does this automatically, shutting
down unused cores and increasing the clock speed of the others.
The hardware vendors continue to improve their processor micro-architectures to better address the
limitations of older multi-core technologies. New subsystems better integrate memory and other
peripherals directly to the processors, resulting in major performance improvements. Buses are being
eliminated, cores are better managed, and channel speeds continue to improve.
In summary:
• Turn SMP on only if you have an SMP system. Having it on in a single-processor system incurs a slight
overhead.
• Turn SMP on if you have a multi-core system.
• Never assume that by simply adding more cores you will see better performance. Always test first.
Memory
The minimum recommended amount of memory to run native NX is 8GB. If you are running NX with
Teamcenter (Teamcenter Integration for NX), the minimum recommended is 12 GB. However, because
NX is capable of handling large assemblies and very complex parts, many of our customers use
workstations with 32GB of RAM, and some even use 64GB, 96GB, or more.
For the optimum user experience and application performance, we recommend that you install as much
RAM as can be installed in the client workstation that is running NX.

© 2020 Siemens
As a guideline, so that you get the best possible performance when using NX, ensure that the amount of
physical memory (RAM) in your workstations is always larger than the amount of memory consumed by
NX, plus all the other applications that are running at the same time on the same machine. This can be
done by using a tool such as Windows Task Manager or Resource Monitor.
The minimum memory requirements varies and depends on various factors including:
• Complexity of the geometry within individual parts
• Size of the assemblies that are loaded
• Less memory is required if the assemblies contain multiple instances of the same components.
• More memory is required when large assemblies contain lots of unique components with complex
geometry.
• Use of Teamcenter in addition to NX
• Some additional memory is required when using Teamcenter 4-tier.
• A even greater amount of memory is required when using Teamcenter 2-tier.
• Fully loading exact assemblies versus using lightweight assemblies and partial loading
• Generating CAM toolpaths for very complex geometry, such as an automotive engine block or
gearbox
• Updating large assembly drawings
Graphics adapters
All the NX certified systems contain graphics adapters that meet all Siemens Digital Industries Software
requirements and are fully supported by our hardware partners. The graphics adapters supported are
carefully selected by working with our OEM partners as well as our graphics vendor partners. We do not
recommend low-end, consumer, or game cards, since these graphics devices are developed for the
DirectX market and are not well supported under OpenGL. Because a majority of platform/hardware
problems are graphics related, it is critical that all the graphics adapters that NX supports are designed
for OpenGL and have the highest level of support from our hardware vendors. We highly recommend
that you only use supported graphics adapters and Siemens Digital Industries Software certified drivers.
For the latest information on certified graphics cards and driver versions, please visit the Customer
Support (GTAC) Web site.

© 2020 Siemens
Multiple monitors
Siemens Digital Industries Software supports multi-monitors but with limitations. These limitations were
necessary due to the large number of possible configurations. Other combinations may work, but these
conditions are tested and supported by Siemens Digital Industries Software. These guidelines could be
extended or relaxed in the future.
The following is a summary of findings for the support of multiple monitors.
• NX 6.0.1 or higher - no older releases are supported.
• Two monitors only.
• LCD monitors only
• Run with native resolution and aspect ratio.
• Laptops are tested without docking stations or port replicators (direct connection only).
• Horizontal Scan mode (not Vertical) and only with identical monitors.
• Dual View (Nvidia) or Extended View (ATI) modes, but the user must have the display window entirely
in either the primary or secondary monitor.
You do not have to comply with the configurations mentioned above, but Siemens must be able to
duplicate the problem on the configurations in our labs before being able to investigate your issues.
Operating system requirements
This section documents operating system and service pack requirements.
Minimum Operating Systems
The following operating systems are the minimum recommended for NX. Newer versions and service
packs are available as they are released.
O.S. Version
Microsoft Windows (64-bit) Microsoft Windows 10 Pro and Enterprise editions
Linux (64-bit) SuSE Linux Enterprise Server/Desktop 15
Red Hat Enterprise Linux Server/Desktop 7.6

© 2020 Siemens
Linux
Starting in NX 1847, NX is no longer supported on the Linux operating system for interactive NX (NX
running with UI), which includes graphics integration. It is only supported for running solvers and NX
Open batch programs with no user interface calls.
Contact GTAC for the new NX Linux product.
If you are using the SCL compiler on Red Hat Enterprise Linux, you need to do some additional setup.
See Programming Tools Product Notes for more information.
Mac OS X
Starting in NX 1847, the Mac OS X operating system is no longer supported.
Windows 10
Windows 10 is the minimum supported release for NX 1953. The supported versions of Windows 10 are
the Pro and Enterprise editions utilizing Semi-Annual Channel (SAC) updates.
Windows 10 is also available for NX 10.0.3 and later versions up to NX 1953. Any caveats or special
instructions are provided in the SFB announcing support.
Windows 7 and 8.1
Windows 7 has reached the end of life and mainstream support has ended. Windows 8.1 is still
supported by Microsoft, but was rarely deployed. These two versions of Windows are no longer
supported by NX 1953. Siemens Digital Industries Software has not performed testing on these versions
and cannot resolve any issues related to NX 1953 running on these operating systems. If NX 1953 is
deployed on these versions of Windows, any issues will have to be replicated on Windows 10 before
filing an incident report with GTAC.
System error when running NX
If you receive the following system error when launching NX, the problem is generally that the
operating system is not up-to-date for the required and optional updates. This error can occur with
Windows 7 and Windows 8.1.
The program can't start because api-ms-win-crt-heap-l1-1-0.dll is

missing from your computer.
The error occurs when there are missing Visual C++ libraries due to a dependency on the Universal CRT
libraries in Visual C++ 2015. To fix the problem, install the Visual C++ 2015 update 3 redistributable
from Microsoft. The 64-bit redistributable (vc_redist.x64.exe) is available in the INSTALL folder of the NX
runtime environment after installation, or you can download the redistributable from Microsoft.

© 2020 Siemens
If you still have a problem, contact GTAC support.
Linux Distributions
NX is developed using Linux standards and accepted Linux development conventions. Quality assurance
testing is performed on the two versions of Linux listed in the table above. Siemens PLM Software
cannot guarantee operation, performance, compatibility, or support on any other distributions.
The following is a list of information about the development environment (for reference only):
Kernel kernel 3.10.0-957.eI7.x86_64

C, C++ Compiler gcc 7.3.1
Java Development version 1.8.0_45
Considerations and caveats
Linux Requirements
NX supports SuSE Linux and Red Hat Linux, both 64-bit only. The minimum supported version of SuSE
Enterprise (Desktop/Server) is 15 and Red Hat Enterprise (Desktop/Server) is 7.6. Newer versions will be
supported via certification.
Visit the Customer Support (GTAC) Web site for details of supported hardware configurations as well
as for the latest graphics drivers.
Java Runtime Environment
The Java Runtime Environment (JRE) is not shipped with NX, but NX does require JRE 8 for certain
products.
To download and install the JRE, visit the Oracle JRE site at http://java.com/en/download/index.jsp, or
the AdoptOpenJDK JRE site at https://adoptopenjdk.net/releases.html?
variant=openjdk8&jvmVariant=hotspot.
Java is used for the following products:
• NX Relations Browser
• Manufacturing – Process Studio Author
• Command line version of the following translators:
• CATIA V4
• CATIA V5

© 2020 Siemens
Considerations and caveats
• Dxfdwg
• IGES
• NX Pro E
• Step AP203
• Step AP214
• Knowledge Fusion ICE
• Quality Dashboard
• Validation Rule Editor
• Simcenter 3D Batch Mesher
• Simcenter 3D Response Analysis Function Tools
• Simcenter 3D Report Writer
• Customer written NX Open Java programs
Java requirements for NX Open
NX Open for Java is designed to be used with Java version 1.8.0_45 or higher.
Post Processing of Abaqus ODB format results
In the NX release, NX uses Abaqus version 6.12 libraries to process ODB results files. For NX to use these
libraries, you must first install Visual C++ 2008 X64 Runtime – v9.0.30729.4967.
Note:
If you have Abaqus version 6.12 installed on your system, the required Visual C++ runtime should
already be installed.
You can download this runtime from the Simulia customer support website: http://www.3ds.com/
products-services/simulia/support/
For more information on the system requirements for ODB version 6.12 files, see: http://www.3ds.com/
support/certified-hardware/simulia-system-information/abaqus-612/system-requirements-for-
abaqus-612-products

© 2020 Siemens
Running Samcef in parallel
On Windows, when you run parallel computations with the built-in Samcef solver, Python 2.7 is
required. In NX 1953, that version of Python is not present. Install Python 2.7 on your disk and ensure
that the Python directory is named Python27 (default name) and is included on your PATH variable.
You can download the software from the Python website: https://www.python.org/downloads/
Note:
The Python requirement does not apply if you have Samcef installed separately from NX.
Configuration files
Starting in NX 12, the NX configuration files on Windows are written to C:\users\<name>\AppData

\Local\Siemens.
Installing the .NET Framework
The NXOpen for .NET API is a Windows-specific project that leverages the Microsoft .NET Framework
component. Before you can execute a custom .NET application, you must install .NET Framework 4.7.2.
In addition, to replay a .NET journal, the .NET Framework 4.7.2 must be installed.
To download .NET Framework 4.7.2, use the links on this page: Microsoft .NET Framework 4.7
(Web Installer).
Visual Studio runtime redistributable
To run NX 1953, the MS Visual Studio 2019 runtime redistributable is required. In addition, the MS
Visual Studio 2013 runtime redistributable is required to properly setup some system dll files for some
of the older executables.
You can download the Visual Studio 2019 redistributable here.
You can download the Visual Studio 2013 redistributable here.
Note:
If you have MS Visual Studio 2019 and 2013 installed, you don't need to download and install the
redistributable.

© 2020 Siemens
Supported hardware and graphics
Supported hardware and graphics
The list of currently supported hardware and graphics cards can be found on the Support web site,
when you click Hardware & Software Certification→NX Certifications→NX. This opens a spreadsheet
that has tabs for supported systems and graphics.

© 2020 Siemens
NX Open programs on Linux
If you try to link an external NX Open C++ program using the ufmenu and uflink scripts with NX 1953
on SLES 15, Linux may fail with an error message such as:
/usr/x86_64-suse-linux/bin/ld: cannot find -lelf
For NX to properly build an NX Open program, you must have the correct RPM kits installed.
For NX 1953 and SUSE 15, the following packages are required:
elfutils-0.158-6.1.x86_64.rpm
libelf1-0.158-6.1.x86_64.rpm
libelf-devel-0.158-6.1.x86_64.rpm
For NX 1953 and RedHat 7.6, the following packages are required:
elfutils-libelf-0.172-2.el7.x86_64.rpm
elfutils-libelf-devel-0.172-2.el7.x86_64.rpm
elfutils-devel-0.172-2.el7.x86_64.rpm
elfutils-libelf-0.172-2.el7.x86_64.rpm
elfutils-libs-0.172-2.el7.x86_64.rpm
Note:
For SUSE, the devel packages are available from the optional SLE 15 SDK DVD/ISO.

© 2020 Siemens
Initializing the JVM
Initializing the JVM
In some cases, NX is not able to create the Java Virtual Machine (JVM) properly on Windows. The root
cause in these scenarios is insufficient memory to start the JVM. In most cases of insufficient memory
Java is able to report back an error code indicating this problem. However, in some cases Java reports a
generic error message that NX then displays. The typical error message is:
Can’t initialize the Java Virtual Machine (JVM)
When running a Java application, such as the Wave Browser or Interactive Class Editor, NX may give an
unexpected error due to this problem.
If NX detects that there is not enough memory available for the JVM, an error message is given and
information is provided in the syslog. The following is an example of the syslog information:
The JVM could not be created due to not enough memory.

The Java heap size must be contiguous and the largest contiguous block
available is outputted below.
Windows largest block free
=================================
Maximum block 267Mb
=================================
Please note, this number is to be used as suggestion for setting the
heap size. It
is unlikely that you will be able to utilize the full amount.
If you need a heap size larger than what is possible you can try to use
the /3GB
switch or its equivalent, if available for the Operating System you are
on.
Otherwise your other option is to use Remoting. Please consult the NX
Open
Programmer's Guide for more information on this topic.
Reset the size of the Java heap
To remedy this problem, you can reset the size of the Java heap that NX uses. Choose
File→Execute→Override Java Parameters to open the dialog box and set UGII_JVM_OPTIONS to the
size of the Java heap. You can experiment with the size of heap that you need, but if the JVM is already
started then you cannot change the UGII_JVM_OPTIONS setting.
It is recommended that you use both the –Xmx and –Xms options together. Both of these are needed as
Java may determine default values for the heap size that are not possible with the machine’s current
memory load. For example:
UGII_JVM_OPTIONS=–Xmx50M –Xms50M

© 2020 Siemens
When trying to determine the size of the heap, keep in mind that if the heap size is too small, a Java
program you are trying to run may not run. This could be due to the amount of memory available on the
machine, or due to multiple Java processes running. This can be the case with the Wave Browser where
there is a client and server process.
Once you find a value that works, you can modify the UGII_JVM_OPTIONS value in the ugii_env.dat file
so you don’t have to reset it in the NX Open Java Parameters dialog box each time you start an NX
session.

© 2020 Siemens
NX variables in the ugii_env.dat file
NX variables in the ugii_env.dat file
Standard and modified environment variables
The ugii_env_ug.dat file contains the standard environment variables for NX. You can override these
variables with the ugii_env.dat file. This file is essentially empty when delivered. You can define new
values for the environment variables in this file and they take precedence over the values defined in the
ugii_env_ug.dat file.
The ugii_env.dat file should be used to modify any standard NX environment variables or add new ones.
Both the ugii_env_ug.dat and ugii_env.dat files are located at <UGII_BASE_DIR>\ugii.
Note:
You can make all, some, or none of the changes to the variables in the ugii_env_ug.dat file.
However, it is recommended that you use the ugii_env.dat file to define all of the values in use at
your site.
Using the ugii_env.dat file
The following apply when using the ugii_env.dat file:
• Define the variables before the #include statement.
• The first variable defined is used. If you have the variable defined twice in the file, only the first one is
used.
Note:
This also applies to the ugii_env_ug.dat file.
• You cannot have spaces in the variable names.
Designate a single ugii_env.dat file for all users
You can place the ugii_env.dat file in a central location for all users to access.
For each user, set the environment variable UGII_ENV_FILE to the location of the file. For example:
UGII_ENV_FILE=G:\common\version_env_vars.corp_standards

© 2020 Siemens
Note:
The file can have any name but must be a fully qualified path.
Statements you can use in the ugii_env.dat file
The statements that you can use in the ugii_env.dat file are shown below with examples:
• #if/#else/#endif
Used to check for specific conditions and then to define variables based on those conditions.
Conditions that can be checked are:
• FILE - Check for the existence of a file
#if FILE ${UGII_BASE_DIR}\UGII\html_files\start_${UGII_LANG}.html

UGII_CAST_HOME=${UGII_BASE_DIR}\UGII\html_files\start_$
{UGII_LANG}.html
#else
UGII_CAST_HOME=${UGII_BASE_DIR}\UGII\html_files\start_english.html
#endif
• platform - Check for a specific platform. Possible values:
x64wnt
lnx64
macosx
#if lnx64
UGII_CAM_THREAD_MILL=${UGII_CAM_THREAD_MILL_DIR}thrm.so
#endif
• $variable = “value” - Check for a specific value for a previously defined environment variable
#if $UGII_LANG = "simpl_chinese"

UGII_COUNTRY=prc
UGII_COUNTRY_TEMPLATES=$UGII_BASE_DIR\localization\$UGII_COUNTRY
\simpl_chinese
#endif
• $variable != “value” - Check for a previously defined environment variable that does not have the
specified value.
#if ${UGII_PACKAGE_DIRECTORY} != ""

#if FILE $UGII_PACKAGE_DIRECTORY\ugii_package_env.dat

© 2020 Siemens
Browser requirements
#include $UGII_PACKAGE_DIRECTORY\ugii_package_env.dat
#endif
#endif
• #include
Used to include a specified environment file at the current location
#include $UGII_PACKAGE_DIRECTORY\ugii_package_env.dat
The NX suite of documentation (Help, What's new Guide, and Release Notes) is provided in an HTML
format that is displayed in your local Web browser.
There are three ways to access the NX documentation:
• Directly on the internet from Support Center (requires login)
• Install the Secure Documentation Proxy, which allows access to documentation on Support Center
without logging in or creating a Wekey account. This eliminates the need and overhead of installing
documentation locally while still providing secure access.
• Install the Siemens Digital Industries Software Documentation Server, which sets up a web server on
each workstation or on your company intranet. For requirements, see Siemens Help Server for
Windows.
The latest versions of web browsers are recommended to comply with the latest browser security
updates.
Windows browser support
• Google Chrome
• Microsoft Edge
• Mozilla Firefox
• Internet Explorer
Downloading browsers
These browsers are free and can be downloaded from the following Web sites:

© 2020 Siemens
Chrome — http://www.google.com/chrome
Internet Explorer and Edge — http://www.microsoft.com
Firefox — http://www.mozilla.org
Licensing Caveats
General licensing caveats
License files and license server
The following are applicable to license files and the license server:
• Merging of license files is not supported.
Example:
You can not merge a pre-TC 2007 MP3 or pre-NX 5 license file, which uses the uglmd license
daemon, with a TC 2007 MP3, NX 5, or NX 6 license file, which uses the ugslmd daemon.
NX requires and tests for the latest version of the ugslmd vendor daemon. This vendor daemon is
supplied with NX and must be installed and initiated prior to starting NX. If an older daemon is
utilized, a generic NX License Error dialog box is displayed during start-up. In addition, the syslog will
contain an error message that the daemon version is older than the client.
NX Borrowing is version specific
NX license borrowing is version specific due to dependencies within the third party licensing software
used by Siemens PLM Software. To ensure that NX works on a borrowed license, you should always
utilize the borrow tool supplied with that NX version. For example, a license borrowed using the NX
1847 borrowing tool will work for NX 1847 but cannot be used to run NX 12. In addition, you cannot
borrow licenses for two NX versions simultaneously on the same workstation.

© 2020 Siemens
Licensing caveats for Windows
Licensing caveats for Windows
The following caveats are applicable to Windows platforms only.
License Option tool
The License Option tool should only be used to borrow NX licenses, even though it may display other
licenses. The License Option tool does not filter features in the license file that are of an earlier version
than NX, such as Teamcenter lifecycle visualization, so these licenses are displayed in the tool. If you try
to borrow a license for an application other than NX, you get an error when you launch the non-NX
application.

© 2020 Siemens
Licensing caveats for Linux
Additional software to support licensing
SuSE and Red Hat require the following to be installed:
• LSB 4.0

© 2020 Siemens
Product compatibility - supported release combinations

Teamcenter and NX
The following table lists the version combinations of Teamcenter, Active Workspace, and NX that are
supported.
Note:
• TC is Teamcenter
• AW is Active Workspace
• The Teamcenter release that is compatible with NX is identified in the table. If no patch is
specified in the table cell, then the base release is the minimum required.
If a patch is required, then the Teamcenter patch level specified in a table cell is the minimum
required for that Teamcenter release. Later patch levels in that release are also applicable,
unless otherwise specified. For example, TC 11.4.0_patch_5 is the minimum patch level in the
Teamcenter 11.4.0 release, and also includes patch_6, patch_7 and so on, that is, TC
11.4.0_patch_5 or later.
• The NX release identifies the minimum update in that series, where applicable. For example,
the NX 1847 series specifies the NX 1851 update as the minimum.
NX 1847 NX 1872
NX 12.0.2 Series Series NX 1899 Series NX 1926 Series NX 1953 Series
Teamcenter UA TC 10.1.7
10.1 AW 3.3.1
AW 3.4
TC TC TC
11.4.0_patc 11.4.0_patc 11.4.0_patc
h_5 h_5 h_15
AW 3.4 AW 4.0.4 AW 4.0.4
Teamcenter UA AW 4.0.4 AW 4.1 AW 4.1
11.4 AW 4.1 AW 4.2 AW 4.2
AW 4.2
AW 4.0.4 AW 4.0.4 TC TC TC TC
AW 4.1 AW 4.1 11.5.0_patc 11.5.0_patch_10 11.5.0_patch_10 11.5.0_patch_1
Teamcenter UA AW 4.2 AW 4.2 h_10 AW 4.0.4
11.5 AW 4.0.4 AW 4.1 AW 4.1 AW 4.1
AW 4.1

© 2020 Siemens
AW 4.2 AW 4.2 AW 4.2 AW 4.2

AW 4.3.3 AW 4.3.3 AW 4.3.3 AW 4.3.3
NX 12.0.2 NX 1851 TC TC TC TC
MP5 update 11.6.0_patc 11.6.0_patch_4 11.6.0_patch_4 11.6.0_patch_4
TC TC h_4 AW 4.1 AW 4.1 AW 4.1
11.6.0_patc 11.6.0_patc AW 4.1 AW 4.2 AW 4.2 AW 4.2
Teamcenter UA h_1 h_1 AW 4.2 AW 4.3.3 AW 4.3.3 AW 4.3.3
11.6 AW 4.1 AW 4.1 AW 4.3.3
AW 4.2 AW 4.2
Teamcenter UA
12.0 AW 4.1
AW 4.2
NX 12.0.2 NX 1851 TC TC TC TC
MP5 update 12.1.0_patc 12.1.0_patch_4 12.1.0_patch_4 12.1.0_patch_4
TC TC h_4 AW 4.1 AW 4.1 AW 4.1
12.1.0_patc 12.1.0_patc AW 4.1 AW 4.2 AW 4.2 AW 4.2
Teamcenter UA h_1 h_1 AW 4.2 AW 4.3.3 AW 4.3.3 AW 4.3.3
12.1 AW 4.1 AW 4.1 AW 4.3.3 AW 5.0 AW 5.0 AW 5.0
AW 4.2 AW 4.2
NX 12.0.2 NX 1851 AW 4.2 AW 4.2 AW 4.2 AW 4.2

Teamcenter UA MP5 update AW 4.3.3 AW 4.3.3 AW 4.3.3 AW 4.3.3
12.2 AW 4.2 AW 4.2 AW 5.0 AW 5.0 AW 5.0
AW 5.1 AW 5.1
TC TC TC TC
12.3.0_patc 12.3.0_patch_1 12.3.0_patch_1 12.3.0_patch_1
Teamcenter UA h_1 AW 4.3.3 AW 4.3.3 AW 4.3.3
12.3 AW 4.3.3 AW 5.0 AW 5.0 AW 5.0
AW 5.1 AW 5.1
Teamcenter UA
12.4 AW 5.0 AW 5.0 AW 5.0
AW 5.1 AW 5.1
Teamcenter UA
13.0 AW 5.0
AW 5.1
Teamcenter UA
13.1 AW 5.1 AW 5.1

© 2020 Siemens
Note:
For information on version compatibility for Teamcenter and Teamcenter lifecycle visualization,
see the Teamcenter documentation.

© 2020 Siemens
NX compatibility with Spreadsheet
NX Platform► Windows
version Spreadsheet software version► MS Excel MS Excel MS Excel MS Excel MS Excel
▼ 2019 2016 2013 2010 2007
Platform Operating Operating
▼ system▼ system For both 32–bit and 64-bit
version▼
NX Windows Windows 10 Pro and Certified Certified Certified Not Not
1953 10 64–bit Enterprise and and and supported supported
supported supported supported
Note:
• The 64-bit versions of Microsoft Excel are supported starting in NX 12.
• Microsoft Starter Edition is not supported by NX due to lack of support for Add-in's, Macro's,
Math and Equation Editing.
• If you launch a spreadsheet command such as Spreadsheet or Part Family on a system having
Excel 2003 or older version as the default spreadsheet application, NX displays an error
message and does not proceed with the launched command.
NX support for the currently supported versions of Microsoft Office will be discontinued as per the
following dates:
Microsoft Office version End of support

2007 October 11, 2017
2010 October 13, 2020
2013 April 11, 2023
2016 October 14, 2025

© 2020 Siemens
NX applications unsupported on specific platforms
NX applications unsupported on specific platforms

The applications listed are not supported on the specified platforms.
Application Functionality Platform not

supported on:
Tooling & Fixture Design NX EasyFill Analysis - Advanced Linux
NX Translators & Open Tools NX Open Python Author Linux
Electro-Mechanical Design Mechatronics Concept Designer Linux
Mechanical Design NX Drafting Linux
Mechanical Design NX Additive Design with Convergent Linux
Mechanical Design NX Layout Linux
NX Translators & Open Tools Content Migration Manager for SolidWorks Linux
NX Translators & Open Tools CMM Drawing Repair Assistant Linux
Electro-Mechanical Design ELMA Linux
Electro-Mechanical Design NX Piping Fabrication Drawings & PMI Linux
Mechanical Design NX Lattice Structures Design Linux
Mechancial Design NX Ship Structure PMI Creation Linux
Mechanical Design NX Ship Dimensions & Adv Annotation Linux
Mechanical Design Drawing Automation for NX (version 10 Linux
and later)
Mechanical Design Layout for NX Linux
Mechanical Design NX Aerospace Design Linux
Mechanical Design NX Lattice Structures Design Linux
Gateway Advanced Studio Rendering Style Mode Linux
Pre/Post Abaqus OBD result file reading Linux
Pre/Post Topology Optimization and Shape Linux Redhat
Optimization
Motion Motion Mechatronics co-simulation Linux

© 2020 Siemens
Support for touch enabled devices

In NX 1953, you can interact and manipulate 3D models and control the overall user interface using
touch screen and stylus. The support for touch enabled hardware follows a slightly different support
model than what is provided through the NX certification program. We have tested NX on a number of
Windows based touch screen laptops, monitors, and tablets. However, support for these devices and
other comparable systems is limited as they are not true workstations and do not qualify for our full
certification program. Support for these devices is limited as follows:
• Graphics performance issues are not supported as most of these devices do not offer the level of
driver support available on workstations.
• Graphics quality and display issues are not supported unless they can be duplicated on a certified
workstation.
• Any issue determined to be caused by the graphics driver is not supported.
• Performance issues with NX are not supported on these systems unless reproducible on certified
workstations.
Caveats aside, we have tested and used for development a variety of touch based systems from HP, Dell,
Microsoft, and others and have found them acceptable for general usage of NX.
Additional Notes
• NX supports touch devices on the Windows operating system.
• Only stylus configurations support pre-highlighting. The most commonly used devices supporting
stylus are the Surface Pros.

© 2020 Siemens
2. NX Caveats and Product Notes
Teamcenter Integration for NX
Product Notes
Refile utility is now retired
Historically, the NX product release has included the refile utility, which was created many years ago for
very specific data conditions and was never intended to be run by all customers on all of their data. This
utility was never mandatory when performing NX upgrades.
NX product enhancements and improvements that are delivered and available in the current NX release
make NX upgrades much faster and easier, so the refile utility is now obsolete. As a result, the refile
utility is retired starting in NX 12.0.1. The documentation for the utility has already been removed in NX
12.
In place of the refile utility, standalone utilities will be introduced that incorporate non-version-up
related options and future NX batch processes.

© 2020 Siemens
Caveats
Listing order for JT assemblies in Assembly Navigator
The listing order of items you have set in the Assembly Navigator is not maintained for JT assemblies if
you reopen the assembly. To get the set listing order for the JT assemblies, you need to save the top JT
assembly with the master dataset.
Assembly arrangements in Active Workspace
NX does not load the assembly arrangement from Active Workspace. The arrangement that was active
at the last save of the assembly into Teamcenter is loaded into NX.
Fundamentals
Product Notes
NX Virtual Reality display environment
The NX VR environment operates within the following display framework:
• The color of geometry comes from the NX component or object color (Edit Object Display→General
tab, Basic group→Color). Color does not come from the True Shading material, Studio material,
face, or facet color.
• Only solid-body, facet-body, and sheet geometry is displayed in the VR environment.
• The VR environment does not support translucency in the display.
• Geometry tessellation quality follows NX graphics window tessellation quality.
The following NVIDIA VR system is supported for NX Virtual Reality:
• Virtual Reality Systems, Components, Drivers | NVIDIA Quadro – https://www.nvidia.com/en-us/

design-visualization/solutions/vr-ready-systems/
Unit Manager settings
When you run the ug_convert_part tool to convert an NX 12 part from mm to inch, the settings in the
Unit Manager dialog box do not display the converted units. This is as intended.
The Units Manager dialog box displays the units that you have selected as the default units for data
entry and object information output. Those units are independent of the underlying part units (metric or
inch).

© 2020 Siemens
Product Notes
Cursor speed and shake gesture
Pressing MB1 and shaking the mouse from side to side is a new gesture called UGUI_MOUSE_SHAKE.
This new gesture is reported to GIT clients whenever a user shakes the mouse.
An API is implemented to provide the value of the pointer speed at a given mouse movement gesture.
This data is only valid if the current gesture is UGUI_PRE_POSITION or UGUI_DRAG_POSITION.
Navigate tool is retired
The Navigate tool is retired. You can explore your design in 3D space using Fly-through.

© 2020 Siemens
Caveats
Speech Recognition
You can use all languages to execute voice commands in NX except the following:
• Simplified and traditional Chinese
• Czech
• Hungarian
Voice commands may not work when you:
• Switch from one application to another in a single NX session.
• Create a command sequence that contains the Simulation (CAE) or Manufacturing (CAM) commands.
Note:
When you execute commands using speech recognition, you can move forward through a dialog
box by saying next. This is supported only for the group-based dialog boxes, such as Extrude and
Bend.
This navigation in the dialog boxes is not supported for other commands, such as, Open and
Curve.
Rendering an animation
NX does not support offline rendering of an animation solution that contains a User Defined animated
camera, with field of view change or zoom magnification change.
To render animations offline, you can use operations such as pan, rotate, or Fly-through to capture key
frames of the user-defined camera. To focus on specific viewpoints of the model, instead of zoom, you
can use Fly-through to position the camera as desired. For more information, in documentation, under
Viewing Objects see Fly-through.
NX Virtual Reality and Windows Mixed Reality
Windows update version 1809 creates multiple issues with NX VR and Windows Mixed Reality, including
drops in frame rate. We recommend that you update Windows to version 1803 or 1903 and later.
Bookmarks
If you create a bookmark file with Ray Traced Studio mode enabled, when the bookmark is applied Ray
Traced Studio mode is not in effect.

© 2020 Siemens
Caveats
If you create a bookmark file when displaying a View Section with clipping disabled, when the bookmark
is applied the section may be incorrectly clipped.
If you try to apply a bookmark file when
1. the bookmark file is not for the current displayed part and
2. the number of views in the layout at the time when the bookmark file was created is not the same
as the number of views in the current displayed part
then the number of views in the layout may be wrong after the bookmark file is applied. Applying the
same bookmark file a second time corrects the number of views.
3MF files with lattice bodies
3MF currently doesn't support ball specifications. If you import or export a 3MF file that has lattices with
balls or specified ball diameters, the balls are lost during the import or export operation.

© 2020 Siemens
Documentation Notes
Installing NVIDIA Iray Server
To obtain Iray Server, go to https://www.irayplugins.com/iray-server/ and follow the instructions for

downloading, licensing, and installing the Iray Server.
Customer Defaults
Customer defaults
Customer defaults allow you to customize the operation of NX. The initial settings and parameters of
many functions and dialog boxes are controlled by customer defaults. You can view them by choosing
File→Utilities→Customer Defaults.
For a description of the new or modified customer defaults, see Customer Defaults.
For additional information on customer defaults, see System administration→Customizing the NX

installation→Customer Defaults in the NX online help. For a listing and description of all customer
defaults, see Fundamentals→Customer Defaults in the NX online help.
Design (CAD)
Modeling
Caveats
Implicit Modeling
When you import a body that contains a shell feature from outside the task environment, it does not
generate the correct result. This will be resolved in the next major release.
Staged Model
Caveats
Staged Model Navigator
Clicking in the Current Feature column does not make that feature the current feature. Currently, you
should Right -click the Current Feature column and choose Make Current Feature.
Derived Stock
Derived stock is always oriented in the Z direction even if the parent stage is oriented differently.

© 2020 Siemens
Product notes
Assemblies
Product notes
Multi-user Design Notifications
In Teamcenter Integration for NX, you can use multi-user design notifications to follow parts, which lets
you receive notifications when another user saves those parts or checks them in or out. You can learn
about design conflicts as soon as they occur, and thus resolve them more quickly.
Multi-user design notification functionality requires both of the following:
• Your server needs a new microservice installation. For more information, please contact your Siemens
Digital Industries Software representative.
• You must set the Enable Multi-User Notification Service customer default.
Caveats
Convergent bodies with mixed geometry
Most Assemblies commands work well with convergent bodies that have a mixture of faceted
convergent geometry and exact geometry. The following commands have limitations as described:
• The Assembly Cut and Clearance Analysis commands don't work with combinations of convergent
bodies with mixed geometry and other convergent bodies as inputs.
• When creating assembly constraints in convergent bodies with mixed geometry, you must select
exact geometry.
Hide Similar Components and Show Similar Components
The new Hide Similar Components and Show Similar Components commands are designed to hide
and show similar piece parts, not subassemblies with children. However, if you alter the assembly
structure by adding or removing children and, later in the same NX session, use the Hide Similar
Components and Show Similar Components commands, some of the subassemblies may be included.
Simplify Assembly
The new Simplify Assembly command, which replaces the old Simplify Assembly wizard, has the
following caveat:
• Convergent and hybrid convergent bodies can't be selected for simplification or included in simplified
assemblies.

© 2020 Siemens
Minimal loading of JT files
You cannot minimally load a monolithic JT file in native NX as a component. You can minimally load a
monolithic JT file in Teamcenter Integration for NX when it is loaded as a component.
Minimally Load - Lightweight Display
The following caveats apply when you load assemblies using the Minimally Load - Lightweight Display
option:
• If you use this load option to load assemblies that have the following characteristics, the components
will be loaded partially instead of minimally:
• Pre-NX 9 components
• Geometry overrides
• Assembly-level facets
• The associativity between multi-CAD override geometry and NX objects, such as PMI, will not be
maintained when assemblies are loaded using the Minimally Load – Lightweight Display assembly
load option.
Product Template Studio (PTS)
Caveats
Product Template Studio (PTS)
PTS Author cannot be used (PR # 9868373)
Animation Designer
Product Notes
Import PLMXML enhancement
The Import PLMXML command is enhanced to better import legacy data from Process Simulate to
ensure the creation of rigid groups and joints.
Contact renamed
The Contact Face command is renamed to Contact.

© 2020 Siemens
Product Notes
Drafting
Product Notes
Sketch
Make sure that there is no active sketch when you enable the Sketch_NewSolverAndUI feature toggle.
Finish your active sketch before you enable the feature toggle.
Layout
Product Notes
Sketch
Make sure that there is no active sketch when you enable the Sketch_NewSolverAndUI feature toggle.
Finish your active sketch before you enable the feature toggle.
Create from 3D
When you use the Create from 3D command, you can now select lightweight components without
first setting the Load Smart Lightweight Data customer default. Assembly performance improvements
made that default obsolete in NX 12.0. Now smart lightweight data is loaded whenever NX needs it to
complete an action.
Limitation to using convergent bodies that have mixed geometry
The Create from 3D command is not supported for the convergent bodies that have mixed
geometry.
Technical Data Package (TDP)
Product Notes
Image support in TDPs
Only JPEG and PNG image files are supported in published technical data packages (TDP). TIFF images
are no longer supported.
If you open an existing TDP template that contains a TIFF image, a message is displayed. If you use the
template to publish a TDP without first removing the TIFF image, the image is not displayed in the TDP
and an error is written in the TDP log file.

© 2020 Siemens
Teamcenter support for TDPs
Technical data package datasets are supported in Teamcenter version 11.6 and up.
Routing
Caveats
• You cannot place a port on a convergent face.
• You cannot place overstock on the convergent face of a fitting.
Routed System Designer
Product Notes
When you single-select a routed segment to rotate using the Move Routing Objects command, and set
the Motion option to Angle , the segment length diminishes as you rotate it about an axis.
If you rotate the segment to a degree that the segment's length diminishes to zero, then that stock
component and any associated insulation is deleted. This behavior is expected. To alleviate the problem,
select the target segment's start and end RCP, as shown below.

© 2020 Siemens
Caveats
If you single-select the segment to rotate, then make sure you also select the Maintain Length check
box in the Settings group.
Caveats
• You cannot place a port on a convergent face.
• You cannot place overstock on the convergent face of a fitting.
• Do not apply assembly constraints to routing paths or insulation.
• Do not mix inch stock or insulation with metric parts, and vice versa.
• You cannot place a part with the Place Part command by referencing objects outside of the work
part.
• Port displays may not be consistent when the Routed System Designer part is not the displayed part.
• Runs do not show their discipline and specification in the Run Navigator columns outside of the
application in the no-part state. The discipline or specification must be loaded in Routed System
Designer.
• Part Template Studio (PTS) parts and stock are not yet supported.
• Connection compatibility is not yet supported in Routing specifications.
• Port engagements are not yet fully supported.

© 2020 Siemens
Ship Structure
Caveats
Sketch
The new Sketch solver is the default in NX 1953, but it is not recommended for ship design workflows.
We recommend that you enable the Sketch_UseClassicSolverAndUI early access feature.
Sheet Metal
Caveats
Patterning of a gusset on non-cylindrical bends
When a gusset is on a non-cylindrical bend, you cannot create a pattern of the gusset.
Note:
This is applicable only for gussets created using Automatic Profile.
To create a pattern of a gusset that exists on a non-cylindrical bend:
1. Extract the curve of the mold edge of the non-cylindrical bend.

For example, use Offset Curve in Face to extract the curve.
2. Use the extracted curve for defining the plane location and create a gusset.
3. Pattern the gusset using the extracted curve as a path.
Tip:
To do this, use Along in the Layout list.
Bridge Bend
You cannot create a bridge bend if the two sheet metal bodies intersect in the following way:
• A body from which you select an end edge intersects with the non-planar web face of the parent body
of start edge.

© 2020 Siemens
Caveats
1 Start edge
2 End edge
Convert to sheet metal
If you create a fold transition between the planar web faces of chained bends and convert the body to a
sheet metal part, the conversion may be partially successful.
Creating multiple flanges
While creating multiple flanges, if adjacent flange edges are not in the same set, you cannot apply an
internal miter.
Unite in Sheet Metal
If you unite bodies that consist of Sheet Metal and advanced Sheet Metal features, the united body may
not support subsequent Sheet Metal operations.
If you unite multi-thickness bodies, the united body may not conform to the selected layer scheme.
Material and Bend tables
The tool selection options are not available for the following commands and options.
• Hem Flange
• Lofted Flange
• Convert to Sheet Metal
• Bridge Bend→Type group→Z or U Transition

Bridge Bend→Type group→Fold Transition→Bend Properties group→Define By list→Length
option
• Advanced Flange→Type group→To Reference

© 2020 Siemens
Structure Designer
Caveats
Corner previews
In some cases, corners display inconsistencies between their preview and final result.
Corners between curve members
Corner results between curve members is not guaranteed.
This will be enhanced in a future release.
Product Notes
Beam Preparation
The Beam Preparation command will be made available in 1980.
Human Modeling
Product Notes
Predict posture algorithm updates for class A vehicles
In this release, the posture prediction algorithms for Class A vehicles are updated. The new models from
the University of Michigan Transportation Research Institute (UMTRI) now also consider the age and
gender of the occupant.
Documentation Notes
Hands-on learning aids in the online help
The online help now includes a limited number of hands-on procedures with part files to download,
which let you work through detailed instructions on your own. These hands-on procedures are a good
learning tool to try out new functionality and complex workflows. The procedure topics are titled
Hands-on: <Procedure name>.

© 2020 Siemens
Caveats
PCB Exchange
Caveats
Flat Solid workflow
The import and export of ECAD models in their bend state only works when the board is a solid body. If
the board is an assembly component this workflow does not work.
Manufacturing (CAM)
Manufacturing Product Notes
The Manufacturing product notes describe product changes that are not included in the What’s New in
NX documentation.
Tool path and template changes
Tool path changes
A general reminder: There are ongoing changes in the processors to fix problems, add enhancements,
and improve reliability. In many cases, you may see some differences between the new path and the old
path when you generate an operation from a previous release. If you rely on automatic methods, these
changes should be acceptable. The end result of the new path should be comparable to, or better than,
the previous path.
To prevent accidental changes to tool paths in part files from a previous release, use the Lock Tool Paths
During Version Upgrade customer default. This option automatically locks all operations with an edit
status of Complete or Repost.
Ongoing changes
As a result of customer feedback for the explorer tree format dialog boxes, there are ongoing changes to
parameter locations. To find a specific parameter, enter the parameter name in the box. As you
type, NX displays a list of matching entries that you can select from.
CAM configuration changes
• No changes
Operation template sets
• In cam_general.opt, added inspection.prt.

© 2020 Siemens
New inspection template part
The new inspection template part contains the following inspection operations:
• INSP_MISC
• INSP_SENSOR
• INSP_ALIGN
• INSP_FEAT_PLANE
• INSP_FEAT_CURVE
• INSP_FEAT_POINT
• INSP_FEAT_EDGE_POINT
• INSP_FEAT_SURFACE
• INSP_FEAT_PATTERN
• INSP_FEAT_CONE
• INSP_FEAT_SPHERE
• INSP_FEAT_ARC
• INSP_FEAT_CYLINDER
• INSP_FEAT_CIRCLE
• INSP_FEAT_TORUS
• INSP_FEAT_CPARLN
• INSP_FEAT_PARPLN
• INSP_FEAT_LINE
• INSP_PATH
• INSP_CONST
• INSP_TOL

© 2020 Siemens
• INSP_OUTPUT
mill_planar operation templates
FLOOR_FACING operation changes:
• Set the following default value:

Non Cutting Moves→Engage→Open Area→Engage Type = Arc
• Added the following:

Main→Main→Use Final Floor Stock Same As Part
• Removed the following:
• Wall Stock
• Wall Blank Thickness
• Extend Walls
• Wall Cleanup
• Finish Passes
• Cut Region Containment
• Exact Positioning
• CutCom
PLANAR_PROFILING operation changes:
• Added Non Cutting Moves→Start/Drill Points
PLANAR_MILL operation changes:
• Added Non Cutting Moves→Start/Drill Points
• Removed CutCom
CHAMFERING_MODELED operation changes:

Non Cutting Moves→Engage→Open Area→Engage Type = Arc

© 2020 Siemens
Main→Main→Use Wall Stock Same As Part
• Floor Stock
• Floor Blank Thickness
• Extend Floor To
• Specify Cut Area Floor
WALL_PROFILING operation changes:
• Set the following default values:
• Non Cutting Moves→Engage→Open Area→Engage Type = Arc
• Cut Regions→Cut Regions→Extend Walls =
• Main→Main→Use Wall Stock Same As Part
• Final Floor Stock
• Specify Cut Area Floor
• Across Voids
• Island Cleanup
• Region Connection
• Boundary Approximation
• Extend Floor to
• Cut Region Containment
• Merge Distance
• Simplify Shapes

© 2020 Siemens
WALL_FLOOR_PROFILING operation changes:
• Non Cutting Moves→Engage→Open Area→Engage Type = Arc
• Main→Main→Use Final Floor Stock Same As Part
POCKETING operation changes:
• Main→Main→Use Final Floor Stock Same As Part
• CutCom
mill_multi-axis templates
TUBE_ROUGH and TUBE_FINISH operation changes:
• Motion Output Type = Line
• Tool, Prg & Machine Control→Machine Control→Motion Output Type
MULTI_AXIS_ROUGHING operation changes:
• Start Point
• Return Point
ZLEVEL_5AXIS operation changes:

© 2020 Siemens
• Axis & Avoidance→Tool Axis→Axis
Tool templates
Milling Tool-5 Parameters and Milling Tool-Ball Mill tool changes:
• Tool tab→Dimensions→Relief Diameter
• Tool tab→Dimensions→Relief Length
Customized templates
If you create your own template files, you must back up the files before you upgrade to the current
release. Copy the template files from the templates folder (%UGII_CAM_BASE_DIR%\mach
\templates\) to a separate location to prevent the installation from overriding your defined
templates.
After the upgrade installation is done, copy your template files to the %UGII_CAM_BASE_DIR%\mach
\templates location.
Merging customized templates
You can merge your customized templates with the templates included in this release in the following
ways:
• Start with the new default templates and apply your customizations. This is highly recommended to
ensure you receive all the PR fixes.
• Re-file your customized templates in the new release, review the changes listed for the release, and
implement the applicable ones in your templates. This method is not recommended, because you will
not receive the PR fixes.
General changes
Sample part files
The links to the sample machines supplied with NX have been removed from the Manufacturing
Tutorials web page. Use the Manufacturing Machine Samples palette to access the sample
machines.

© 2020 Siemens
Milling
Machine Tool changes
The standard machine tools supplied with NX have revised postprocessors and kinematics models.
Review all existing Manufacturing setups which use a standard machine tool from a release prior to NX
8. If necessary, retrieve the machine tool again.
Milling
Cut Plane Transfer feedrate
Now, when you set the Transfer Type moves to Cut Plane for planar operations, the Traversal feedrate
is set to Rapid by default.
Non Cutting Moves node→Transfer/Rapid→Within Regions→Transfer Type = Cut Plane
Planar Deburring
In the current release, Planar Deburring is available for preview without a separate license when you
turn on the Enables Planar Deburring early access feature.
(File→Utilities→Early Access Feature)
In future releases, Planar Deburring may require a separate license. At that time, the separate license
will be necessary to use any operations created during the preview period.
Integrated Simulation and Verification (ISV)
ISV Simulation
• External file simulation in Teamcenter Integration for NX uses the same file selection box as native
NX.
• The latest CCF files for the TNC and Fanuc controllers require the Python controller parser type.
When you set Implementation to Python, it is not necessary to redefine global variables inside the
driver. The driver obtains the variables directly from the kinematics model.
Note:
If you prefer the library parser approach, use the CCF files from NX 11. You must define global
variables inside the driver for this approach.
ISV Simulation, VNCK
NX now supports Virtual Numeric Control Kernel (VNCK) 4.5.5. VNCK 4.5.5 must be used because it is
certified for Windows 10.

© 2020 Siemens
VNCK 4.5.2 is no longer supported, and is not available in the Support Center download area for the NX
1953 release.
The Virtual Numeric Controller (VNC) machine data files, also known as the SRAM files, from earlier
releases are not compatible because the files are VNCK-version dependent. You must upgrade your VNC
machine data files to the VNCK 4.5.5 version. For more information, see Save VNCK machine data in the
Integrated Simulation and Verification (ISV) NX documentation.
The VNCK 4.5.5 installer and installation instructions are available at the following location:
Support Center→NX→Downloads→Select a Version=NX 1953 Series→NX 1953 Add

Ons→VNCK
ISV using CSE simulated controllers with Python parser
• The CSE Python parser is supported for Windows only.

This means that the standard examples supplied with NX will not run on non-Windows operating
systems. As a workaround: Inside the Machine Configurator, in the Global Settings dialog box,
change the Implementation setting for the MCF from Python to Library.
• For existing simulations using Python parser with encrypted files from older versions, for example NX
9 or NX 10, we recommend that you use the un-encrypted *.py files from the latest release.
Feature-based Machining (FBM)
Create Feature Process
If your organization prefers to use the previous version of the Create Feature Process command, turn
on the Enables the Classic Create Feature Process feature toggle in the Feature Toggles dialog box
(File→Utilities→Feature Toggles).
Manufacturing critical maintenance and retirement notices
Planned retirement of Post Builder application
In a future release, the Post Builder application will be under critical maintenance. There will be no
updates and no issues will be corrected. At that time, you can still run postprocessors built in Post
Builder, but we strongly recommend that you switch to the Post Configurator platform.
Template part files
The following template part files will be deleted in NX 1980:
• Die Mold (Essentials)
• Turning (Essentials)

© 2020 Siemens
Manufacturing critical maintenance and retirement notices
• Machinery (Essentials)
• Multi-Axis (Essentials)
• Mill Turn (Essentials)
Verify
There are newer options to validate tool paths.
Currently, the Verify command is visible by default. In a future release, Verify will be hidden by default.
You can use the Show Verify option in Customer Defaults to control the visibility as needed.
Planned retirement of NX Manufacturing Tutorials from all platforms
The Manufacturing Tutorials are in critical maintenance.
• In NX 1953 and later releases, the tutorials will not be updated, and no issues will be corrected.
• The tutorials will be completely removed in a later release.
The new Manufacturing Day One is planned to replace the existing tutorials. To view the Manufacturing
Day One content:
1. Launch NX.
Note:
The Manufacturing Day One tab is available on the Welcome Page when you launch the
complete NX suite or the NX Manufacturing application.
2. Click the Manufacturing Day One tab on the NX Welcome Page.
Planned retirement of Solid Edge CAM Pro Manufacturing Tutorials from all platforms
The Manufacturing Tutorials are in critical maintenance after the Solid Edge 2021 release.
• In Solid Edge 2022 and later releases, the tutorials will not be updated, and no issues will be
corrected.

© 2020 Siemens
• The tutorials will be completely removed in a later release.
New Manufacturing Day One content is planned to replace the existing tutorials.
Retirement of Create Feature Process type Template Based
In the Create Feature Process dialog box, the Template Based option has been retired in NX 1953.
Manufacturing Wizard Builder
The Manufacturing Wizard Builder is on critical maintenance. It is a plug-in for the Process Studio Author
(PSTUDIO) application, which is no longer being developed. The 32 bit version is included in the NX
installation, and there is no plan to discontinue this.
The location in the Windows start menu has changed. Choose Start→All Programs→Siemens
NX→Manufacturing→Process Studio Author
There are no plans to discontinue CAM Wizards, which are xml files based on our block based UI
architecture.
Point To Point planned retirement from all platforms
Point To Point is in critical maintenance. The Drill template has been hidden by default, but is still
available.

© 2020 Siemens
Manufacturing documentation notes
Manufacturing documentation notes
Hands-on learning aids in the online help
The online help now includes a limited number of hands-on procedures with part files to download,
which let you work through detailed instructions on your own. These hands-on procedures are a good
learning tool to try out new functionality and complex workflows. The procedure topics are titled
Hands-on: <Procedure name>.
Note:
Make sure you are not in the Welcome role when you work through a hands-on procedure.
Manufacturing caveats
General caveats
Machining Feature Navigator
The Machining Feature Navigator is sometimes empty for parts loaded in the Manufacturing
Compare Tool Navigator. As a workaround, right-click a column header in the Machining Feature
Navigator, and choose Apply Filter. This problem will be fixed in a future release.
Reflect Component
NX CAM does not support the Reflect Component assembly command. If you use any geometry from a
reflected component for your operation, the results may be unpredictable.
NX CAM plans to support the Reflect Component command in a future release.
NX process
When you exit NX, it may close the UI without stopping the process. There is no data on how
widespread this problem is.
Tilt Tool Axis
Problem Workaround
Shortest 2D distance to curve Use the 3D shortest

distance option.
For longer tool paths, the shortest distance calculation can become
unsynchronized.

© 2020 Siemens
Problem Workaround
The tilted tool path may have non cutting moves with lifts in regions None
where they are not needed, and the moves can cause gouges.
IPW
• A Generic Motion (GMC) operation does not change the machine mode state of the IPW. Adding a
Machine Control subop with a Set Modes event at the beginning of the GMC operation does not
change the machine mode state of the IPW. The previous machine mode, either milling or turning,
remains active.
If the preceding operation does not have the required machine mode, you must add an operation
with the required machine mode before the Generic Motion operation. For example, if the Generic
Motion operation is for turning, add a turning operation. The new operation must generate tool path,
but does not need to cut material.
Note:
This is not a limitation in ISV when you use the CSE driver. The machine state is defined by the
workpiece spindle setting, which is either turning or milling.
Milling caveats
Rotary Floor milling
Problem Workaround
The Min. Lead Angle does not influence the tool path. None
Multi Axis Roughing
Problem Workaround
The Custom Feed and Speed parameter To control the engage feed rate during the helical
values specified for the Helical and Plunge or plunge move, do the following:
engage types are not output in the G code.
The engage motions use the specified Cut 1. Select the Feeds & Speeds node.
feed rate.
2. In the Feed Rates group, under More, define
an Engage feed rate.
Turning caveats
Multi-channel Turning
You must synchronize the program group before you simulate the machine.

© 2020 Siemens
Hole machining caveats
Right-click the program group and choose Tool Path→Synchronize
The Rough Turn Multi-Channel operation has the following limitations:
• When you use the following settings, the retract movement of the primary operation can cause
reduced spindle speed of the secondary operation.
Main node→Multi-Channel Turning group
Mode = Merged
Feeds and Speeds node→Spindle Speed group
Output Mode = SMM
• In the Tool Settings, Axis & CutCom node→Tool Orientation group:
• You must set the Tracking Point option to Automatic. Do not use the default setting of Rotate
With Holder.
• When you set the Reorient Tool Holder option to Fixed, the fixed value is passed to the secondary
operation. This can lead to an unwanted tool path for the secondary operation.
• The Display Tool Path command displays only the tool path of the primary Rough Turn Multi-
Channel operation.
• Turning on the Deactivates Sync Marks at End of Each Rough Cut in Multi-Channel Turning
Merged Mode feature in the Early Access Features dialog box can lead to an asynchronous state of
the machining process at the end of a selected program group or operation. For example, Channel 1
stops the spindle, even though Channel 2 still cuts material.
It is recommended to always turn this feature off.
Hole machining caveats
Tapping operations
Drilling and Tapping are distinct operation subtypes. Although tapping cycles are available in
the Drilling operation dialog box, we recommend that you do not use a Drilling operation combined
with a tapping cycle. The tapping cycles will be removed from the Drilling operation in a future release.
In a Tapping operation, you can set feature geometry parameters, such as pitch, that output the
required mom variables for tapping. If you use one of the tapping cycles in a Drilling operation:

© 2020 Siemens
• The operation will not contain the necessary feature geometry parameters and in-process feature
volumes for tapping.
• You will have the legacy Point to Point output where the pitch is driven by feed rate.
Back Counter Sinking operation
The Gouge Checking option reports false gouges.
ISV caveats
Multi tool collision warnings
Multiple function tools (multi tools) can be used in both spinning mode for operations such as milling or
drilling, and non spinning mode for operations such as turning.
If the cutting portions of individual cutters on a multi tool overlap, the inactive cutter can cause
misleading collision messages.
Non spinning display:
Spinning display:

© 2020 Siemens
ISV caveats
Synchronization Manager
In Windows 10, if you choose File→Exit to terminate the NX session, and the Synchronization
Manager dialog box is open, NX displays Parasolid error messages before terminating the NX session.
Visualize 2D Dynamic
• If blank geometry is not defined, you must click Step Forward twice before NX asks for blank
geometry.
• The 8-bit PseudoColor visual graphics driver mode is not supported. As a work around, change the
graphics X server settings. For example:
NVidia Quadro and FX graphics drivers
In the XF86Config file, in the Device section, set CIOverlay to TRUE.
Simulation
• In certain cases the reported minimum distance of a clearance violation is not the closest distance.
• Selecting a location on the tool path is now supported in ISV for both CSE-based simulation and tool
path simulation. Selecting tool path segments involving cycles, such as drilling cycles, may not work
in some cases.
There are also some cases in which the selected positions of rapid motions are not displayed correctly.
• When the simulation runs in the history buffer, and the spindle speed Output Mode for an operation
is set to SFM or SMM to maintain constant surface speed, the simulation behavior can be unreliable.
• When you use the Machine Code Based Simulation option for synchronized operations, Show Tool
Path is supported, but Path Segment Selection is not supported.

© 2020 Siemens
• When you use the Machine Code Based Simulation option in the sim09 machine tool, milling
operations using CYCLE800 may have unwanted 360-degree motions of the C-axis.
• When you use the External Program Simulation option, and you replace a machine, the
software removes the selected external main program from the Program Manager dialog box. You
then lose all changes in the edited main NC code program.
As a workaround, save your main program before replacing the machine.
CSE simulation
• When there are multiple workpiece objects, the tool trace is always attached to the first component
classified as _WORKPIECE, and moves with the component. If the tool trace is displayed on the wrong
component, you can reorder the kinematics tree to place the required _WORKPIECE component first.
NX uses the tool tip of the active tracking point, of the active tool, in the carrier.
• To set the active tracking point, use SetCorrectionSwitch/SetToolCorrection.
• To set the active tool, use activateNextTool.
• When dragging behavior is used (Kv >0), the display and the collision checking are not synchronized.
The graphical display uses the dragged positions.
Collision checking and material removal are based on the ideal interpolated values.
This means that NX may report a collision that is not directly visible inside the graphics window.
Virtual NC Kernel (VNCK)
• When it reaches a breakpoint, the simulation may fail to stop or may not stop at the exact position
specified.
• Although the VNCK versions 4.4, 4.5.2, and 4.7.4 are not officially released for Windows 10, they
usually run without any problems when you use HMI Operate. If the VNCK does not boot after
installing, please ensure that Windows Data Execution Prevention is not active for vncksl.exe and
vplc3172dp.exe.
1. Press the Windows key.
2. In the search box, type advanced system, and press Enter.
3. In the System Properties dialog box, click the Advanced tab.

© 2020 Siemens
ISV caveats
4. Under Performance, click Settings.
5. Click the Data Execution Prevention tab.
If the Turn on DEP for all programs and services except those I select option is selected, you must
exclude the vncksl.exe and vplc3172dp.exe files.
To exclude the vncksl.exe and vplc3172dp.exe files:
1. Click Add.
2. Select the vncksl.exe and vplc3172dp.exe executable files.
The default location for both files is the VNCK installation folder.
3. Click OK.
Note:
You must exclude the vncksl.exe and vplc3172dp.exe files for all installed VNCKs.
VNCK - NCK Power On Reset
In the Human Machine Interface (HMI), if you execute an NCK Power On Reset (warm restart) while the
simulation is stopped for any reason, the VNCK state and the simulation state in NX are not the same.
If you try to continue the simulation, or execute an NCReset, NCStop, or NCStart command, NX
displays the following Machine Tool Simulation message and aborts the action.
VNCK executed an externally triggered 'NCK Power On Reset (warm

restart)' while being in 'SIM Stop' mode. This is an unsupported use
case which created an inconsistent state. Shutdown and reboot VNCK to
heal this.
If this happens you must shut down and reboot the VNCK.
HMI Advanced
• HMI Advanced is not supported, because it is not supported on Windows 10.
Positional ISV — Show Machine Axis Positions dialog box
When the setup has a multi-function machine and you use the dynamic manipulator to change the tool
axis for a fixed-axis operation, NX does not update the Show Machine Axis Positions dialog box. To
avoid confusion, use the Show Machine Axis Positions customer default to suppress the dialog box.

© 2020 Siemens
1. Choose File tab→Utilities→Customer Defaults.
2. In the Customer Defaults dialog box, choose Manufacturing→User Interface.
3. Click the Dialog Boxes tab, and in the Visibility group, clear the Show Machine Axis Positions
Dialog check box.
Generate IPW with Path customer default
Using the Generate IPW with Path customer default may cause commands that require the IPW, such as
Verify, to have problems when the IPW is not complete. This can happen because the IPW takes more
time to generate than the operation.
Post Configurator
Heidenhain TNC PLANE rotation on non-orthogonal 5axis machine
The Real Machine Axis option for tilting plane kinematics does not work with non-orthogonal 5-axis
machines for Heidenhain TNC PLANE rotation. The SPA , SPB, SPC angles in the PLANE command
output could be wrong.
DEF File Editor
The editor removes comments from the main definition file, including any existing comments.
TCPM prepositioning plane
When this option is activated, the plane output for the prepositioning is wrong in the following case:
• There is only one MCS in the Geometry View of the Operation Navigator, and
• The MCS is defined as Local, and
• Special Output is set to None.
Feature based machining caveats
Teach Feature Mapping, Teach Operation Sets
Limitations and workarounds:

© 2020 Siemens
Product Notes
When you Teach Operation Sets does not Workaround

use
Run Teamcenter Integration for The correct operation subtypes • Manually add the missing tool
NX, and store the operation classes and operation subtypes
templates in Teamcenter to the generated machining
Use a library other than the The tool class rules using the Machining
native ASCII library, such as MRL Knowledge Editor.
or TDM
• Replace the missing subtypes
and classes. To do this:
1. (Optional) Change your

CAM configuration to use
native operation types
and the standard ASCII
tool library.
2. Use Teach Operation

Sets to teach the
operations.
3. Use the Machining

Knowledge Editor to add
or optionally replace the
tool classes and the
operation subtypes.
Additive Manufacturing
Product Notes
New version of Build Processor Interface
You must install the updated Build Processor Interface (BPI) 5.0.19.0 version when you upgrade to NX
1953. This installs the latest updated 3.1.00004.0 version of the Build Processor System.
You will get this message until you install the (BPI) 5.0.19.0 version: Incorrect version of the
Materialise Build Processor Interface.
Before you install the BPI 5.0 version, stop any Build Processor Manager process that may be running,
uninstall the old BPI version, and then install (BPI) 5.0.19.0 from this location: %UGII_CAM_BASE_DIR%
\mach\auxiliary\mfgam\BuildProcessorInterface.exe

© 2020 Siemens
Note:
You may need to resolve printers in the Build Processor Manager application, after you upgrade.
Templates
If you created your own template files in an earlier version of NX, you must do this before you upgrade
to the next NX version: copy the template files from the templates folder (%UGII_CAM_BASE_DIR%
\mach\templates\) to a separate location to prevent the installation from overriding your defined
templates.
After the upgrade installation is done, copy your template files to the %UGII_CAM_BASE_DIR%\mach
\templates location.
am.xml data
If you have custom support profiles in your current NX version and you want to upgrade to a newer NX
version, you must ensure that you migrate your am.xml data to the upgraded version so that your
custom profiles are available in the upgraded NX version. For detailed instructions, see Migrating the
am.xml file.
Shortcut key for switching to Additive Manufacturing
You can press Ctrl+Alt+Z to switch from another NX application to the NX Additive Manufacturing
application.
Caveats
Print marks
• Geometric bodies of print marks on all the non-nested parts get removed when you use the Add
Overflow Build Tray command to add another build tray for the non-nested parts. Generate the
geometric bodies for all print marks on the parts added to another build tray.
• When you use a 3D printer that does not support print marks with negative thickness value and you
try to generate geometric bodies for such print marks, NX displays a warning.
If you generate geometric bodies for print marks with negative thickness value and you switch from a
3D printer that supports such print marks to a 3D printer that does not support them, NX does not
display a warning and these print marks are excluded from the output file.
VB script for automatic overflow build tray and nesting
The MultiPlatformNesting.VB VBscript does not support Materialise printers.

© 2020 Siemens
Caveats
Support structures anchored to a lower part or user-defined support structures
• If you use the Pattern Supports command for support structures that are extended to a lower part or
user-defined support structures and pattern them to a part that does not have any lower part or user-
defined support structures, the patterned support structures are extended only to the length of the
original support structure instead of the build tray. Use the Regenerate Supports command to
properly update the support structures.
• If you use the Create Supports command to add line and point support structures using the
automatic support generation process, then the generated line and point support structures do not
get extended only to the lower part or user-defined support structure. Instead the support structures
pass through them to the build tray. Use the Regenerate Supports command to anchor the line or
point support structures to the lower part or user-defined support structures in the build tray.
• If you use the Move Part command to move a lower part that has an existing support structure
anchored on it, the support structure is not updated after you move the lower part. Use the
Regenerate Supports command to properly update the anchored support structures.
Note:
Support structures are anchored to a lower part or to user-defined support structures only if you
have set the Prevent creating supports intersecting other parts in the build tray feature toggle
to On in the Early Access Features dialog box.
User-defined supports
When you move a part that has user-defined supports, the part is moved, but the user-defined supports
do not move unless your user-defined supports reference part geometry, for example, edges or faces of
the part.
Heat Sink support attribute
The Heat Sink attribute is currently not visible for gusset support structures.
Additive Manufacturing Process Simulation
Caveats
• The software does not yet support automatically generating compensated/deformed geometry from
computed deformations, for models created with convergent geometry.
• The application will run on a localized version of NX, but the deformation results (in case of solver
slicing) must be selected manually, except for the English, German or French versions.

© 2020 Siemens
CMM Inspection Programming
CMM Inspection - New Features
Enhancement to 5-axis Scan Curve
NX 1953
You can now drag the probe for a 5-axis Scan Curve sub-operation in the graphics window to change
the probe angles. This enhancement makes it much easier to create 5-axis scan paths on complex
surfaces.
Scan lines on a plane
NX 1953
Use the new Scan Line sub-operation type to easily create scan lines on a planar face. Previous releases
required using the Modeling application to manually create the lines for these type of paths.

© 2020 Siemens
The Scan Line parameters are similar to the U and V parameters for the Point Set sub-operation type.
Scan arcs on a curve
NX 1953
Use the new Scan Arc sub-operation type to easily create scan arcs on cylinders and cones. Previous
releases required using the Modeling application to manually create the arcs for these type of paths.
The Scan Arc parameters are similar to the parameters for the Point Set sub-operation type.

© 2020 Siemens
Scan the boundary of a plane
NX 1926
You can now easily create a scan path that follows the boundary of a planar face. Previous releases
required using the Modeling application to manually create the boundary curves for these type of paths.

© 2020 Siemens
To create the scan path, do the following:
1. Choose Home tab→Insert group→Inspection Path.
2. In the Inspection Path dialog box, click Select Feature .
3. Select the feature to inspect.
4. Click Add Sub-Operation .
5. In the Create Sub-Operation dialog box, from the Move Type list, select Scan Curve.
6. In the Geometry group, from the Curve Selection list, select Boundary.
7. Specify the scan curve parameters, and click OK.
8. Click OK to save the inspection path.
Display Nearby Paths
NX 1926
NX can now display other paths in the CMM program as you create and edit an inspection path. In the
following example, the path being editing is displayed in blue. The paths before and after the active tool
path are displayed in gray.

© 2020 Siemens
To change the path display, right-click an object in the Inspection Navigator, and choose Path Display,
then one of the display options.
• Show Selected Paths Only
• Show Nearest Paths
• Show All Paths
Resequence Paths
NX 1926
The Resequence Paths command now has sequencing options.

© 2020 Siemens
• Head Angle Changes considers head angle changes when resequencing inspection paths.
• Tool Change considers tool changes when resequencing inspection paths.
• Distance to Path gives the same results as previous versions of NX.
Circular Arc Transition Moves
NX 1899
When programming inspection paths for round parts, you can specify the Transition Motion as Circular.
This will produce transition moves between inspection points that follow the curvature of the part.
Curve Scanning Improvements
NX 12.0.2 MP12, NX 1899

© 2020 Siemens
A curve that is defined in NX using multiple segments can now be inspected as a continuous scan with
control over the scan speed and point density for each individual segment. In the Curve Scan sub-
operation dialog box, a list of control points is presented. The list is pre-populated with control points at
the beginning and end of each curve segment. You can edit scan speed and point density at each
control point.
3-axis curve scan 5-axis curve scan
These settings are implemented in the DMIS 3.0, DMIS 5.2, and MODUS (Equator) postprocessors using
DMIS statements in the following format:
P(CURVE_SCAN_1)=PATH/CURVE,<point data for curve1>

PAMEAS/DISTANCE,<dist1>,SCNVEL,<speed1>,P(CURVE_SCAN_1),$
DISTANCE,<dist2>,SCNVEL,<speed2>,P(CURVE_SCAN_2),$
DISTANCE,<dist3>,SCNVEL,<speed3>,P(CURVE_SCAN_3)
Other postprocessors do not currently support these settings.
Data Elimination and Data Filtering
NX 12.0.2 MP10, NX 1880, NX 1899
Data elimination means the removal of measured data points, sometimes called outliers, that are
outside a range of standard deviations from the mean deviation. Data filtering means a high pass, low
pass, or band pass filter is applied to the measured data in order to isolate form deviation from surface

© 2020 Siemens
texture. You can enable these and set the parameters using new groups in the feature dialog boxes and
the method dialog box.
Example Meaning
Data elimination and filtering are turned off.
Data elimination based on a standard deviation

multiple.
Low pass data filter
High pass data filter
These settings are supported by the DMIS 5.2 postprocessor using a statement in the following format:
GEOALG/CIRCLE,LSTSQR,STDDEV_LIMIT,2.,FILTER,CIRCULAR,HIGH,15.,GAUSS
Other postprocessors do not currently support these settings.
Head Touch on Outer Circles and Cylinders
NX 12.0.2 MP10, NX 1880, NX 1899
Simulation of inspection paths using the PH20 in Head Touch mode has been improved for the following
feature types:
• CIRCLE/OUTER

© 2020 Siemens
• CYLNDR/OUTER
• GCURVE on the surface of a CYLNDR/OUTER
Verify Program
NX 12.0.2 MP10, NX 1880, NX 1899
You can now verify inspection programs before sending them to the shop floor for execution. Many
common errors are detected and reported in the NX information window.
• Feature not measured or constructed
• Datum not defined before a tolerance that references it
• Size tolerance missing when using MMC or LMC modifiers
Arc Scan using Rotary Table
NX 12.0.2 MP8, NX 1880, NX 1899
You can now perform arc scans by bringing the probe into contact with the part, then rotating the part
with the rotary table while holding the probe at a stationary XYZ. You can specify this on the Scan Arc
dialog box using the new Rotary Table choice for Scan Mode.
This is supported by the DMIS 5.2 postprocessor using a statement in the following format:
PAMEAS/P(CIRCLE1_PATH_Scan_Arc),ROTARY,RT(ROTARY1)
Other postprocessors do not currently support this statement type.
Support for Valisys programs
NX 12.0.2 MP8, NX 1880, NX 1899
Inspection programs written using Valisys (eM-ProbeCAD) may now be imported into NX CMM with
good success. Fewer than 10% of operations will need to be edited by hand. Support for the following
statement types was added in NX 12.0.2 MP8:
• DATSET statement
• MACRO and CALL statements
• CONST/POINT,…,BF
• Convert 3 character datum letters VP1,VS1,VT1 to valid datum letters

© 2020 Siemens
CMM release notes
• Option to ignore BND1,BND2,BND3,BND4,F(VBND and BOUND/
• Option to ignore Comments
• OUTPUT that isn’t a T() or F() format
• Valisys GEOALG formats
• GSURF/GCURVE Features
• Width Tolerance
• OUTPUT/R()
• TEXT/OPER
• ROTAB/
• SAVE/FA
CMM release notes
PAX file change
The .pax files are now located in the UGII_BASE_DIR\cmm_inspection\templates folder.
VALISYS critical maintenance and retirement notice
The VALISYS application is unsupported as of July 21, 2016. Use the NX CMM Inspection Programming
application instead of VALISYS Programming and use CMM Inspection Execution instead of NX-Inspect.
Linking to PMI information
All geometry referenced by PMI must be in the current reference set, and if it is not, then NX:
• Issues warning messages in the information window.
• May still create features, but will not create paths because there is no access to the feature geometry.
Caveats
Renaming or deleting the SENSORS group
In the Inspection Navigator, do not delete or rename the SENSORS group as this may cause machine
simulations within the Inspection Path dialog box to fail.

© 2020 Siemens
Machine simulation
When you create an inspection path or simulate a program, you may see the following INI Programs
message:
In order to handle INI files in the Program Manager, define the channels
in the Machine Tool Builder.
You can ignore this message for NX CMM Inspection applications. It has no effect on the machine
simulation.
Manufacturing Planning
Line Designer
Product Notes
Template files
To work in Line Designer managed mode, you must import the standard part files delivered with Line
Designer into the Teamcenter database, so you can access these files in the New Item dialog box. If you
do not perform this step, the New Item dialog box displays only blank templates.
A setup script for installing Line Designer templates in Teamcenter is included with NX:
%UGII_BASE_DIR%\MANUFACTURING_PLANNING\templates\tcin_linedesigner_template_setup.bat
For information about how to use the script, see Installing File New templates in the NX help at the
following location:
Home→
Teamcenter Integration for NX→
System Setup/Administration→
Server Setup/Administration→
Installing/creating/modifying templates→
Installing File New templates
Platform support
Line Designer is currently supported only on the Windows platform.
Data Upgrade
Due to changes in the connector design in NX 11 and NX 12, equipment that uses connectors created in
the previous versions should be upgraded to NX 12.0.2 MP5 or later format.

© 2020 Siemens
Product Notes
For more information, see Using library components with connectors from NX 12.0.2 MP5 or earlier in
the Line Designer caveats.
Manufacturing Planning Additions
Manufacturing Planning Additions includes Teamcenter extensions to support the following:
4GD Support Use of Line Designer with 4GD capabilities requires a Teamcenter extension called 4GD
Plant Design.
FactoryCAD Migrating libraries from FactoryCAD to Line Designer also requires a Teamcenter
Library extension to support new required dataset types. This extension is included in the
Migration Manufacturing Planning Additions package to Teamcenter installation
(TC12.x_MfgPlanningAdditions_3.0_wntx64.zip).
Find the MfgPlanningAdditions x.x package on Customer Support. Log on using your webkey
credentials.
If you need to request credentials, see the WebKey management page on the Support page.
Instructions for applying the MfgPlanningAdditions x.x package are included in the package .zip file. For
example, TC11.x_MfgPlanningAdditions_3.0_wntx64.zip
and TC12.x_MfgPlanningAdditions_3.0_wntx64.zip.
In Support Center, find the ManufacturingPlanningAdditions package in the following section:
Support Center→
Teamcenter→
Downloads→
Additional Downloads→
For example, from the Manufacturing Planning Additions list, choose Windows 64 and search for
TC12.x_MfgPlanningAdditions_3.0_wntx64.zip
Factory resource samples
Installation of the sample factory resources, conveyors, and robots from the manufacturing resource
sample library to Teamcenter is highly recommended.
Factory Resources
Factory Conveyors
Factory Robots

© 2020 Siemens
Factory Weld Guns
Instructions for installing the samples are located in the following section of the Teamcenter HTML
documentation:
Home→
Installing Teamcenter→
Teamcenter server Installation on Windows→
Adding Features→
Installing and configuring the Manufacturing Resource Library
Manufacturing Resource Library version compatibility
Line Designer supports the use of factory resources with compatible versions of Teamcenter and
Manufacturing Resource Library (MRL). You should find the latest version of MRL in the latest
Teamcenter release.
Note:
You should always upgrade the Manufacturing Resource Library components from the previous
release to the new release.
Documentation Notes
Note the following about the Line Designer documentation:
• Line Designer can work with BVR data structures, and the documentation describes BVR procedures
wherever required.
In the release notes, you can find Line Designer in the Manufacturing Planning section.
• Line Designer is now available to work in native NX. Please refer to the Line Designer Help
documentation for more details.
Note:
End Items support is currently not available in Line Designer in native NX.
Caveats
Configured components in the Plant Navigator
Configured out components from the plant structure appear as loaded components with no graphics in
the Plant Navigator.

© 2020 Siemens
Caveats
Using library components with connectors from NX 12.0.2 MP5 or earlier
While placing or disconnecting components in a layout, or while dragging components to another

layout, you may experience incorrect behavior if those components have connectors created in NX 11 or
earlier.
Recommend Before using the library objects in NX 12.0.2 MP5 or later Line Designer layouts, you
ation should upgrade any part files of the library objects that include connectors created
before NX 12.0.2 MP5. To do this:
• Open the library objects in NX.
• Open the Edit Connector dialog box for each connector.
• Click OK.
• Save the library objects in the later version.
Loading the plant layout with connected components
While loading the plant layout with connected components, you may observe the components as
disconnected with Save and Close options disabled. The remedy to this issue is to restart the NX
session, and again load the same plant layout.
Creating occurrence poses
When you create occurrence poses for the components, NX shows no modifications for the parent
component in the tree structure, in the Plant Navigator. Also, if the state of the component for which
you create occurrence poses is Released, you may observe an issue that you can still create and save the
occurrence pose.
Deleting the connected components in a layout
When you work in managed NX, and you load a plant layout and then delete any component that is
connected to another component, NX deletes all the connections in the layout.
This issue is fixed in Teamcenter 11.6.0.10, Teamcenter 12.2.0.5, and Teamcenter 12.3 and later.
Modifying the kinematic components
In a kinematic assembly, when you jog the component joints, NX displays the component as modified.
The issue is fixed in a later release.

© 2020 Siemens
Fixture Planner
Product Notes
Template files
The Open dialog box displays only installed templates. You must import the standard template part files
delivered with Fixture Planner into the Teamcenter database, so you can access these files in the Open
dialog box. Other templates are not configured to work with Fixture Planner.
A setup script for installing Fixture Planner templates in Teamcenter is included with NX:
%UGII_BASE_DIR%\MANUFACTURING_PLANNING\templates\tcin_fixtureplanner_template_setup.bat
For information about how to use the script, see Installing File New templates in the NX help.
Platform support
Fixture Planner is currently supported only on the Windows platform.
Manufacturing Planning Additions installation
Using Fixture Planner with Teamcenter also requires you to install the Manufacturing Planning Additions
package to the Teamcenter server installation (for example, MfgPlanningAdditions 3.0).
ManufacturingAdditions 2.5 and later supports the Fixture Planner in NX 1953.
Find the MfgPlanningAdditions x.x package on Customer Support. Log on using your webkey
credentials.
If you need to request credentials, see the WebKey management page on the Support page.
Instructions for applying the MfgPlanningAdditions x.x package are included in the package .zip file. For
example, TC11.x_MfgPlanningAdditions_3.0_wntx64.zip
and TC12.x_MfgPlanningAdditions_3.0_wntx64.zip.
In Support Center, find the ManufacturingPlanningAdditions package in the following section:
Support Center→
Teamcenter→
Downloads→
Additional Downloads→
For example, from the Manufacturing Planning Additions list, choose Windows 64 and search for
TC12.x_MfgPlanningAdditions_3.0_wntx64.zip

© 2020 Siemens
Documentation Notes
Data requirements for Export
When you export the study, NX generates the required data before the export, once you save the study
in Fixture Planner.
Note:
You should perform Save All for the study in NX, so you can see all the required part files in the
study.
Importing Fixture Data
You can make changes in the fixture assembly data in native NX and then import only the fixture
assembly in managed NX. This import allows the exchange of the relevant changes within the fixture
assembly, and lets you update the planning scope of Fixture Planner.
Data requirements for Import

After you make changes in the fixture assembly in native NX, when you import back the changes of
the fixture assembly to managed NX, the scope of the import should be the Fixture Assembly only,
and not the study.
Documentation Notes
Note the following about the Fixture Planner documentation:
• In the release notes, you can find Fixture Planner in the Manufacturing Planning section.
• Fixture Planner is now available to work in native NX with limited capabilities. Please refer to the
documentation for more details.
Caveats
Loading the study with assembly load options
In Fixture Planner, while loading a study using assembly load options, you may observe the different
behavior for the minimal load and the partial load option.
Note:
NX currently supports the partially load and the fully load options, and does not support the
minimal loading of the study and its components. Use only the Partial load - Lightweight display
option to load the study.

© 2020 Siemens
Creating occurrence poses
When you create occurrence poses for the components, NX shows no modifications for the parent
component in the tree structure, in the Planning Navigator. Also, if the state of the component for
which you create occurrence poses is Released, you may observe an issue, that you can still create and
save the occurrence pose.
Saving a study
You must use the Save All option, to properly save the modified data to Teamcenter.
Assembly Line Planner
Product Notes
Template files
To work in Assembly Line Planner managed mode, you must import the standard part files delivered
with Assembly Line Planner into the Teamcenter database, so you can access these files in the New Item
dialog box. If you do not perform this step, the New Item dialog box displays only blank templates.
A setup script for installing Assembly Line Planner templates in Teamcenter is included with NX:
%UGII_BASE_DIR%\MANUFACTURING_PLANNING\templates\tcin_linedesigner_template_setup.bat
For information about how to use the script, see Installing File New templates in the NX help at the
following location:
Home→
Teamcenter Integration for NX→
System Setup/Administration→
Server Setup/Administration→
Installing/creating/modifying templates→
Installing File New templates
Platform support
Assembly Line Planner is currently supported only on the Windows platform.
Manufacturing Resource Library version compatibility
Assembly Line Planner supports the use of factory resources with compatible versions of Teamcenter
and Manufacturing Resource Library (MRL). You should find the latest version of MRL in the latest
Teamcenter release.

© 2020 Siemens
Documentation Notes
Note:
You should always upgrade the Manufacturing Resource Library components from the previous
release to the new release.
Documentation Notes
Note the following about the Assembly Line Planner documentation:
• In the release notes, you can find Assembly Line Planner in the Manufacturing Planning section.
Caveats
Loading a line with assembly load options
In Assembly Line Planner, while loading a line using assembly load options, you may observe the
different behavior for the minimal load and the partial load option.
Note:
NX currently supports the partially load and the fully load options, and does not support the
minimal loading of a line and its components. Use only the Partial load - Lightweight display
option to load a line.
Copying of a workarea object
Copying and Pasting options for a workarea is currently not available in Assembly Line Planner.
Make Unique of a workarea object
The Make Unique option for a workarea is currently not available in Assembly Line Planner.
Structure of a workarea object
Assembly Line Planner uses the recommended BiW data model. The workarea objects (MEWorkarea)
must not have a process twin structure.
Using Manufacturing Collaboration Context
Assembly Line Planner uses the typical Manufacturing Collaboration Context. This includes a product
(PBOM), a process (Plant BOP), and a resource structure (Plant BOE).

© 2020 Siemens
Supporting product configurators
Assembly Line Planner may not support some advanced product configurator use cases, when you
create the variant conditions on operations. This does not impact loading of the data in NX.
Knowledge Fusion and DesignLogic functions
Product Notes
Impact of angle base units on custom Knowledge Fusion and DesignLogic functions:
Customers who use NX interactively should see no impact from this change. Customers automating NX
programmatically should read this section carefully.
The internal base units for angles are now radians instead of degrees. Internally, calculations involving
angles will be converted to radians while the calculation is performed. This change enables certain new
calculations involving angular units.This affects not just the angle measurements but every
measurement that includes angular dimensions as shown in the following table.
Measure Base units before radian-based Base units in radian-based

Angle degrees radians
Angular Velocity degrees/sec radians/sec
Angular Acceleration degrees/sec^2 radians/sec^2
Angular Jerk degrees/sec^3 radians/sec^3
Per Angle 1/degree 1/rad
Angular Momentum per Angle mN-mm-sec/degree mN-mm-sec/rad
Moment per Angle mN-mm/degree mN-mm/rad
Voltage per Angular Velocity microV-sec/degrees microV-sec/radians
Length per Angle mm/deg mm/rad
Per Angle Squared 1/degree^2 1/rad^2
Mass Moment of Inertia Per Angle kg-mm^2/deg kg-mm^2/rad
Custom DesignLogic and Knowledge Fusion functions with parameters involving angular
dimensionalities may need to be scrutinized for accuracy.
• Functions that have been authored using pure KF language may not be impacted. Any special coding
done by you to handle units/unit conversions in your functions should work the same as they did in
NX 1872.
• Functions that make calls to UG Open/Ufunc accepting and returning dimensionalities with angles
may be impacted. Even those that don’t may be impacted.

© 2020 Siemens
Product Notes
For example, the functions floor() and ceiling() had to be changed because they sometimes may receive
a value that has an angle dimension, in which case UF_KF_ask_number() would return a radian value.
You might have special custom coding to apply unit conversion from degrees to radians in such cases
which may no longer be necessary. We also recommend looking into the APIs
UF_KF_ask_number_with_measure & UF_KF_make_number_with_measure that provide numbers in
degrees while preserving the dimensionality. Using these APIs instead of UF_KF_ask_number &
UF_KF_make_number may help achieving the original intent of the KF/DL functions. For example:
//========================================
DllExport extern void supplimentary_Angle(UF_KF_value_p_t *data, int
num, UF_KF_value_p_t *rv)
//Initialize UF session
UF_initialize();
double angle=0;
char *dim = "";
// Extract a degree-based value and its dimensionality from an input

argument
UF_KF_ask_number_with_measure(data[0], &angle, &dim);
//Calculate supplementary
double comp = 180 - angle;
// Prepare a return value with a given dimensionality.

UF_KF_make_number_with_measure(comp, dim, rv);
UF_terminate();

© 2020 Siemens
Validation
Check-Mate and Requirements Validation
Caveats
Validation rules
Validation rules do not recognize unset part attributes.
Using NX Issue Management
To use NX Issue Management, Teamcenter Issue Manager must be deployed from the server by the
Teamcenter Environment Manager. If NX cannot connect to Teamcenter Issue Manager, you will see a
message. For more information, see the Teamcenter Environment Manager help.
Using Teamcenter for NX Issue Management
When you use NX Issue Management, you can specify Teamcenter as the issue site only when
Teamcenter Issue Manager is deployed by Teamcenter Environment Manager on the server side.
Tooling Design
Mold Wizard
Mold Wizard and Progressive Die Wizard Caveats
Check Wall Thickness
The new Range Areas tab appears in the Check Wall Thickness dialog box for the Mold Wizard and
Progressive Die Wizard applications:
Connecting Areas
Range selection Displayed when Thickness Range in the Face Selection Filter group on the
filter is off Inspect tab is not selected.
Number of Displays the total number of connecting areas from the Connecting Areas list
connecting areas table.
Thickness Range Displays the Thickness Range values specified in the Face Selection Filter group
on the Inspect tab.
Connecting Areas Displays thickness results grouped into areas and ranges.
list table
Click on a cell in the Area Name or Range columns and the area containing the
defined range is outlined and zoomed in on in the graphics window.

© 2020 Siemens
Note:
To populate the list, you must enter a value for the Low and High thickness
ranges in the Face Selection Filter group on the Inspect tab.
Progressive Die Wizard
Check Wall Thickness
The new Range Areas tab appears in the Check Wall Thickness dialog box for the Mold Wizard and
Progressive Die Wizard applications:
Connecting Areas
Range selection Displayed when Thickness Range in the Face Selection Filter group on the
filter is off Inspect tab is not selected.
Number of Displays the total number of connecting areas from the Connecting Areas list
connecting areas table.
Thickness Range Displays the Thickness Range values specified in the Face Selection Filter group
on the Inspect tab.
Connecting Areas Displays thickness results grouped into areas and ranges.
list table
Click on a cell in the Area Name or Range columns and the area containing the
defined range is outlined and zoomed in on in the graphics window.
Note:
To populate the list, you must enter a value for the Low and High thickness
ranges in the Face Selection Filter group on the Inspect tab.
Press Die Checker
Product Notes
Platform support
Press Die Checker is currently supported only on the Windows platform.

© 2020 Siemens
Caveats
Minimal load support
The minimal load is not completely supported in Press Die Checker.
Data translation
Product Notes
Updates for the default tessUG.config JT configuration file
• To ensure that you are using an up-to-date configuration file, we highly recommend using the
tessUG.config configuration file included with NX and customizing it per your current settings.
• Make sure you delete all the references to the activateCsysPMI option in the JT configuration file.
If activateCsysPMI = true is set anywhere in the configuration file, the translator stops the
translation process.
• The doSectionViews configuration option which is used to process non-lightweight PMI section
views (also known as heavyweight section views) is removed from the default tessUG.config file
shipped with NX11. This option is now renamed as LegacyHeavyweightSectionViews. If your
existing NX part or assembly contains section views created using PMI tab→Section View command
in Pre-NX11 versions and you want to translate these section views to a JT file, you need to add
LegacyHeavyweightSectionViews option in your tessUG.config configuration file and set it
to true.
CATIA V5 translator product notes
You can now import the following type of files to NX:
• CATIA V5-6R2019 files (on Windows 64-bit)
• CATIA V5-6R2018 SP3 files (on Linux 64-bit)
You can now set Include Reference Geometry as a translator option.
ACIS translator product notes
You can now read and write ACIS version up to R29.
DXF/DWG translator product notes
You can now read and write AutoCAD DXF/DWG version up to 2020.

© 2020 Siemens
Product Notes
NX to JT translator product notes
• When you set JtFileFormat = “10” in the tessUG.config file, the NX JT translator now exports to
version JT 10.5 files. The JT 10.5 version additionally contains smart topology table (STT) and per face
group attributes (PFGA) information.
• The STT information in the JT files allows the JT reader, such as NX, to perform certain precise
analysis operations without having to load the precise geometry. The JT load performance improves
in such JT readers due to their ability to do more with JT tessellation geometry. For optimal use of
STT data in a JT file, use Teamcenter Visualization version 12.3 or later.
As STT data is additional information that is written to a JT file, the size of JT file can increase.
• The PFGA information in the JT files optimizes the JT file structure for multicolored parts. The size
of the JT file reduces with PFGA, typically with parts that contain bodies with multicolored faces.
To correctly visualize JT 10.5 files with PFGA, use Teamcenter Visualization version 12.3 or later.
Earlier versions of Teamcenter Visualization do not correctly display the colors applied on different
faces of bodies in a JT 10.5 file with PFGA.
For more information about exporting to previous JT file versions, such as 10.3, 10.2, 9.5, and so on,
see the JtFileFormat configuration option in JT configuration file—Setup section in the NX help.
NX ProE translator product notess
You can now import Creo 6.0 files to NX.

© 2020 Siemens
Caveats
Support for imported PMIs
The following NX translators do not support the export of Imported PMI objects:
• 2D Exchange
• DXF/DWG
• STEP AP203 and STEP AP214
Exporting convergent bodies
• The NX ACIS and CATIA V4 translators do not allow selection of convergent bodies.
• The NX STEP AP203, STEP AP214, and IGES translators do not support exporting of the convergent
bodies. These translators add a message “Convergent/Facet bodies are not processed” to the log file.
Support for Teamcenter settings
The following translators do not support other Teamcenter settings other than variant rule, revision
rules, and effectivity:
• STEP AP203, AP214, and AP242
• IGES
• DXF/DWG
• 2D Exchange
Limited support for new line styles
The following NX translators do not support the new OOTB and shipbuilding line styles, and write them
as Solid line style:
• CATIA V5
• IGES
• NX to JT
• STEP AP203, AP214, and AP242

© 2020 Siemens
Caveats
Internationalization caveat
File import or export by the following translators may not work if you set the NX temporary directory
UGII_TMP_DIR to a folder containing non-locale characters.
• DXF/DWG
• IGES
• STEP
• 2D Exchange (export only)
NX to JT translator caveats
NX to JT translator caveat for the Windows operating system

If you are translating pre-NX11 parts with material, texture, and light applied on it and you want to
get the texture or light information into the JT file, We recommend you to invoke NX in Author2
(non-IRAY+) rendering mode and then translate the parts to a JT file. This recommendation is
applicable for JT creation from interactive NX session as well as command line application ugtopv.
Contact GTAC to get more information on how to invoke NX in Author2 (non-IRAY+) rendering
mode.
Note:
If you invoke NX in Author2 (non-IRAY+) rendering mode then these options will be available
in the JT Configuration and the Export JT dialog boxes.
NX to JT - IRAY texture and material caveats

In some situations, you may find differences between the quality of the texture displayed in NX and
that displayed in JT, when you view it in the Teamcenter Visualization.
For NX parts that contains symbolic thread features:
• If you apply different colors to multiple curves of a symbolic thread feature in an NX part, they
will appear in the same color in the JT file.
• If you associate a PMI object to a single curve of a symbolic thread feature in an NX part, it gets
associated to all the curves in the JT file. If you select any thread feature PMI in the JT file in
Teamcenter Visualization, all the curves are highlighted.
Exporting line style and line width applied on symbolic thread curves caveat
Different line styles and line widths applied on the curves of symbolic thread features are not
exported to JT files. When viewed in Teamcenter Visualization, such curves are displayed with the
Dashed line style and the Thin line width.

© 2020 Siemens
DXF/DWG translator caveats
DXF/DWG — Dimension export caveats

These caveats are applicable when you export a file using the 3D option in the AutoCAD DXF/DWG
Export Wizard dialog box.
• Dimensions associated with external references are exported as non-associative dimensions to

the DXF/DWG file.
• NX Radius dimensions associated with ellipse or spline object are translated as AutoCAD block
reference.
• The dimension associated between NX sheet object and View port object may be translated as
overridden text of AutoCAD dimension.
• Narrow dimensions are exported as non-associative dimensions to the DXF/DWG file.
• Chamfer and Thickness dimensions are exported as block reference to the DXF/DWG file.
• Angular dimensions created with vector option are exported as block reference to the DXF/DWG
file.
• Dimension with fits tolerance having fit tolerance style other than Fit Symbol is exported as block
reference in AutoCAD.
• Dimension text location may not match with NX for the dimensions created with oriented text.
• Dimension line breaks and foreshortening symbols are not supported when dimension is
exported as group or block.
• If a dimension text is on the extended dimension line, the exported dimension has to be updated
to view any foreshortening symbols on it.
DXF/DWG — MText import caveats
You cannot import:
• MText paragraph tabs to NX.
• Euro symbol (created using %%128 in MText) to NX.

DXF/DWG — Architecture data import caveats
• You can not import:
• View dependent data
• Texture data

© 2020 Siemens
Caveats
• Corner windows
• Wall cleanups
• Body modifiers on staircase
• Associativity defined between the architecture objects is not maintained in NX. For example, door
on wall will not move along if wall is moved.
DXF/DWG — Solids import caveats
You cannot import:
• Material, color, and transparency applied on solids in the DXF/DWG file.
• Solids data at location outside the NX supported bounding box.

DXF/DWG translator- Image translation Caveats
• When you import DXF/DWG model data to NX drawing view, the translator does not support
image translation.
• When you import DXF/DWG file that contains image rotated by angle which is not in a multiple of
90, the image is imported with zero degree rotation.
Note:
In NX, the images are rotated in steps of 90 degrees only.
• When you import DXF/DWG file with images having other than .jpeg, .tiff, and .png formats to
NX, the translator does not support importing of such images.
• Images are not imported if exported as CGM.
• Image translation is not supported if the DXF/DWG file is imported to workpart.

DXF/DWG translator- 3D Workflow caveats
When you export View Breaks using 3D workflow, the translator does not support an export of the
following:
• NX Object clipping and view break symbols.
• Geometry clipped inside a view boundary.
• A section line arrow in Break view.
Dimension export using 3D workflow

© 2020 Siemens
• When a dimension is exported as a block reference, the foreshortening symbol is not supported.
• 3D workflow does not support the inclusion of before/after appended text in the export of the
inspection dimension. It always includes all the appended text in the frame.
• The translator does not support a tolerance separator in the output DXF/DWG file.
Text export using 3D workflow
• When you export text as lines using 3D workflow, the translator ignores the text symbol aspect
ratio.
DXF/DWG translator- Associative dims to polyline and block caveats
You cannot import dimension as real associative in following scenarios:
• Blocks are imported as custom symbols or as a part and if dimensions are associated with block
reference in the DXF/DWG file.
• Dimensions are associated to 2D and 3D polyline.
• Dimensions that have following Object snap points:
• Tangent
• Perpendicular
• Nearest
• Apparent Intersection
• Parallel
• Intersection
• Dimensions are associated to arc segment of the polyline.

DXF/DWG translator- Support for drafting objects caveats
You can not export:
• Drawings created in the Layout application using the 2D option.
• Custom symbols used in a PMI table.
• Section views.
DXF/DWG Support for Hole table

© 2020 Siemens
Caveats
If the multiple sections of the hole table are created on different drawing sheets, the continuation
text will be lost.
DXF/DWG support for importing model and layout data
• You cannot import DXF/DWG model data and layout data to a drawing view while importing to a
work part.
• When you import DXF/DWG files with model data to drawings with Import Curves as Sketch
Curves , it results in increased translation time.
2D Exchange caveats
• Object attributes with title longer than 50 characters or string value longer than 132 characters are
not exported to 2D parts.
2D Exchange – Dimension export caveats

These caveats are applicable for both, when you export a file using the NX Part file option in the 2D
Exchange Options dialog box or when you export a file using the 2D option in the AutoCAD
DXF/DWG Export Wizard dialog box.
Following dimensions are exported with the Override Dimension Text:
• Feature Parameter Dimensions
• True Length Dimensions
• Dimensions in scaled view and output set to Modeling (applies only when you export a file using
the NX Part file option in the 2D Exchange Options dialog box)
• Dimensions associated to:
• Drafting Intersection point
• Offset center point
• Section line (in scaled view)
• The dimensions where associated object type changes in the flattened part. For example, circle
projected as line.
Following Data will be exported as grouped geometry in the 2D part file and as a block in the DXF or
DWG file.
• Linear and Radial callouts
• Retained dimensions

© 2020 Siemens
• Component level dimensions and PMI dimensions
• Inherited ordinate PMI dimensions
• Dual dimension in scaled views and output set to Modeling.
• Dimension with hole and shaft tolerance in scaled views and output set to Modeling.
• Dimensions associated with:
• Blanked objects
• 3D and Symmetric centerlines
• Faces
• Two object intersection (applies to ordinate dimension only)
• Target Points
• Dimension created in plane other than view plane.
• PMI Partial Bolt Circle centerline.

2D Exchange translator- Image translation caveats
• 2D Exchange Translator does not translate image, if image is not projected on 2D. This happens
when image is in XY plane and trimetric view is exported.
• 2D Exchange Translator supports translation of images only if input is being exported to Part File
and not to IGES).
2D Exchange translator- Dimension export caveats
• When Dimension and a Leader are associated with the symmetrical centerline, the translator
exports them as a grouped geometry.
• When a radial dimension is associated with a break view geometry, the translator exports it as a
group geometry.
• When a perpendicular and angular dimension is associated with a break view section line,
translator exports them as a group geometry.
2D Exchange translator - Foreshortening Symbol export caveats
A translator does not support export of foreshortening symbol when dimension is exported as a
group in a 2D part.
2D Exchange translator – Leader caveats

© 2020 Siemens
Caveats
A leader with an extension line is converted as a grouped geometry when it is associated with a
spline in a 2D part.
2D Exchange translator – Weld symbol caveats
When you export a weld symbol containing arcs, the translator exports it as a grouped geometry.
2D Exchange translator – Support for drafting objects caveats
You can not export:
• Drawings created in the Layout application
• Custom symbols used in a PMI table.
• Section view while exporting Model views.

2D Exchange Support for Hole table
If the multiple sections of the hole table are created on different drawing sheets, the continuation
text will be lost.
DXF/DWG and 2D Exchange - PSM body support project caveats
• If you export convergent bodies as polyline mesh, it exports only edges.
• Colors are not honored when you import 3D faces as convergent bodies or JT facets.
• Colors applied to face of convergent body is not honored on export.
• You cannot export model views with convergent bodies with 2D Exchange (or using 2D option on
DXF/DWG export dialog box).
STEP translator caveats
• When you import kinematics information from AP242 XML files, the translator names the joints as
Rigid Group. To use such joints in simulation, you must rename them per your requirements.
• When you export or save NX data to an STPX file, the STEP translator does not export nested external
references.
• When you export NX data containing PMI lightweight section views to a STEP AP242 file, the
following are not supported:
• Selective object sectioning
• Section plane display properties
• Section view crosshatches

© 2020 Siemens
• When you export NX data to a STEP AP203, AP214, or AP242 file, the translator does not export NX
layer categories.
• When you export data to a STEP AP242 file, the translator does not export:
• Layer mapping and layer mask.
• Color overrides for faces, wireframes, points, and coordinate systems.
• Components and body colors, when you export components as external references.
• Color overrides at the assembly level, when you export selected objects.
• Color overrides at the assembly level, when you export NX files to XML (*.stpx, *.stpxz).
• The STEP AP203 and AP214 translators do not export and import assembly color overrides.
• Due to STEP schema limitations, chamfer dimensions from NX are exported as presentation data.
• When you import tessellated PMI from STEP AP242 files, vertices that create the PMI display are not
optimized and this can result in an increase in the NX file size.
CATIA V5 translator caveats
• The translator exports NX files to CATIAV5 R14 files.
• If an attempt to export a newly created part in Teamcenter Integration for NX mode fails, close and
open that part file and re-run the translation.
• You cannot import CATIA V5 R7 and earlier version of files.
• You cannot translate standard and user defined attributes.
• Color is supported on a per face basis.
• You can only import CATIA V5 “Lines and Curves” into NX using default Linetype and Thickness
values.
• You cannot export NX parts with file name containing international characters.
• The CATIAV5 translator does not keep a log of failed export of password protected data during
translation.
• Before re-importing a CATProduct with different content (potentially due to option choices), it is best
to manually delete previous output files in case the IDs in the node or component part filenames
shift.

© 2020 Siemens
Product Notes
• During import, the translator will look for component files at and below any directories specified
through Assembly Search Directories.
• The translator looks for the default settings file in the following sequence:
1. Settings file specified using the d= option if you launch the translator from command line
prompt.
2. Settings file specified using the NX_CATIAV5_DEF environment variable.
3. Settings file specified using customer defaults.
4. Searches for the settings file in the directory specified by the environment variable
UGII_CATIAV5_DIR. If this is not defined on your system, you can set it to %UGII_BASE_DIR%
\catiav5 on Windows or $UGII_BASE_DIR/catiav5 on Linux.
ACIS translator caveats
When you import ACIS files, few solid bodies from ACIS file may get imported as collection of sheet
bodies, and sheet bodies with multiple faces may get split into multiple sheet bodies. This will also result
in increased translation time.
Exporting unsaved imported IFC file
In NX 1926, your NX session may crash if you import an IFC file and export it without saving. You must
save your NX work prior to exporting the imported file using Save As or Export IFC command.
Caveat for all translators
The password protected parts or assembly components are not exported to other file formats.
Mechatronics Concept Designer
Product Notes
PLCOpen XML export for STEP 7
Mechatronics Concept Designer can export the sequence of operation in the standardized XML format
PLCOpen XML. PLCOpen XML can be imported into STEP 7 5.5 SP 2 Hotfix 4 and above. If you need to
update your current STEP 7 installation you can find information about the latest service packs and
hotfixes at the following:
English: https://support.industry.siemens.com/cs/products?
dtp=Download&mfn=ps&pnid=14342&lc=en-WW

© 2020 Siemens
Import PLMXML enhancement
The Import PLMXML command is enhanced to better import legacy data from Process Simulate to
ensure the creation of rigid bodies and joints.
Automation Designer
Product Notes
To work with Automation Designer, you must set it up as a four-tier, client-server application with
Teamcenter as the server.
Software requirements for Automation Designer in NX 1953
Support
ed
Product version Notes
Teamcen • 12.2 We recommend that you use Teamcenter 13.1 or later to use the complete
ter functionality of Automation Designer.
• 12.3
Note:
• 12.4 If you are upgrading Teamcenter, see Teamcenter Upgrade in the
Teamcenter documentation.
• 13.1
EPLAN • 2.7 You must have an EPLAN runtime license EADN:Application 0193.
Automation Designer supports only .zw9 files.
• 2.8
• 2.9
TIA Portal • 15.0.0 You must have a valid TIA Portal license.
• 15.1.0 • STEP7 Professional Combo V15, V15.1, V16
• 16.0.0 • (Optional) STEP7 Safety Advanced Combo V15, V15.1, V16
• (Optional) Drive Support: SINAMICS Startdrive V15, V15.1, V16
Note:
Automation Designer does not exchange data with TIA Portal V14.SP1. But
you can export program blocks of TIA Portal V14.SP1 to a higher TIA Portal
version.

© 2020 Siemens
Product Notes
Support
ed
Product version Notes
eCl@ss 8 or later You must have a valid eCl@ss license.
ADVANC
The terms of use of the eCl@ss standard state: This content contains eCl@ss. The
ED
use of the eCl@ss standard requires a license. Please register and order in the
Download Portal.
Automati 7.0 You must add Automation Designer content to Teamcenter. If Automation
on Designer content already exists, you must upgrade it.
Designer
To upgrade Automation Designer content to support NX 1926, you must:
content
1. Upgrade the existing library in Teamcenter before you run NX 1953.
2. Run the Automation Designer application in NX 1953, and then upgrade your
other existing data.
Automation Designer supports the versions of Windows that NX supports.
For more information on the supported versions, see certifications page.

© 2020 Siemens
Caveats
Installation
• During the export of PLMXML you can get the following errors:
#Severity #Code #Detailed message

ERROR 10012 User is not a system
administrator
ERROR 40006 Unable to create Site IMC—
1838610269
Even with this error, the import of the folder structure succeeds and the folder data is available in the
importing environment.
To resolve the errors, you can add the following closure rule clauses in the transfer mode
(incremental_import):
1. CLASS.*: CLASS.Site: ATTRIBUTE.*: SKIP
2. CLASS.Document: CLASS.Site: CONTENT.*: SKIP
Add the clauses before any attribute with PROCESS action. (AD-36826)
Upgrade
• You cannot upgrade projects containing tags with expressions to NX1953. (AD-37985)
Save
• Executing the Save As command on read-only library objects such as Types, Symbols, Formsheets or
others, causes an error message stating The dataset is read only. Confirm the error message.
Automation Designer saves correctly the new library objects that can be used without limitation
afterwards. (AD-36213)
• If you create a new revision of a product, apply a Save As before modifying the product.
If you modify the product before saving and afterwards save it as a new revision or new item, the
original product is changed, too. This is NX default behavior. (AD-34086)
• If you clear the check box of the customer default Accept Automatic Names for New Parts (the
default is the activated check box), the error Cannot save part with a temporary name occurs
during saving the Automation Designer workset.
Do not change the default setting. (AD-37475)

© 2020 Siemens
Caveats
Localization
• An error occurs when you create a new workset for an existing project while a content language is
active. A content language is active when you set the environment variable
UGII_UGMGR_LANG_TCSERVER_APPLICATION=ADDisplayTcServerInSpecificLocale.
As a workaround create new worksets only in sessions where no content language is active.
(AD-37725)
• Reports that use the report templates delivered with Automation Designer have table headers that do
not localize.
As a workaround you can create new report templates using property names or property title
placeholders that correctly localize the report table headers. (AD-37692)
• Some property titles in form sheets and query result table headers do not switch to content language,
but are dependent from NX user interface language.
As a workaround, if you want to create localized output showing translated content for such titles as
well, use the content language as the NX user interface language, too. (AD-37647, AD-37853)
• Automation Designer content does not contain translations of List of Values, LoVs. (AD-36197)
• Queries that you create with a different NX user interface language than the Teamcenter master
languge (English always for Automation Designer), and that filter for specific property values, do not
return a result.
As a workaround create such queries using English as NX user interface language. (AD-37577)
• The following properties are not localizeable (AD-8462):
• Device function – User property 5
• Device function – Contact – Trip point hysteresis
• Device Function – Input/output – Tag Description
Collaboration
• When multiple users create subsets for the same mechanical data in the same project, some
mechanical objects can be greyed out in the Collaboration Navigator and they are invisible in the 3D
model. Only one user should create a subset and publish the collaboration context. Then other users
can use the Load external objects commmand to avoid creating subsets by themselves. (AD-8881)
Data exchange
• The Teamcenter user name must not exceed the length of 14 characters. Otherwise the transfer of
ownership is not successful. (AD-27236)

© 2020 Siemens
• When transferring a template being used in a project including which link to mechanical objects
containing AssemblyArrangements, the template import can fail with a null value for xml attribute
error.
As a workaround you can skip the closures rules in the transfer mode that include the assembly
arrangement. (AD-37323)
Snapshot
• Restoring a snapshot can fail with error Object is reference by relation when using Teamcenter
versions prior to TC13.1, TC12.4.0.3, and TC13.0.0.3. Snapshot restore is not available if Automation
Designer is based on Teamcenter 12.2 or TC12.3 series. (AD-35936)
• The functionality to inspect a snapshot is limited and experimental. Inspection functionality is only
available, when the AD_ENABLE_INSPECT_SNAPSHOT=1 environment variable is set.
• A snapshot can only be inspected while the same project is not open, and no other snapshot of this
project is inspected at the same time.
If Cabinet Design components are used in the project, additional NX inter-part relations resolve to a
newer part than the one which is inspected by the snapshot. This results in an error Invalid OM
object in Automation Designer.
Automation
• The sdx-file import of CreateMyConfig 6.0 release version has some known issues that blocks the
transfer of engineering result from ADNX to CMC:
• The products S120M, CU310-2PN and CU310-2DP after export from Automation Designer are not
imported successfully in CreateMyConfig. (AD-8763, AD-8779)
• The encoder number value as defined inAutomation Designer is not respected by CMC. You use the
encoder number for establishing the mechanical connection between Motor and Encoder.
(AD-8764)
Electrical Design
• If you delete any of the interruption points on a busbar connection, and save then the project, an
error occurs if you create a new interruption point in place of the deleted one and link it to another
interruption point, and the busbar connection is created.
As a workaround, delete the existing busbar connection after deleting the interruption point, before
you save the project. (AD-37830 )
EPLAN
• If you use an UNC path as the target location for the project generation, an error occurs.
As a workaround, map a drive letter to the network location and use this as the target location.
(AD-37683)

© 2020 Siemens
NX Open differences between releases
Programming Tools
NX Open
NX Open differences between releases
The NX Open differences between releases and deprecated items replacements are now published in
Support Center.
In the NXOpen APIs What's Changed Reports webpage, you can select the Changes That May
Require Code Changes tab to view the changes that have occurred for the release and any that might
require changes to your existing code. The What's New tab provides new items for the release.
You can compare your release to another one to see the amount of change that has occurred between
the two releases. In the Comparing NX <your release> and: listing, select the release you want for
comparison, and click Compare. You can get comparisons for up to two years of releases.

© 2020 Siemens
Release upgrades
A primary goal of NX Open is to maintain your automation investments. This is done by adopting
policies which minimize the amount of required code changes by you to migrate your applications to
new releases of NX. The following contains a description of these policies and how they impact your
ability to support the users of your applications, and the steps you should take to successfully move your
application to new releases of NX.
NX Open API change policy
NX maintains the following three primary policies to protect your investments:
• API stability
Stability ensures that the API that has been released will continue to work. This means that the API is
still present in future releases and the behavior of the API doesn't change. API changes should be
designed to minimize any changes to your source code. For example, if the capabilities of a method
are expanded which requires new parameters, then NX may maintain and optionally deprecate the
original method and add a new method that includes the new capabilities. By doing this, existing
applications do not require code changes unless they want to take advantage of the new capabilities.
• Binary compatibility
Compatibility means that applications that are built against a specified release continue to work with
subsequent releases. This requires not only that API stability is maintained but also is binary
compatible. For example, re-ordering the values of enum members so that API stability is maintained.
In this case, the values have changed so existing automation programs will be using the wrong
values. In other cases, deleting a method or modifying the inheritance hierarchy of a class will likely
cause run-time errors for existing programs.
The other aspect of binary compatibility is the compiler. When the compiler NX uses changes, this
may break binary compatibility of automation programs. While some language bindings are more
tolerant of being backwards compatible, such as Java, others are not as tolerant, such as C++.
NX libraries will be forward compatible for all releases in a release family. If you compile and link your
application with the libraries shipped with a functional release of NX, such as NX 1847, then your
application should continue to run with all future monthly releases in that release family (NX 1847).
This compatibility means you do not need to recompile, relink, and reship your applications to
customers running various monthly releases of NX. Note that NX is not backwards compatible, which
means you can't compile and link an application in NX 1847 and expect it to work in NX 12.
NX will only change the compiler used (breaking binary compatibility) in a functional release and will
not change it more than once a year. During the functional release, the compiler may change and APIs
may be retired per the deprecation policy for deletion.
• Deprecation policy
If an API change requires you to make source code changes, you are given notice one year in advance,
if possible. For example, if a method is going to be replaced by a new method, the original method is
marked as deprecated in NX 1847, which is the release family. The original method is maintained
through the current release family and through the next release family also, after which the API may
be retired and removed.
The what's changed reports in Support Center and, if possible, compile time warnings are used to
warn you of changes made in the current release and changes coming in the next release. The

© 2020 Siemens
Release upgrades
deprecated items topic in Support Center provides a list of the deprecated methods and their
replacement methods.
For more information about API information in Support Center, see NX Open Differences between
releases.
Note:
NX development makes every effort to follow the above policies. However, there may be instances
when the policies must be violated due to the type of changes required. When this type of change
is made, it is published on the Changes That May Require Code Changes tab in Support Center.
This includes information on the change that happened and suggests changes that could be made
to the code.
NX maintains and publishes stability metrics that show that for at least the last 10 years the
stability of the NX Open APIs is above 96% for any given release, while the average is above 99%.
Exploring changes to the NX Open API between releases
NX Open changes are published in Support Center. In the NXOpen APIs section for your release, you
can view API changes in the NXOpen APIs What's Changed Reports.
By default, this webpage contains the reports of the current release and the last functional release. In
addition, you can select a release to compare with your release to get a comparison between the two
releases. You can get comparisons for up to two years of releases.
Each page presented provides a point-to-point comparison of the APIs. The What's New tab on the page
presents the new API items added between the two selected releases. The Changes That May Require
Code Changes tab provides information that shows the changes that violate API stability and (or) binary
compatibility, in accordance with the rules specified in the above policies.
For example, removing API items violates our API stability and binary compatibility policy unless the
compiler changes. For each entry, we provide remediation suggestions, if needed, and possibly the
reason for the change. An example of a change for which the only remedy is to recompile, is if a class
has a new base class inserted into it's hierarchy. In this case, you don't need to change your code, but
you do have to recompile your automation code that uses the API. This is contrasted by changes to a
method signature to add an additional parameter. In this case, there will be a description of what the
new parameter's purpose is and how to use it.
Also, the Changes That May Require Code Changes tab lists all of the deprecated APIs, their
replacement APIs, and the earliest that each API could be retired. APIs that are retired are listed on the
tab, along with when the API was removed and their replacement.
Open C API changes are listed in the NX release notes, in the New Open C routines, Obsoleted Open C
routines, and Deleted Open C routines topics.
Function declarations that are newly retired (obsolete/deprecated) are moved to the uf_retiring.h file,
which contains a complete list of Open C functions that could be deleted in the next NX release.

© 2020 Siemens
Release upgrade process for a functional release
For each functional release of NX, you should perform the following steps to migrate your application to
the release:
1. Review the Changes That May Require Code Changes tab for the release you are going from and
upgrading to. This helps you to understand what changes are being made in the release and what
changes are planned for the next release.
2. For any methods or properties that have been deleted and for those which you have not already
replaced in your code, implement the replacement code.
3. Recompile your entire source base using the current compile time files and settings for the given
release.
4. For any methods or properties that produce deprecation warnings, decide if you are going to
replace this code now or in the next release. Implement the replacement code for any deprecated
methods you want to replace now and recompile.
5. Link your application with the appropriate NX Open libraries.
6. Perform a full suite of application testing in a stable NX environment.
7. Distribute your applications to your user base.
Release upgrade process for a monthly release
For each monthly release of NX, you should perform the following steps to migrate your application to
the release:
1. Review any changes for the monthly release in Support Center.
2. Any API changes that may require rework or a recompile of your code will only be made if
absolutely necessary. In this case, you will have to rework or recompile the affected applications,
then test and redistribute. These changes are provided in Support Center.

© 2020 Siemens
Product Notes
Product Notes
Certified compilers and environments to use for NX Open programs
The following table specifies the compiler (or installation for Python) to use for the applicable platform.
These certified compilers are the ones used in testing for a particular release. These are the only ones
certified for use with NX Open:
Windows Linux
C/C++ Visual Studio 2019 Professional gcc 7.3.1

16.0.5
Build 19.20.27508.1
.NET .NET 4.7.2 Framework N/A
Java (64–bit) JDK 1.8.0_45 JDK 1.8.0_45
Python (64–bit) Python 3.7.4 Python 3.7.4
Use of a non-certified compiler
• C++
For Windows, any version of a Visual Studio compiler should work within the release family as long as
the version is equal to or higher than the certified version.
For Linux and gcc versions, any version of gcc should work as long as the version is equal to or higher
than the certified version and in the same release family.
• .Net
The .Net framework provided by Microsoft attempts to maximize backward compatibility. The version
used should be equal to or greater than the certified version. Additional information is provided by
Microsoft at Version Compatibility in the .NET Framework.
• Java
Java has historically allowed programs compiled with earlier compiler versions to work with later JRE
versions. This means that users can choose to compile at the certified compiler level and run with a
later JRE version, or choose to compile at a compiler level greater than or equal to the certified
compiler.
• Python
The Python version that NX delivers is built at the certified version for the release. In addition, Python
is binary compatible in a major release family, so for example, if we build and certify against X.Y.4,
our NX Open Python binaries will be binary compatible for all releases in the X.Y series (X.Y.5, X.Y.6,
and so on). But they will not be binary compatible with a different major release family, for example,
the X.Z series (X.Z.3, X.Z.4, and so on).

© 2020 Siemens
Using a non-certified compiler or environment is not without risks, which is assumed by the user. If an
issue arises using a non-certified compiler or environment, Siemens Digital Industries Software can
investigate with the following caveats:
• We need to be able to reproduce the issue easily so we can investigate the problem.
• If the compiler or environment regresses, it is expected that the user will investigate the issue in their
environment to rule out improper usage on their part. For example, it is expected that users will rule
out scenarios where the latest version of the compiler or environment fixes a bug that now catches
something invalid that wasn't caught before in a previous version.
• There exists the possibility that the solution to the issue encountered cannot be realized in the release
reported, but will be deferred to a later release.
Using the SCL compiler on Red Hat Enterprise Linux
To use the SCL compiler gcc 7.3.1 on Red Hat 7.6 or later, add a repository and install the compiler
package:
1. Register the system (required for Red Hat Linux). If you don't register, the following commands will
fail.
2. Install a package with a repository for your system. Run the following to enable the RHSCL
repository:
sudo yum-config-manager –enable rhel-server-rhscl-7-rpms
3. Run the following to install the collection:
sudo yum install devtoolset-7
4. The compiler is installed. However, the default compiler recognized is still the one found by paths
and environment variables. To use your compiler, either invoke a shell or set environment variables.
• Invoke a shell using the SCL compiler:
scl enable devtoolset-7 bash (or ksh)
• Set environment variables:
• INFOPATH /opt/rh/devtoolset-7/root/usr/share/info:$INFOPATH

© 2020 Siemens
Product Notes
• LD_LIBRARY_PATH /opt/rh/devtoolset-7/root/usr/lib64:/opt/rh/devtoolset-7
/root/usr/lib:/opt/rh/devtoolset-7
/root/usr/lib64/dyninst:/opt/rh/devtoolset-7/root/usr/lib/dyninst:/opt/rh/devtoolset-7
/root/usr/lib64:/opt/rh/devtoolset-7/root/usr/lib:$LD_LIBRARY_PATH
• MANPATH /opt/rh/devtoolset-7/root/usr/share/man:$MANPATH
• PATH /opt/rh/devtoolset-7/root/usr/bin:$PATH
Note:
When invoking a shell to use the compiler, it's possible you could have problems when
running Perl scripts. In that case, setting environment variables is the preferred method.
Running Java and .NET programs
To run programs created in NX Open that require Java or .NET, the following is required:
Windows Linux
.NET .NET 4.7.2 Framework N/A
Java (64–bit) JRE 1.8.0_45 or later JRE 1.8.0_45 or later
Note:
Some standard NX applications, such as translators, require installation of the JRE. For additional
information, see Considerations and caveats.
Internet browsers
If you do not see the latest documentation for the following programming tools, it may be a cache issue.
Try clearing your cache, or using a different browser.
• Open C Reference Guide
• NX Open C++ Reference Guide
• Open for Java
• NX Open Python
• Open for .NET

© 2020 Siemens
In the Open C Reference Guide, if links to the example .c files do not work in IE, the .c file may not have
an associated program to open it. Follow the instructions for your operating system to associate the .c
file to a program, such as Notepad.
Managed C++
Starting in NX 1872, support is dropped for managed extensions for C++ (referred to as managed C++).
In addition, C++/CLI extensions, which superseded managed C++, are also not supported.

© 2020 Siemens
Siemens Digital Industries Software
Headquarters Europe
Granite Park One Stephenson House
5800 Granite Parkway Sir William Siemens Square
Suite 600 Frimley, Camberley
Plano, TX 75024 Surrey, GU16 8QD
USA +44 (0) 1276 413200
+1 972 987 3000
Asia-Pacific
Americas Suites 4301-4302, 43/F
Granite Park One AIA Kowloon Tower, Landmark East
5800 Granite Parkway 100 How Ming Street
Suite 600 Kwun Tong, Kowloon
Plano, TX 75024 Hong Kong
USA +852 2230 3308
+1 314 264 8499
About Siemens Digital Industries Software

Siemens Digital Industries Software is a leading global provider of product life cycle management
(PLM) software and services with 7 million licensed seats and 71,000 customers worldwide.
Headquartered in Plano, Texas, Siemens Digital Industries Software works collaboratively with
companies to deliver open solutions that help them turn more ideas into successful products. For
more information on Siemens Digital Industries Software products and services, visit
www.siemens.com/plm.
This software and related documentation are proprietary and confidential to Siemens.
© 2020 Siemens. A list of relevant Siemens trademarks is available. Other trademarks belong to
their respective owners.

Release Notes

Uploaded by

Copyright:

Available Formats

Release Notes

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Release Notes

Uploaded by

Copyright:

Available Formats

NX 1953 Release

• Algorithmic Modeling, which allows you to develop math-based designs quickly.

• Staged Model to streamline the process of building in-process designs.

• CMM Inspection Programming

NX 1953 Release Notes PDF, NX 1953 Series 3

• Manufacturing Data Management

4 NX 1953 Release Notes PDF, NX 1953 Series

NX Caveats and Product Notes

NX 1953 Release Notes PDF, NX 1953 Series 5

6 NX 1953 Release Notes PDF, NX 1953 Series

NX central runtime directory

Central runtime directory concept

NX 1953 Release Notes PDF, NX 1953 Series 1-1

• Libraries and executables

Teamcenter code and scripts

1-2 NX 1953 Release Notes PDF, NX 1953 Series

System requirements guidelines

This processor is too old and not supported anymore

• Hidden line rendering

NX 1953 Release Notes PDF, NX 1953 Series 1-3

• Turn SMP on if you have a multi-core system.

1-4 NX 1953 Release Notes PDF, NX 1953 Series

• Complexity of the geometry within individual parts

• Size of the assemblies that are loaded

• Use of Teamcenter in addition to NX

• Some additional memory is required when using Teamcenter 4-tier.

• A even greater amount of memory is required when using Teamcenter 2-tier.

• Updating large assembly drawings

NX 1953 Release Notes PDF, NX 1953 Series 1-5

The following is a summary of findings for the support of multiple monitors.

• NX 6.0.1 or higher - no older releases are supported.

• Two monitors only.

• LCD monitors only

• Run with native resolution and aspect ratio.

Operating system requirements

Operating system requirements

This section documents operating system and service pack requirements.

Minimum Operating Systems

1-6 NX 1953 Release Notes PDF, NX 1953 Series

Contact GTAC for the new NX Linux product.

Starting in NX 1847, the Mac OS X operating system is no longer supported.

Windows 7 and 8.1

System error when running NX

The program can't start because api-ms-win-crt-heap-l1-1-0.dll is

NX 1953 Release Notes PDF, NX 1953 Series 1-7

If you still have a problem, contact GTAC support.

Kernel kernel 3.10.0-957.eI7.x86_64

Considerations and caveats

Java Runtime Environment

Java is used for the following products:

• Manufacturing – Process Studio Author

• Command line version of the following translators:

1-8 NX 1953 Release Notes PDF, NX 1953 Series

• Knowledge Fusion ICE

• Validation Rule Editor

• Simcenter 3D Batch Mesher

• Simcenter 3D Response Analysis Function Tools

• Simcenter 3D Report Writer

• Customer written NX Open Java programs