Possible Bug Command Line --repair & --merge switches no longer work
Hi there! Forgive me if I am missing anything I'm supposed to have. I've never used the Prusa forms before. I checked for others with this problem but found no one.
I upgraded to 2.9.1 from 2.9.0 and found that a python script I created to render stl models using the Prusa command line engine stopped working. I found that I would get an actual error output from on my console saying --repair was not recognized. Commenting out --repair I would no longer get an error at console, but I would during debugging with the error below. I noticed that "returned non-zero exit status 3221225477" always returned this address. From what I can tell, it's just some address that isn't within the read area allotted to Prusa. Outside of that, I have no idea. So, either I can remove the --merge switch, which then Mutiple models no longer merge, or if I uninstall and go back to 2.9.0, everything goes back to working.
I did read the release notes and saw there was some changes to auto arranging prints for printing whole parts one at a time, so it made sense to me maybe something got misconfigured during this new feature. Just a total guess though. I wanted to report this incase this was a legit bug.
Exception has occurred: CalledProcessError Command '['C:\Program Files\Prusa3D\PrusaSlicer\prusa-slicer-console.exe', '--gcode', '--merge', '--scale', '100%', '--load', 'D:\Users\Soh57\Documents\DND Mercant models\Automation\Etsyapp\Profiles\default\filament_Default.ini', '--load', 'D:\Users\Soh57\Documents\DND Mercant models\Automation\Etsyapp\Profiles\default\printer_Default.ini', '--load', 'D:\Users\Soh57\Documents\DND Mercant models\Automation\Etsyapp\Profiles\default\print_Default.ini', '--output', 'D:\Users\Soh57\Documents\DND Mercant models\Patreon\Black Scroll Gaming\Portals\309001_BSG_Calling_Portals_01_Enchanted_Glen\STLs\test_output.gcode', 'D:\Users\Soh57\Documents\DND Mercant models\Patreon\Black Scroll Gaming\Portals\309001_BSG_Calling_Portals_01_Enchanted_Glen\STLs\309001_EG_top_front.stl']' returned non-zero exit status 3221225477. File "D:\Users\Soh57\Documents\DND Mercant models\Automation\Etsyapp\Scripts\test2.py", line 21, in main result = subprocess.run(command, capture_output=True, text=True, check=True) File "D:\Users\Soh57\Documents\DND Mercant models\Automation\Etsyapp\Scripts\test2.py", line 34, in main() subprocess.CalledProcessError: Command '['C:\Program Files\Prusa3D\PrusaSlicer\prusa-slicer-console.exe', '--gcode', '--merge', '--scale', '100%', '--load', 'D:\Users\Soh57\Documents\DND Mercant models\Automation\Etsyapp\Profiles\default\filament_Default.ini', '--load', 'D:\Users\Soh57\Documents\DND Mercant models\Automation\Etsyapp\Profiles\default\printer_Default.ini', '--load', 'D:\Users\Soh57\Documents\DND Mercant models\Automation\Etsyapp\Profiles\default\print_Default.ini', '--output', 'D:\Users\Soh57\Documents\DND Mercant models\Patreon\Black Scroll Gaming\Portals\309001_BSG_Calling_Portals_01_Enchanted_Glen\STLs\test_output.gcode', 'D:\Users\Soh57\Documents\DND Mercant models\Patreon\Black Scroll Gaming\Portals\309001_BSG_Calling_Portals_01_Enchanted_Glen\STLs\309001_EG_top_front.stl']' returned non-zero exit status 3221225477.
RE:
iam facing the same issue. Since Update to 2.9.0 the terminal call with flatpak: flatpak run com.prusa3d.PrusaSlicer -s --load $config_mini_pla $rotate --merge $batch doesnt work anymore. If i call without --merge all works. Could you please check that issue? Thank you very much.
RE: Possible Bug Command Line --repair & --merge switches no longer work
This is a user to user forum. Bug reports need to be made at the appropriate github repository. For Prusa Slicer that is https://github.com/prusa3d/PrusaSlicer/issues
Please follow their guidelines for submitting issues and also please search both open and closed issues with as many relevant keywords to avoid opening duplicates. There are over 4800 open issues currently.
RE: Possible Bug Command Line --repair & --merge switches no longer work
Understood! I'll do that now! Thanks for the guidance 🙂