3D printer brand / version + firmware version (if known)
Printer: Conrad Renkforce RF1000,
Firmware: RF.01.47 (development) - modified. This is a customized, Repetier-based firmware specifically made for the printer.
Behavior
Background information:
The RF1000, RF2000 printers were designed to have about 17-20mm of free space in Y, at the front of the bed. So the bed surface actually starts at X=0, Y=20. The reason for this unusual approach is unknown, presumably to make nozzle purging and cleaning, etc, easier.
The printer's actual travel values are X=245, Y=245 and Z=200, which allows a build volume as shown in this picture:
The Problem:
Unfortunately, Prusa Slicer will not slice anything that protrudes in front of the print bed, even if it is within the printable volume.
OK, I would agree that Prusa Slicer should insure the first layer of a print does not protrude beyond the bed surface. But, beyond that, limiting build volume to the projected bed surface is 'stealing' potential build volume from the user.
Prusa Slicer could, theoretically, determine the dimension 'W' shown in the picture, and use that as a limiting criteria. But I think the User should bear a little responsibility, too. Let them worry about 'W'.
But don't take away more than 0.75 liters !! of build volume.
An possible work-around would be to show a warning and giving the user the option to slice anyway.
BTW: Slic3r, v1.2.9, doesn't have a problem with the issue at all. The user could actually place the object completely outside of the print bed and Slic3r will still generate GCode.
Version
2.4.0 beta1 win64 (and presumably earlier versions)
Operating system type + version
Windows 8.1
3D printer brand / version + firmware version (if known)
Printer: Conrad Renkforce RF1000, Firmware: RF.01.47 (development) - modified. This is a customized, Repetier-based firmware specifically made for the printer.
Behavior
Background information: The RF1000, RF2000 printers were designed to have about 17-20mm of free space in Y, at the front of the bed. So the bed surface actually starts at X=0, Y=20. The reason for this unusual approach is unknown, presumably to make nozzle purging and cleaning, etc, easier. The printer's actual travel values are X=245, Y=245 and Z=200, which allows a build volume as shown in this picture:
The Problem:
Unfortunately, Prusa Slicer will not slice anything that protrudes in front of the print bed, even if it is within the printable volume.
OK, I would agree that Prusa Slicer should insure the first layer of a print does not protrude beyond the bed surface. But, beyond that, limiting build volume to the projected bed surface is 'stealing' potential build volume from the user.
Prusa Slicer could, theoretically, determine the dimension 'W' shown in the picture, and use that as a limiting criteria. But I think the User should bear a little responsibility, too. Let them worry about 'W'. But don't take away more than 0.75 liters !! of build volume.
An possible work-around would be to show a warning and giving the user the option to slice anyway.
BTW: Slic3r, v1.2.9, doesn't have a problem with the issue at all. The user could actually place the object completely outside of the print bed and Slic3r will still generate GCode.
Project File (.3MF) where problem occurs
N/A