2024 Readme

The Sort function in the PRM Library is not effective for the PRM type, Interlayer Temperatures, and Last Modified columns.

Lack-of-Fusion-only and Hotspot-only PRMs will be erroneously labeled failed if given a name containing unicode characters.

Selected points from the Results Probe are lost upon closing the Table window.

TIVUS files with names containing more than one period (.) cannot be used to create warped STLs in Local Simulation. Use a different filename, or use the distort_stl tool to warp files from the command line in Local Simulation.

Importing STL files into Local Simulation on a Windows Remote Desktop may produce a crash.

As a workaround, try launching Local Simulation from a command line with this command:

tscon 1 /dest:console start "appbase.exe modelfile.stl"

Replace modelfile.stl with the name of the file to be imported.

If this does not work, you may try this:

Determine the remote desktop session ID

1. At the command prompt, type query session and press Enter.
   
2. Find the numerical ID in the rdp-tcp row (typically 1 or 2).

Create and run a batch file.

1. In a text editor, create a two-line batch file (.bat) with the correct Session ID, Netfabb install directory, and STL file path. These elements are located as shown below:

   tscon <session ID> /dest:console 
   start "" "<Netfabb install directory>\SIM\appbase.exe" "<STL file path>" ""
   

   An example is as follows:

   tscon 1 /dest:console 
   start "" "C:\Program Files\Autodesk\Netfabb Ultimate 2024\SIM\appbase.exe" "c:\test\1.stl" ""
   

   Replace the <…> placeholders with the paths and names applicable to your system.

2. Run the batch file as an administrator.
   Note: The batch file will end by logging you out of the remote desktop connection. Log back in to see the imported STL file in Simulation Utility.

• For the Windows Remote Desktop, an additional possible workaround is to open Local Simulation on the server station and leave it open. When remoting in, this is less likely to trigger an immediate crash.

Either way, other remote desktop products are not known to be affected by this issue and would lend themselves to be valid alternatives.

Tivus projects with custom unicode coded PRM files that are transferred to new systems, or after changing the PRM library, will not import the custom PRM file. Custom PRM files must be re-imported and reassigned.

Switching from multiple displays to a single display, dialog menus may appear off screen. To fix the issues reinstall Local Simulation.

If a DED mesh preview is made and then the mesh settings are changed before solving, the Mesh in the preview may not match the one observed in the simulation results.

Closing the results table in the DED workspace turns off Warp by Displacement. Warp results visualization must be restored manually from the Plot Settings menu.

When working with a part that contains model in the name, Local Simulation crashes when upon performing a mesh preview or a solve. The error is caused because Local Simulation incorrectly writes multiple STL files to the *STLF keyword.

As a workaround, rename the part so that it does not contain the text "model".

Warning and error notifications are cleared from the list of toast notifications when a simulation is re-run.

If a part level powder bed or DED model is run while a PRM generation process is in progress, critical warnings and error notifications for the PRM process are not shown. Warnings and errors for a PRM generation are available from the View Logs button within the Job Manager.

If multiple PRM files are generated simultaneously, the Lack of Fusion, Hot Spot, and Interlayer temperature columns in the Processing Parameters Library can remain blank until Local Simulation is closed and restarted.

Some SLDPRT files do not import the first time. Re-attempting the import, however, should succeed.

Using the Wall thickness meshing approach is liable to generating mesh settings beyond the simulation limits of Simulation Utility included in Netfabb Ultimate.

The first time you solve from the command line, you may receive a message saying "'pan' is not recognized as an internal or external command, operable program or batch file." As a workaround, edit the Path environment variable (Windows Control Panel > System Properties > Environment Variables) to point to the bin directory of the Local Simulation installation (typically C:\Program Files\Autodesk\NetfabbSimulation 2024\Solver\bin).

Be sure to set the environment variables in netfabb_sim_vars.sh according to your system. Refer to the Shell and Intel MKL Environment Variables section of the help for details about controlling the number of threads and the memory limit per thread. If these variables are not set in accordance with your system, a segmentation fault can occur.

Under-constrained DED toolpaths creates under-constrained floating elements and incorrect results.