Feature requests

First, I would like to thank you for creating such an elegant and enjoyable CAD application. Plasticity has a refreshing approach to solid modeling, and one of its greatest strengths is that it stays focused on making the modeling experience fast, intuitive, and enjoyable. I would like to suggest a feature that I believe could significantly expand Plasticity’s capabilities over the long term: a scripting API. Many modern engineering and CAD workflows benefit from automation. While interactive modeling remains the primary way users create geometry, there are many situations where scripting becomes invaluable: Automating repetitive modeling tasks. Generating parametric or algorithmic geometry. Creating custom tools tailored to specialized industries. Building plugins that extend Plasticity without increasing the complexity of the core application. Integrating Plasticity into larger engineering, manufacturing, and research workflows. Several established CAD systems have embraced this idea. For example, SolidWorks exposes APIs through C++, C#, and VBA; Autodesk Inventor provides automation through .NET and VBA; Fusion 360 supports Python and JavaScript; and Blender has developed an exceptionally rich Python API that has enabled an enormous ecosystem of community-developed tools. I am not suggesting that Plasticity become another Blender or attempt to compete on extensibility alone. One of Plasticity’s greatest strengths is its clean, focused interface, and I would not want that simplicity compromised. Instead, I envision scripting as an optional capability for advanced users. Those who simply want to model interactively could continue working exactly as they do today, while engineers, researchers, educators, and software developers could unlock entirely new workflows through automation. Some possibilities might include: A Python or JavaScript scripting interface. A documented API for geometry creation and modification. A plugin architecture for community-developed extensions. Macro recording for repetitive operations. An integrated scripting console or editor for rapid experimentation. Such features would not only increase productivity but could also foster a community that contributes tools, utilities, and workflows back to the broader Plasticity ecosystem. As someone interested not only in using CAD software but also in understanding and developing engineering software, I believe that a scripting interface would make Plasticity an even more compelling platform for technical users while preserving the excellent modeling experience that already exists. Thank you for your time and for the work you continue to put into Plasticity. I look forward to seeing how the software evolves in the coming years.

The default colour for splines - powder blue - is not a good one. This is especially so when laying out spline cages. For example, creating splines over black and white reference images in which case the splines tend to 'vanish' especially when editing points. Plasticity therefore needs to allow users to choose a default colour they are happy to use and not have have powder blue imposed on them.

I believe a 4 function/scientific calculator should be added for convenience.

Especially for the surface modeling workflow, there are two important tools that I frequently use in my pipeline: Rail Revolve and Sweep 2. Having similar tools available in Plasticity would be a great addition to the surface modeling workflow.

It would be cool if you could create dimension configuration tables that you could name and edit within the table, like you can in Solidworks. This would greatly benefit engineering users.

It's almost routine that when you create a patch from one of the primitives - circle, rectangle, polygon - you will want to delete the primitive as they may be of no further use. This involves an additional and constantly very repetitive action of selecting the primitive and deleting it. As creating a patch activates a very simple dialog box, it would be great if there was an option, say a check box, to delete the primitive leaving only the newly created patch. Although small, I think this would be a very welcome addition to modelling workflows.

For those of us that need to name objects, sorting by name would help to find items especially when hidden.

When selecting an object in the viewport, expand its entire group hierarchy and reveal the exact object in the Outliner.

Avoid requiring users to switch to Edge selection just to reposition an enclosed curve.