3DPrinting/PrusaSlicer-NonPlainar
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Fix of #1380 - Wrong estimated time when using extruder absolute coordinates

Browse source
This commit is contained in:
Enrico Turri 2019-04-15 12:54:57 +02:00
parent bf3a52925b
commit 703f65c7bf
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
src/libslic3r/GCodeTimeEstimator.cpp
View file

@ -38,7 +38,6 @@ static const std::string MOVE_TYPE_STR[Slic3r::GCodeTimeEstimator::Block::Num_Ty
#endif // ENABLE_MOVE_STATS #endif // ENABLE_MOVE_STATS
namespace Slic3r { namespace Slic3r {
void GCodeTimeEstimator::Feedrates::reset() void GCodeTimeEstimator::Feedrates::reset()
{ {
feedrate = 0.0f; feedrate = 0.0f;
@ -695,6 +694,8 @@ namespace Slic3r {
set_axis_position(X, 0.0f); set_axis_position(X, 0.0f);
set_axis_position(Y, 0.0f); set_axis_position(Y, 0.0f);
set_axis_position(Z, 0.0f); set_axis_position(Z, 0.0f);
if (get_e_local_positioning_type() == Absolute)
set_axis_position(E, 0.0f);
set_additional_time(0.0f); set_additional_time(0.0f);
@ -715,7 +716,6 @@ namespace Slic3r {
_blocks.clear(); _blocks.clear();
} }
void GCodeTimeEstimator::_calculate_time() void GCodeTimeEstimator::_calculate_time()
{ {
PROFILE_FUNC(); PROFILE_FUNC();