You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is what the developer mentioned as roadblocks:
TOOL CHANGE gcode is in wrong position, the actual Tn gcode is before the comment. Not a big problem, the TOOL CHANGE comment isn't mandatory and could be removed, but still it needs bit of work to verify it works properly
no settings saved in the gcode. There's a kind of encoded piece at the end of the file, but extracting values from it would need to be implemented. Also the piece probably isn't the full list of settings. This is a blocker at the moment; alternative way to tell filaswitch the settings would need to be implemented before Cura gcode can be processed.
relative extrusion needs to be turned on by user, not a biggie, same thing needs to be done in S3D depending on the printer profile
Would a Cura dev be interested in looking at these? Only n2 is really critical to make this work together, n1 is nice to have, and n3 is just documentation.
The text was updated successfully, but these errors were encountered:
cfelicio
changed the title
Filaswitch Compatibility
Feature Request: Filaswitch Compatibility
Apr 13, 2018
Hi @cfelicio , thanks for your suggestion. I've discussed this in our team but we're not going to look at it. Since Cura is open source, everybody is of course invited to create this feature. Maybe the creator of filaswitch? You can try to use some post processing scripts to see if you can get it working in your setup, but that requires some tinkering skills.
Hi All,
Filaswitch currently supports S3D and Slic3r, it's heavily used for post processing multi color objects, so you get a smart prime tower in your gcode.
I would love to see Cura on the list, so I opened a request over there:
spegelius/filaswitch#43
Here is what the developer mentioned as roadblocks:
Would a Cura dev be interested in looking at these? Only n2 is really critical to make this work together, n1 is nice to have, and n3 is just documentation.
The text was updated successfully, but these errors were encountered: