Slic3r PE cant write G-Code files
Hi,
new to this forum.
I have created a silly object and tried to run it through slic3r PE to create the G-Code. When writing the files Slic3r says Failed to rename the output G- (see attached)
I did check the permissions on the files and directories and all seems fine. Anyone else have this problem?
The .times file exists in the directory and i do see the .tmp file show up for a few seconds and then disappear.
PrusaControl did not have such problems.
I am running under the latest Windows 10 OS
Re: Slic3r PE cant write G-Code files
Try to run it in a "open" directory, not in your profile-directory.
For example D:\Myprints\Mygode
Thomas
Re: Slic3r PE cant write G-Code files
Hi,
so that actually solved the problem, which got e thinking about why. Turns out I tracked it to a QNAP NAS utility called QSYNC. That utility constantly syncs the local volume to my NAS.
On any directory that had syncing enabled slic3r had this problem most of the time, and on any directory that did not have syncing enabled it worked all the time.
I think that QSYNC somehow delays, or otherwise affects the filesystem operation and files can take longer to disappear/move/rename/etc. I have had this problem with other things like the Particle IDE, but never understood why until now.
Whatever the reason I just use a directory outside of my syncing and all is well.
thanks for the help!
Re: Slic3r PE cant write G-Code files
according to slic3r:
It is a known issue of renaming files on Windows, if you have some file
monitor application active. The upcoming Slic3r release will have a
workaround implemented to retry renaming a file after a bit of delay.
https://github.com/prusa3d/Slic3r/commit/9d9e4a0f7b2d9d3440c2a05bc65b2cab707d148a