How to reduce long compute times switching from design to manufacturer workspace.

[tookemtoni]

The design intent is that I will be going back and forth from design and the manufacturer workspace changing the design to get better nests. Unfortunately it's taking several minutes switching from design to manufacture workspace. This is a serious bottleneck for me. The only reason I'm with Fusion is because it has integrated nesting. 😐

See demo video.

Details:

• There are about 200 manufactured comps and 600 non-manufactured comps
• I have named non-mfr comps with a unique suffix and use "select by name" to hide them. Works great but I assume it would be better if they were not part of the derive from the start.
• I am nesting from a derive as opposed to switching to the manufacturer workspace in the source desgin as not to add more data to the source design. (Isn't this a best practice?)
• The derive source is derived at root to reflect any and all changes. Excluding the non-manufactured comps in the Derive Edit dialog could be an option but it impractical because there are no filtering tools in this dialog and if new non-mfr comps where added to the source they would also need to added to the derive exclusion list. 
• The best would be if the comps properties could be tagged with an "manufacture" indication and only those would be passed onto the manufacture workspace. 🚀

Any tips to reduce switching time in the current build 2602.1.25 (2 July 2025)?

[marcus.toepke]

Can't you use a manufacturing model to avoid jumping between the design area and the manufacturing area?
This way you must do it only one time ... I think 😉

Apart from that, I can empathize with you that it is very annoying yes!

[seth.madore]

We are doing a fair bit of work on the backend to make switching from Design to MFG a less painful task. Would it be possible for you to share one of these data sets so we have something concrete to base our potential improvements on? If you can't share it here, you're more than welcome to drop me an email with the dataset:
seth DOT madore AT autodesk DOT com

[tookemtoni]

Once mfr model is created.,,,I agree switching to it is fast.  But in this case I need to get to the design timeline to make changes that will improve the nesting and going from design to mfr ws to edit mfr model is unacceptably slow IMO.