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
- At the Command prompt, type
query session and press Enter.
- Find the ID number in the rdp-tcp row (typically 1 or 2).
Create and run a batch file
- 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 2018.3\SIM\appbase.exe" "c:\test\1.stl" "" - 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.
- At the Command prompt, type
query session and press Enter.
- If you close Local Simulation after initiating a cloud solve, the cloud solve is interrupted. As a workaround, you can enter your Autodesk Account credentials and enable the Stay signed in check box. When you close Local Simulation, you will be prompted to save your project. The next time you open Local Simulation and open the previously saved project, you will be automatically signed in and your cloud solve will show that it is running (if not already completed). As a best practice, we recommend that you are always signed in before opening a project or importing a new model in Local Simulation.
- Local Simulation does not work if Netfabb is installed in a folder whose name contains international characters.
- If you complete a simulation with at least one part and one support and later apply unique PRM files for the part and support using the "Unique for all parts and unique for all supports option", you will receive an error when attempting to solve again. As a workaround, you can use the "Unique for all parts and unique for all supports option" on a new simulation or use the "Per geometry" option to apply unique PRM files to the part and support.
- The first time you submit a simulation to be solved on the Cloud, you may receive an error about starting the simulation. This issue can appear if you have a slow network connection and the server cannot verify your user account. As a workaround, simply save the project, close Local Simulation, reopen the project, and solve again.
- 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.
- Simulation results now include a file <projectname>_f.case that reports on recoater interference for the simulation, either 0 for none, or 1 for one or more incidents of interference.
- When a saved .tivus project is reopened after closing Local Simulation, any heat treatment schedule input will be truncated to the first two lines. The user will have to re-enter additional lines before simulating the project again.
- Log files from PRM files generated on the cloud are not available from the Processing Parameters Library, but are accessible from the Job Manager.
- Local Simulation does not solve DED type simulations if it encounters Unicode characters, such as Japanese or Chinese, in the LSR file name or in the path to the solver. To check this path in Local Simulation, select and see the Executable field.
- Local Simulation cannot solve simulations or generate PRM files on the cloud using Unicode character files or directories.
- Local Simulation cannot export warped STLs using Unicode character files or directories.
- PRM files that include Hot spots and lack of fusion analysis types must have at least one temperature entered for both Lack of fusion and Hot spot fields.
- PRM files generated on the cloud will not show an error messaging window if the simulation fails. Open the log file from the Job Manager window to investigate and fix the cause of the failure.
- 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.
- Exporting multiple Warped STL files from the same project using the same warp factor will overwrite the existing file. To save new files, manually change the exported file name.
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 () to point to the bin directory of the Local Simulation installation (typically C:\Program Files\Autodesk\Netfabb Local Simulation 2018\bin).
- Local Simulation cannot generate PRM files with Unicode paths or file names.
- Be sure to set the netfabb_sim_vars.sh environment variable 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.