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\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 solve simulations if it encounters Unicode characters, such as Japanese or Chinese, in the path to the solver. To check this path in Local Simulation, select and see the Executable field.
- Local Simulation cannot work with files or directories named with Unicode characters, as used in Japanese, Chinese, or Korean languages. Avoid using such characters to name any files to be imported, such as process parameter, STL, and TIVUS files. Also avoid using such characters to name directories when saving files or projects.
- If you open a Netfabb 2017.3 project in Netfabb 2018.1 and use the Simulate Process functionality to send the model to Local Simulation, models with open supports are suppressed in Local Simulation. As a workaround, you can regenerate the supports in Netfabb 2018.1 and click Simulate Process to send the model to 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.
- When examining quantitative stress results, the Index reported on the Results tab does not match the Increment number reported when you hover your cursor over the timeline. The Index begins counting at the first sign of plasticity, therefore it displays a much lower number than the Increment shown in the timeline. Refer to the analysis log files to determine the increment at which the plasticity step is applied.
- 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 examining results for Lack of Fusion Volume, Hotspot Volume, or Interlayer Temperature, the Index reported on the Results tab is fixed to 1. This value is also reflected in the timeline.
- 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".
- If you experience a power outage, you may not be able to open
Local Simulation. As a workaround, delete the
tivusJM.ctrl file from the following location: C:\Users\yourusername\AppData\Roaming\Autodesk\Local Simulation for
Netfabb 2018.2\2018.2.
Tip: The AppData folder is hidden by default. To view, type %appdata% into the Windows explorer folder browser.
- The new combined PRM files in Local Simulation for Netfabb 2018.2 don't allow you to use multiple PRM files for a part-level simulation. Refer to this knowledge article for additional details and a workaround.
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 resolve relative paths to navigate to the execution folder. As a workaround, use the "cd" command to navigate to the directory containing the input file.
- Local Simulation cannot work with files or directories named with Unicode characters, as used in Japanese, Chinese, or Korean languages. Avoid using such characters to name any files to be imported, such as process parameter, STL, and TIVUS files. Also avoid using such characters to name directories when saving files or projects.
- 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.