search

prusa3d / PrusaSlicer-settings

Prusa3D specific settings for the Slic3r Prusa Edition
GNU Affero General Public License v3.0
358 stars 203 forks source link

Python post_processing script failing on one machine, not on other #267

Closed paynterf closed 3 months ago

paynterf commented 3 months ago

I have two Windows 11 XPS15 laptops. I have a FlashForge Creator Pro II IDEX machine that requires a post_processing step to convert from gcode to gx after being sliced by Prusa Slicer. The post_processor is a python script running under Python 3.10. On my older laptop this works fine, but fails on my newer one with the following error message

Screenshot 2024-08-15 193020

I have the same python script and the same python interpreter version on both PC. I have the same *.INI file on both PC's, and the 'post_process' points to the correct python executable location and to the correct python script.

I have the feeling that the issue is associated with the recent change to use a 'fast drive' temp file as the input argument to the script, but I can't think of a way to test this out. Is there anything I can do to troubleshoot this issue?

TIA,

Frank

paynterf commented 3 months ago

Apologies - operator error. Forgot to install Pillow :(