Cura 14.03 Slicing does not complete normally

[ianeagland 0]

Hi

Slicing a model (Windows 7) the processing bar goes solid white and stay there. No job time or material used or opportunity to save to SD.

Using 14.01 on the same PC the job time and material used displays work as expected.

14.03 has not hung up because if you change a parameter it reslices but still just ends up showing a solid white progress bar

Regards

Ian

 

[Dim3nsioneer 557]

After the status bar is full, Cura works on the plugins. A blocked status bar might be caused by a closed loop in a plugin.

[ianeagland 0]

Thanks.

Unloaded Tweak At Z 3.1.1 and all OK.

Now to find problem in tweak!

Ian

 

[ianeagland 0]

Ok

I copied the plugin from 14.01 into 14.03 to try.

I now have the problem back. So the identical plugin works in 14.01 but not 14.03 so I am guessing 14.03 is the problem rather than the plugin.

Ian

 

[nallath 1,120]

Could you create an issue on github? It helps us keeping track of bugs.

 

[ianeagland 0]

OK, Issue created

 

[gr5 2,167]

What height did you use in tweakAtZ? Maybe you set it to a value taller than your print?

 

[Dim3nsioneer 557]

What height did you use in tweakAtZ? Maybe you set it to a value taller than your print?

 

@IanEagland: As gr5's question indicates, more information is needed about the issue. Is it possible for you to provide a link to your model and the gcode somewhere? As one of the developers of the TweakAtZ plugin I would like to check if I can reproduce the issue. If the model has to be kept confidential, you may send both files to dim3nsioneer@gmx.ch. I would delete them after the issue is solved.

Thx

Stefan

 

[ianeagland 0]

Hi

Problem must have related to model file in some way. Unfortunately it was a part under development and the original stl was overwritten. I did the same test this morning with the latest STL ready to send files to Stefan and it worked perfectly.

I have closed the issue.

Thanks for all the help.

Regards

Ian

 

[Dim3nsioneer 557]

Good to hear it works (again). However, if you (or someone else) experience the problem again, it would be interesting to know why the plugin fails.