In 2021 note text is no longer stored in the memory table. The only memory table items used by nesting would be the sheet names & materials, part names, labels & materials, and group names. These items are used to load the dialog pages and regenerate the final nested result. This memory table ids are stored in the nesting operation's toolpath entities and are not visible to the user. I don't believe toolpath entities are available through the API.

Have you reported the issues you are seeing in 2021? There was several nesting text issues fixed in 2021 when opening 2020 or previous version files. Some text was being assigned to the wrong fields, such as part labels showing up as material names. If you haven't please report the issue so we can address it a 2021 patch. Thanks, Steve

In X5 and beyond the default Tool Manager reports are set in Configuration-Reports. If you want a customized report, create a new set of rpx files or change the existing ones using the ActiveReports Designer located in mcamx5\common\reports.

Your "profile tolerance" when adding operations (try 0.001, instead of 0.010). Also, your nesting "resolution"... fine, medium or course (try a user-defined value of 0.100 or 0.010). With the suggested values it should be very accurate.

yes

nesting solid ops is in x5

it might be your mouse... try slowing down your double click speed or... try pressing the mouse and holding it down as you move the part.

yes.

It creates "new" views not "named" views but that is definitely a good idea. Thanks.

The nesting corner and fill direction specify how the parts are placed on the sheet. Also, allowing the parts to be rotated will normally pack the parts closer and fill up the margins.

You can use the ActiveReports Designer to modify the nesting report's RPX template. This allows you to customize your reports.

To nesting 3d geometry... create a 2d boundary around the objects, add this boundary as a part in geometry nesting then use the "attach" function (part page right click) to attach the 3d geometry.

Please describe the steps in as much detail as possible so I can reproduce this. Thanks

Are you nesting each file as a cluster or as individual operations? When nesting a cluster all ops must use the same wcs and all tplanes must be parallel to that wcs. In that case, all ops in the file must have the same wcs. If you are not nesting clusters but each op in the file represents a part then their wcs value should be maintained. Meaning the view might have a different view number but its actual definition should be the same. If this not the case, there may be something we need to look into. Thanks.

Please clarify what you meant by "I set the material thickness after nesting"? How are you setting the material thickness after nesting? Thanks.