2020.2 Readme

Local Simulation

• Importing STL files into Local Simulation on a Windows 7 Remote Desktop produces a crash. As a workaround, you can launch Local Simulation from a command line with the following command: tscon 1 /dest:console start "appname.exe modelfile.stl" where modelfile.stl is the name of the file to be imported. If this does not work, a more extensive procedure is as follows:

  Determine your remote desktop session ID

  1. At the Command prompt, type query session and press Enter.
     
  2. Find the ID number 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 2020\SIM\appbase.exe" "c:\test\1.stl" ""
     

  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.
• Local Simulation does not work if Netfabb is installed in a folder whose name contains international characters.
• When working with a part that contains "model" in the name, Local Simulation will crash when you perform 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.
• The Clipping Edit function is not available after using the Results Probe on a clipped surface. To edit the clipping plane, turn the clipping function off and then turn it back on again, selecting the desired new clipping surface.
• If a .TIVUS file using a custom PRM file is shared, moved, or copied to a new workstation, then the PRM file will revert to the first PRM file in the Machine Dialog menu. Import the custom PRM using the Processing Parameters Import function to add it to the local library and then reselect the file from the Machine Dialog.
• 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 the Local Simulation is closed and restarted.
• Selected points from the Results Probe will be lost once the user exports a CSV file.
• Some .SLDPRT files will not import the first time. If the user re-attempts the import it will work correctly.
• The new splashscreen that appears upon opening Local Simulation may not be fully visible on smaller screens at some resolutions.
• PRM files created for Lack of Fusion and Hotspot only analysis will be erroneously labeled as "failed", even though they completed successfully. To overcome this issue, manually import the files into the PRM library.

Local Simulation

• 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 (Control Panel > System Properties > Environment Variables) to point to the bin directory of the Local Simulation installation (typically C:\Program Files\Autodesk\NetfabbSimulation 2020\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.
• Unconstrained DED toolpaths will create unconstrained floating elements and incorrect results.