Open bbinnard opened 2 months ago
Can you share the .3mf project file as well as the .gcode file?
The print file is an STL file, not 3MF. disk.zip I can recreate it as a 3MF if you need that.
This problem still exists with Ver. 2.1.0-beta. The error message is Move out of range: 29.916 1.367 331.092 [-2.000]. No changes were made to printer since I opened this issue.
Please share the project file(3mf file with settings).
I don't know what settings you refer to - I don't think Orca has a way to export it's internal settings.
You can export to a 3mf project in OrcaSlicer file menu
Oh well, I guess I'll stick with FLSunSlicer. Or maybe go back to PrusaSlicer.
Is there an existing issue for this problem?
OrcaSlicer Version
2.1.0-Beta
Operating System (OS)
Windows
OS Version
Windows11/64 Ver 23H2
Additional system information
No performance problem - everything runs OK with PrusaSlicer. My printer is running the current version of Klipper.
Printer
FLSun SuperRacer
How to reproduce
1.Start print
Actual results
Print fails with error "Move out of range: 29.916 1.367 331.092 [-2.000]" immediately
Expected results
Print completes
Project file & Debug log uploads
disk.zip klippy.log debug_Mon_Jun_03_06_27_58_6056.log.zip
Checklist of files to include
Anything else?
This is the 3rd time I'm reporting this problem. I received no useful result on prior 2 reports. Everything works OK when I slice with PrusaSlicer. For this trial I used the Orca definition for the new SuperRacer printer type and tried to print with Printable Area set to 300.0001 (which I think came from the Orca definition for my FLSun SuperRacer printer) and also with Printable Area set to 265 which was suggested by a Facebook user.
My guess is there is some interaction between Klipper and Orca, but I've got no idea what that might be.