Solid Modeling Fix

1. Some users reported that there was an issue with the Solid Modeling Tools and Solid Modeling Analyzer, wherein an error would occur if they attempted to access either, after switching off their Solid Modeling Custom Tools module within their license. This issue has been resolved- SMT and SMA should no longer function as dependent on the Solid Modeling Custom Tools module.

UI Fixes

1. When hovering over the “Connection Name” setting in the default saw processing station, the help text displayed was the help text for the “Saw Blade Width” setting, with the correct help text only popping up when one hovered over the input field. This issue has been resolved, with both settings now displaying the correct help text, when one hovers over the setting name.
   

Figure 1: "Do Not Show Again" option missing.

1. When users attempted to add machining tokens to parts that they did not have the proper tools in the spreadsheet Toolfile to create, the software correctly displayed a warning message. However, this warning message was unable to be prompted to not show again, with that specific checkbox absent from the UI. This issue has been resolved- the dialog box should now have a "Do Not Show Again" option added to the bottom of it.

1. The Project Properties UI header has been altered to a different color to correspond with the appearance of other interfaces.

1. When a user was disconnected from the internet after requesting a module trial, the request would simply cancel and quit the module trial without any displayed error message to inform them. This issue has been resolved- a warning message should now pop up to inform users when they have been disconnected, and that their download should resume when reconnected. 
   

Figure 2: Previous Drill Depth text (left), updated Drill Depth text (right).

1. The BORE hardware machine token was found to have incorrect help text when one clicked on the “Drill Depth” value in one’s machining tokens, getting a description that was not concise or accurate to the field. This issue has been resolved- the text has been updated to reflect the function of the "Drill Depth" field more accurately. 

Dado and Polyline Fixes

Figure 3: 2D part drawing before associative polyline token move (left) and after (right).

1. Users reported an issue with associative polyline tokens, wherein the associative polyline tokens on the right-side part of their product would not cut correctly but would display correctly in 2D drawings and 3D modeling. When comparing 2D part drawings to processed nest composite drawings, it was found that the cut of some parts would be moved. This issue has been resolved- the cut on parts should no longer move when using associative polyline tokens.
   

 

Figure 4: Skewed dado route in product.

1. There was a reported issue some users had with dado routes, with the dado routing in their products being skewed in the cabinet sides when using a ¼” router. This issue has been resolved- a 1/4" router should no longer produce any skewed sides when using dado routes. 
   

Face 5 Barcode Fix

1. There was an issue reported by users using spreadsheet PTP Toolfiles, wherein they found that products with HBORE and Face 6 machining applied would sometimes fail to have the “Run” field on the barcode for the face 5 border program, even with “Always Route Borders” applied. This issue has been resolved- the Run field should now appear on the face 5 barcode.
   

Report Group Fixes

1. An issue was reported, wherein some users found that when updating their G-code from composite drawings in the aftermath of processing a batch, their G-code would automatically create report groups. This issue persisted even when the “Process Report Groups” setting in the Processing Center was disabled. This issue has been resolved- with the "Process Report Groups" setting disabled, no report groups should be generated. 
   

Session Connection Fixes

 

Figure 5: New reconnection dialog box.

1. A dialog box has been added to inform users who have previously lost connection during a session that their session has successfully been reconnected, to help ensure there is no confusion regarding the status of one’s connection. 

1. Some users with SLS licenses reported an issue with their event logs: when experiencing an error (such as a lack of internet connection during an attempting opening of a session), the error would not be stored in the event logs, and they were unable to locate any record of it for use as future reference. This issue has been resolved- event logs should now track errors related to connectivity without issue.

1. There was sometimes an issue experienced by users whose devices had idled during a session, with the software erroneously giving them a prompt that states they have been disconnected and must reconnect, even when they are currently still connected. This issue has been resolved- users should no longer have this message appear when their station has been left idle but connected.