Thanks for the response. Being able to adjust the diameter of the towers is definitely a plus. The printer I'm building is a variation of the Pryntech OpenSL printer
http://www.facebook.com/Pryntech. It's the closest thing to the Form 1 you can get that is open source, they actually use the same laser/galvo components as the Form 1. I should be getting all the electronics and laser components tomorrow, I'm just building my own frame. My goal is to make a larger build area than what is common for these photo-resin based printers. Right now, I have a Type A Machines Series 1 and it's a great printer. I use Kisslicer and Pronterface. I've just been waiting for a true "SLA" solution to become open source. I was very close to building a DLP printer but then saw what Pryntech had to offer.
I like that you have an all in one solution, slicing and control (without being specific to one printer). It's silly to have to try to communicate with 2 different developers when problems and feature list wishes pop up.
I'm excited about what you have and the fact that it has SLA-type features like the support towers and the ability to rotate the part in any axis on the build platform. Form 1 has their own software but as SLA printers get more popular in the open source arena, you may have a jump on the other guys from the software side of things. When using the galvos & laser, you gain tremendous speed chewing through the gcode because the galvos can move the mirrors much faster than any XY or Delta printhead. So, you have a chance to grab this SLA market before anyone else does.
One of my ideas for slicing gcode is the ability to "scan" the object rather than jump around when infilling. What I mean is, create your perimeter loops as you do now, then scan, from top to bottom, the infill. Whether it's solid or a percentage of infill, scanning from one end to the other, back & forth. I could be wrong but seems like it would be so much faster than hopping around like most slicers do with gcode on FFF printers.
One other question I have is
can you control the gcode resolution? Kisslicer has an "oversample" setting that allows for finer curve representation (shorter line segments) when slicing. This is nice when slicing high resolution meshes. You definitely don't want the gcode to be at a lower rez than your model. You need a nice XY resolution to compliment you fine Z layers.
What do you think? If you have a demo version or trial, that would be wonderful. If not, the customizable supports has me sold anyway.
Looking forward to giving it a go.
Thanks.