When in Rome, most people visit great works of art, see masterpieces of architecture, or simply try to convince random tourists that a modern recreation of naval battles in the Colosseum would be really cool and somebody should really get on that. [Andrew] had a different idea, though. He thought meeting up with Slic3r developer [Alessandro Ranellucci] would be just as educational and entertaining as visiting a basilica and thoughtfully decided to film his interview for all to see.
Whenever a file of a 3D object is sent to a 3D printer, the object must first be converted into GCode – the language of lines, circles, and computer aided design that all 3D printers speak. To convert 3D objects to GCode, every piece of 3D printer software from Pronterface, ReplicatorG, and Repetier must first ‘slice’ the file up so the object can be printed one layer at a time.
As the lead dev for Slic3r, [Alessandro], a.k.a. [Sound] goes over the current happenings of his STL to GCode converter – he’s even getting a little support from the very cool people at LulzBot – and the future of Slic3r. There’s still a lot of work to be done optimizing the current software, improving the user interface, and getting rid of all those nasty edge-case bugs.
For as much as we at Hackaday focus on the hardware half of 3D printers, it must be said the current state of the art in desktop manufacturing wouldn’t be where it is without [Alessandro] and other software devs. There’s still a lot of room for improvement – try printing a single wall thickness cylinder without a seam, for example – but without software projects like Slic3r, 3D printing wouldn’t be where it is today.