ID 580624 - Edits to the Sweep Effector using Pen Extrude in MeshOps do not visually update in real-time

Follow
  1. The Foundry SANDBOX
  2. Bug Tracker
  3. Modo

Problem summary
Edits to the Sweep Effector using Pen Extrude in MeshOps do not visually update in real-time.
 
When using a Content Preset to drive the Pen Extrude, any changes made to the Sweep Effector of the Pen Extrude won't visually update unless you toggle the visibility of the Content Preset off and on again.
 
Customer reported version
Modo 17.0v6
 
Customer reported platform
Windows 11
 
Steps to reproduce
 
1) Open Modo. Draw a primitive cube or create a plane. 

2) Select the edges of the plane. Navigate to the Edge tab in the Model toolbar. Select Edges to Curves.

3) In the Edges to Curves menu, select Curve Type: Polyline and tick Create New Mesh. Click OK.
 
4) Create a new empty Mesh Item. Open the Mesh Operations Viewport. 
 
5) With the empty Mesh Item selected, select Add Operator in the Mesh Operations Viewport. Create a Pen Extrude operation and select the polyline mesh created in step 3. 
 
6) In the dropdown menu under the Pen Extrude operation, go to Tool Pipe > (Add Tool Pipe). Add a Content Preset to the tool pipe. 
 
7) In the Content Preset menu, select any premade profile. Your mesh should update in the 3D Viewport. 
 
8) In the Properties, in the Sweep Effector tab, change some of the Profile Attributes such as Size and Curve Subdivision Tolerance. 
 
9) You should not see your mesh visually updating in the 3D Viewport. Toggle the visibility of the Content Preset operation off and on. Now you should see your mesh has visually updated,
 
Expected behaviour
The mesh should visually update as you change the properties in the Sweep Effector.
 
Actual behaviour
The mesh did not visually update.
 
Workaround
Toggle the visibility of the Content Preset operation off and on after making changes to the Sweep Effector.
 
Reproduced by support
This bug has been reproduced in:
Modo 17.0v6 - Windows 11 - macOS Monterey
Modo 17.0v1 - Windows 11 - macOS Monterey
 
Unable to reproduce bug in:
Modo 16.1v8 - Windows 11 - macOS Monterey
 
Earliest version tested
Modo 16.1v8
- This issue doesn't appear in this version and has regressed
 
 

    We're sorry to hear that

    Please tell us why