After reading the available documentation, I tried to deploy my first attempt at model exporting.
However, for some file types, Export Downloads are not working properly.
In my case, STL and PNG are not responding, G-Code and 3DM download files with empty content, and only DWG (out of the 5 file types I have tried so far), works flawlessly (which is fantastic btw!).
The ShapeDiver export components support many file formats, but not all of them are compatible with all the data types available in Grasshopper. It is the responsibility of the definition to make sure the geometry sent to an export component makes sense with respect to the chosen file format.
In your definition, you are trying to export a Brep object, which is compatible with DWG and 3DM out of your list. For the other file types, it’s pretty clear why they’re not working:
PNG is compatible with Bitmap objects only. Check out the documentation to learn how to import, internalize and use Bitmap objects in your definitions.
STL is compatible with meshes only. I’ll check whether Breps should be converted automatically to meshes before exporting, but it wouldn’t make sense anyways because you typically want fine control over meshes in STL files used for 3d printing.
G-Code is a plain text file format, the export component does not generate G-Code itself. This needs to be done in the definition, and the resulting text needs to be used for the export. The extension is supported as a shortcut, so that users don’t have to rename text files after exporting them from ShapeDiver.
I tested the 3DM export in your deployed interface and it seems to work fine, can you describe the problem you’re having?
Regarding the 3DM, if I recall correctly, it was opening up “empty”. I am gonna try to reproduce the issue again.
On another note, since you replied (and I made the necessary small adjustments) I have been trying to upload an updated version of this definition, but I keep getting upload errors. Below are the reference codes for the upload errors: