did not help unfortunately. note that this is standard Mac disk mounting result. To be fair, it should work when I map the disk on the mac by pressing CMD+K and putting http://flashair_ip/ - it mounts and I should be able to use this drive. I'm currently using version 4.0.1 which does not have this ...

nope, no special characters nor long path in my case. http://10.0.0.9/ is mounted as /Volumes/10.0.0.9 with flags webdav, nodev, noexec, nosuid if my problem came from some problem with path, it would happen every time. Sometimes it's enough to save the (previously saved with zero length + error mes...

That is what this is all about. If it is not the model, it must be the slicer. What else? S3D has its flaws, no question. But I feel it is unfair to blame them for all those faulty models out there. Lets leave it at that. If they can do something, tweaking how they handle mesh defects this will be ...

I didn't say this is a bug, only that it looks like a bug. I would not dare to blame S3D publicly when I'm not 100% confident that I have paid my dues already. This is up to the vendor to say this word, not me. Look, I thought this forum is about "Troubleshooting and Bug Reports" (see the name somew...

They did not say it’s a bug, who told you this?

No point arguing man. We are n00bs, they are the experts. That the Support Team admitted this is not expected behaviour and the problem is not the model is a fact but they are the experts. Let them live in the bubble, we know where the problem is

Yeah, whatever

Yeah thanks for support, finally someone who bothered to test it. Support apready answered that they are able to reproduce it and are up to fix it

same problem, S3D v4.1.1 running on both Macintosh and Windows. Message "Failed to execute post processing commands" keeps popping up after saving almost any gcode to a network path. It's happening as well when saving gcode to Toshiba FlashAir webdav share. Note that saving the GCODE file onto Deskt...

I have problems slicing stl files in vase mode in 4.1.1. Some people on this forum are trying to convince me that this version is the best and that my STL files are broken, but I cannot believe other slicers (and s3d v4.0.1 too) work without any issues. Reverted back to 4.0.1 and problems are gone. ...