MosaicManufacturing / canvas-issues

Bug reports and feature requests for Canvas
https://canvas3d.io
8 stars 6 forks source link

Filament Aliasing #186

Open rcmaniac25 opened 3 years ago

rcmaniac25 commented 3 years ago

Is your feature request related to a problem? Please describe. Add the ability to alias one filament to another so CANVAS considers multiple colors as the same filament input.

Describe the solution you'd like For coloring purposes, I may want to section off a portion of the model, but then for printing I may not want it to be a different color. Ex. 3D printing a head where each eye is a different color in CANVAS, but for the most part they will always be the same color. Currently, CANVAS doesn't match color+material (which is understandable, I may have 2 grey filaments: one PETG, one PLA or one light grey, one dark grey). I'd like to be able to say "filament 3 is actually filament 1" by aliasing it (or whatever terms is desired). This way when it goes to slice, instead of doing two transitions: 1 -> 2, 2-> 3, it does one transition: 1 -> 2 and just uses filament 1 for both 1 and 3.

If #169 exists, this becomes similar to how stamping works when uploading an image: you can paint in virtually unlimited color options... but have the hardware limit, so you instead have to now pick from a limited pallet of colors/materials and alias the rest, but would mean that in future implementations (a Palette with 5+ inputs, or combining Palettes, or IDEX/tool-changer + Palette(s) then the alias can just be removed and it will automatically support more color/materials options.

Describe alternatives you've considered Copies of a project, where the higher details are removed.

Additional context Came up after I had painted a model for Halloween and was asked if they could get the model (printed) in just 2 of the 3+ colors I had painted it in. I changed one color to the same as another, and CANVAS simply considered 2 different filaments but I didn't want it to.

brandonbloch commented 3 years ago

This is an interesting concept! I could see a half-measure feature where you can "merge" one input into another permanently, but the full "aliasing" idea may fit nicely with some planned workflow changes.