So, MakePrintable is now compatible with the m200, which is awesome.
They would also like to integrate their mesh fixing software into Z-Suite.
Personally, I think this would be a great addition to the suite, as it only adds valuable functionality without in any way compromising quality or the high standards of Zortrax’ prints.
What do you guys and girls think? I hope Zortrax recognise this as A Good Thing, and are open to this.
Thanks! Yes please everyone who uses MakePrintable please give your feedback and what you would like to see. With the help of you all we can make this the best software for your 3D printing files!
Also join the MakePrintable group on Facebook.
I've used to use NetFabb but I'll take a look into it (already created @zortrax account).
Does there need to be any integration?
Can't you just upload an .stl, repair it and then load it into z suite?
Or is the idea that it will repair the file better in the final z code format?
It would be beneficial to integrate it, as a mesh repair toolkit would by itself be a feature that would greatly improve the functionality and user friendliness of the software.
Finding a site, figuring it out, uploading, then downloading the model, and then importing it into Z-Suite is a barrier that I believe isn’t necessary.
Z-Suite is kind of bare, feature-wise - but it shows great promise. Also, I’m looking forward to the implementation of individually removable supports in Z-Suite!
It would be beneficial to integrate it, as a mesh repair toolkit would by itself be a feature that would greatly improve the functionality and user friendliness of the software.
Finding a site, figuring it out, uploading, then downloading the model, and then importing it into Z-Suite is a barrier that I believe isn’t necessary.
Z-Suite is kind of bare, feature-wise - but it shows great promise. Also, I’m looking forward to the implementation of individually removable supports in Z-Suite!
Dont count on possibility to export fixed files in ZCODE format, it wont happen - ever.
Does there need to be any integration?
Can't you just upload an .stl, repair it and then load it into z suite?
Or is the idea that it will repair the file better in the final z code format?
I'm not exactly sure what does this Zortrax m200 compability do there since export format is STL, not ZCODE itself.
Keep in mind that by posting your STL to this service, you are giving the design to them. You may still own it, but they can do whatever they want with it too, per their Terms of Use. For casual stuff that's fine (most websites have this sort of agreement), but for something you value, or a customer's design/product, you may need to consider the consequences:
....you expressly grant, and you represent and warrant that you have all rights necessary to grant, to Company a royalty-free, sublicensable, transferable, perpetual, irrevocable, non-exclusive, worldwide license to use, reproduce, modify, publish, list information regarding, edit, translate, distribute, syndicate, publicly perform, publicly display, and make derivative works of all such User Content.....
Keep in mind that by posting your STL to this service, you are giving the design to them. You may still own it, but they can do whatever they want with it too, per their Terms of Use. For casual stuff that's fine (most websites have this sort of agreement), but for something you value, or a customer's design/product, you may need to consider the consequences:
…you expressly grant, and you represent and warrant that you have all rights necessary to grant, to Company a royalty-free, sublicensable, transferable, perpetual, irrevocable, non-exclusive, worldwide license to use, reproduce, modify, publish, list information regarding, edit, translate, distribute, syndicate, publicly perform, publicly display, and make derivative works of all such User Content…
Also we have that in our terms and conditions because we use the files to make sure the program does what it’s suppose to do. Nothing else. If you don’t want us to see it then use the encrypt option.
Not really trying to pick an argument, but if I encrypt the file so you can't see it, you can't fix it either, so there is no point. The grant of license isn't just for your own use, it is about as broad as can possibly be written.
You and the current management may have the absolute best intentions. Future management or owners may have entirely different intentions but the corporate entity still has the license I granted. For most people, it is probably not a concern as what they upload may have no great value. But the Terms and Conditions say what they say, basically that you can do anything you want with my IP. I am aware that this is almost boilerplate language in T&Cs, mainly because it limits the liability of the website entity in the event of some unintended consequence. Let's say the North Koreans hack the site, download my STL design for a hydrogen bomb, and start World War III. I can't sue you for the loss of my country because I granted the unlimited license in the T&C. Most websites with this kind of language have no intention of selling my design for profit or mischief, however they also want no liability if it happens inadvertently. Some T&Cs have in it a standard of care of the IP (generally it is called out as equal to their own, which may not be comforting), I didn't see that in yours but I didn't read the whole thing either.
Very rarely, if ever, will you see in T&Cs unlimited liability for IP loss. The users just need to be aware of what they are giving away, and almost nobody every reads the T&Cs until something bad happens.
Not really trying to pick an argument, but if I encrypt the file so you can't see it, you can't fix it either, so there is no point. The grant of license isn't just for your own use, it is about as broad as can possibly be written.
You and the current management may have the absolute best intentions. Future management or owners may have entirely different intentions but the corporate entity still has the license I granted. For most people, it is probably not a concern as what they upload may have no great value. But the Terms and Conditions say what they say, basically that you can do anything you want with my IP. I am aware that this is almost boilerplate language in T&Cs, mainly because it limits the liability of the website entity in the event of some unintended consequence. Let’s say the North Koreans hack the site, download my STL design for a hydrogen bomb, and start World War III. I can’t sue you for the loss of my country because I granted the unlimited license in the T&C. Most websites with this kind of language have no intention of selling my design for profit or mischief, however they also want no liability if it happens inadvertently. Some T&Cs have in it a standard of care of the IP (generally it is called out as equal to their own, which may not be comforting), I didn’t see that in yours but I didn’t read the whole thing either.
Very rarely, if ever, will you see in T&Cs unlimited liability for IP loss. The users just need to be aware of what they are giving away, and almost nobody every reads the T&Cs until something bad happens.
Yes if you encrypt it the software will still fix the model. We just can’t see it on our end. The user wil still be able to download the fixed model.
So you fix an encrypted STL file without ever decrypting it? That has to be some kind of neat trick.