Post-processing script does not write the correct file in PrusaSlicer 2.7.1
 
Notifications
Clear all

Post-processing script does not write the correct file in PrusaSlicer 2.7.1  

  RSS
Scott Gartner
(@scott-gartner)
Eminent Member
Post-processing script does not write the correct file in PrusaSlicer 2.7.1

I wrote a post-processing script in python and tried to get it to run.  PrusaSlicer 2.7.1 runs the script just fine and it passes a path to the file ".77848.gcode.pp" which is fine until the script tried to open it because this file is the binary gcode version, not the gcode version as documented.  

This file should be written as gcode and only converted to bgcode after the post-processing script has run.

One way you can prove that it is writing the wrong file is to put this in the post-processing script block:

c:\windows\system32\cmd.exe

This will cause the export to pause until you close the command window.  You can then go into your "C:\Users\[username]\AppData\Local\Temp" directory and look for the temp file (which will end in .gcode.pp) and see that it is bgcode and not gcode.

 

This topic was modified 4 months ago by Scott Gartner
Posted : 09/01/2024 1:46 am
Share: