InStep Studio


Settings: Application Settings

Time to read: ~7 min

The main application settings can be accessed through the Menu: Settings → Application Settings.


Each new release (either larger or simply service releases) are likely to contain some changes to the way that the data is presented (i.e. different order) or what values are presented. In general, though, the interface will be the same:

Application Settings Interface

What is important is not so much the individual entries but how the layout works. The properties can be sorted either by group or alphabetically to better find items. Each entry is in a group of entries that perform similar tasks or are applicable to similar items.
For each setting, when it is selected, a different message shows up in the Information panel at the bottom, providing a description of what the setting does.


Here we will briefly describe each setting. Note that several of these are described in more detail in help sections where they are introduced or also in the tutorials. The entries described here are applicable to and last updated for V3.0.0, Revision 34.

Appearance Group

Color of the background gradient at the bottom edge
Color of the background gradient at the top edge
Default color to apply to single body's facets
Default view to switch to once the geometry is loaded
Color to apply when edges are made visible
Width of the Edges when made visible
Styling to apply to the Triad located at the origin when visible (Tens or Plain)
Color to use for vertices when displayed
Size of points/vertices when displayed
Turns on visibility for items that are not yet considered stable release tools

Behavior Group

Determines whether the application asks to split bodies that appear to consist of multiple parts, specific to the Surfacing tool
Number of facets to consider the threshold to switch into a mode that reduces some of the more time consuming operations.
Determines whether the Interface is to be asked for when the application starts up
If during the login the UserName and Password are to be remembered, then this gets set. Should not be manully reset, use the Settings > License settings instead
Each time a new file is loaded, the view will generally reset (both scale and orientation) to offer a more consistent (albeit perhaps not perfect) orientation. If this is not of interest, it can be turned off. This would still apply for the first file loaded in a session, but subsequent loading of files would then bypass the reset and instead use the previous view settings.
Determines whether the application always splits multiple bodies, never splits multiple bodies or asks the user.
Legacy setting, determining whether the body split operation should consider non manifold edges. Leave in default condition
Undo operations are stored before a more complex operation is performed, such as conversion of facet data to feature data. For simple files this means storing the current set of data either to memory or a local file (which is set from the Data : SaveUndoToDisk setting). However, for large files this storing of data can take a fairly long time on its own as the amount of data can be considerable (all of the memory items are stored to disk or copied in memory). Frequently, this is not needed or the user decides that creating an Undo option is to be skipped in favor of better performance (or long delays due to running out of memory/disk space). It is recommended to turn Undo off as it is not generally helpful in the process.
This is the location where some temporary files may be written to for some more specialized operations. In general, this path must have write access and be on the same drive as the application is installed to. The path should be as short as reasonable.

Booleans Group

This is the number of divisions that the bounding box is divided into along its longest edge for the purpose of determining the result of a Boolean operation. The value should be increased gradually if necessary as it can result in very large data sets. A default value of 200 is generally towards the upper end of what is necessary.


If the application encounters a crash/error, the application attempts to notify the server in order to guide debugging efforts for development. If this value is true then the Log file is uploaded as part of this process. The contained information is considered confidential but does not contain any personal information. It can be viewed by going to Help>About and clicking on the Log-File link at the bottom of this page.
If this value is true and a error report is generated (see above), then the file that caused the issue is also submited. These files are considered confidential and only used for the purpose of troubleshooting issues.
It is possible to export STEP files to assembly step files (where detail parts are provided by reference). Generally, this is not useful as several applications do not properly support this function. However, if such a file is generated and this option is turned on, then the detail parts are written to a subfolder rather than the location where the STEP file is written to.
Determines whether the imported file is to be checked for very large/small data and scaling requested from the user.
If turned on and the import contains a FE style mesh with Prisms, then the application explicitly checks for the order of the vertices within the prism and makes corrections where necessary to follow the Ensight format (same as Patran and a number of others).
If the bounding box scale is below this value it corrects it.
Default method by which to extract surface representation for 3D FE style meshes
Input Units
These are the units to expect polygon data to be in. Use the Import>Resize tool to change scale related items
Applicable to the FE module, if shell elements are present, are they to be imported
Applicable to the FE module, if solid elements are present, are they to be imported
Sets the level of information to be recorded. Currently unused
NUmber of elements above which automatic surface extraction for FE elements is skipped
If set to true and Undo is enabled, the the application creates local files rather than to use memory

Debug Group

Allows a custom folder to be used for storing shader files if the default shaders are not functioning properly.
Defines which of the shader programs is to be first attempted. See property tip for allowed values

Drag Drop Group

Key to clear selection (Edit)
Key to snap the current view to the closest of the default views
Key to create a facet from the selection (Edit)
Key to delete the current selection (Edit)
Keys to reset the view
Clear selection key
Key for select-all
Select/Unselect modifier key
Mouse button to show options
Press-hold-move button for Pan
Press-hold-move button for Rotate
Mouse button for selecting
Sensitivity factor to apply to mouse motion
Mouse Button for selection of rotate-around point
Press-hold-move button for Zoom

Repair Group

Determines whether Intersection testing is to be performed any time that the Issues button/tool is activated or only when requested (through checkbox)
Determines if processes (that can) are to enable parallel/multi-threaded operations (using all available CPUs)

Simplify Group

Algorithm to use for Simplify Methods

Subdivide Group

Scaling factors to apply for subdivision: Change to the parameters (but not algorithm) defined by Doo-Sabin