herzla

or isn't there a function to update UI within a long operation?

i wrote a little plugin doing changes on the gcode as it sometimes needs several seconds I tried to show a progress-bar but UI is blocking - so I switched to a sub-thread to do the work but it's still the same if I don't wait for the thread to finish the progress-bar get's shown and runs smooth but I need to wait for the thread? or can I tell cura to wait for the thread to be finished? (~~ i don't know much about python ~~ but I did some research ~~) .. import threading from time import sleep .. class SamplePlugin(Extension): def __init__(self): ... self._application.getOutputDeviceManager().writeStarted.connect( self._processGCode ) ... def _processGCode(self, output_device): self._message = Message(catalog.i18nc("@info:progress", "processing gcode changes"), 0, False, -1) self._message.setTitle("Sample Plugin") self._message.show() x = threading.Thread(name="SamplePluginThread", target=self.threaded_processGcode, daemon=True) Logger.log("d", "start thread") x.start() *** how to wait without block*** ?? x.join() is blocking UI wait-loop is blocking UI also while x.is_alive(): sleep(0.1) *** how to wait without block*** ?? Logger.log("d", "fan control thread finished") #self._message.hide() #self._message = None def threaded_processGcode(self): ... for line in lines: if line.startswith(";LAYER:"): iLayerNr = int(re.split(':| |;|#|\n',line)[2]) if self._message: self._message.setProgress(iLine * 100 / len(newLines)) ...

thanks, you created custom support for this screenshot? does it look the same when using tree-support? did you change other option also? I didn't got it looking like yours

I created this little sample model to make testing faster (real model is similar but more complex and bigger and needs 20 minutes to slice) pls don't recommend to print it upside down 😉 i was able to remove all transactions "inside the bowl" by using Combing Mode = all and disabling Z-Hop on retraction but when support is active there is one travel move through/over the model on each layer from support to the shell to be able to print this part with materials like TPU where stringing never ends I need to get rid of this travels another problem is that Z-Hop needs to be dissabled so this move goes over the already printed support and oftain touches it - I already needed to abort an PETG print because this travels broke the support 'avoid printed parts when traveling' is important to be checked 'avoid supports when traveling' does no change changing 'Z seam alignment' doesn't help also is there a way to let this travels go around "outside"? how can I enable Z-Hop again? model file: uBowl.3MF thanks 🙂

"Remove Empty First Layers" gehts hidden when support is active - seems like it gets disabled also in older Versions (until Beta2) but is hidden and active in 5.3 release when I disable support, than disable "Remove Empty First Layers" and then activate support again the GCode looks as espected and starts above the bed @GregValiant may you can check if this is same on your computer and may it was disabled?

may you answer my question about the preview - otherwhise I can't help you as the model drops down every time and the bug is only on adaptive layers there is not much outside cura that will affect it the model dropping down in preview is a bug already and with adaptive layers it get's worse 😄 😄 😄 for sure, different language on OS and Cura 😄 😄 😄 I beleve, I was sure before, it workes fine in 5.3 Beta 2 and I just know it's possible to let models start "in the air" since yesterday so I don't think a lot people do that.. and even less with adaptive layers ~~ there have been a lot of (quite deep) changes from Beta 2 to release without public testing so I also still see tree-support growing through the model, brim errors and I see a lot more new and unsolved problems on github depending 5.3 "release" I got really sad when I saw the xmas-tree and don't know the reason why they needed to hurry on the release so may I just skip 5.3 and come back next year 😄 may this thread prevents others to crash the bed - github may show us the truth soon

i opened the project on another windows 10 computer with fresh cura 5.3 installed Z ist starting at -1.19 when I use standard-profile the model get's dropped in preview but Z ist starging with positive value enabling adaptive layer (0.18+-0.8) makse the change - now also with absolute standard voron 2.4 profile Z is starting negative attaching a simple model producing same bug V350_MGN9_Assembly_Tool.3mf V350_MGN9_Assembly_Tool.gcode

it never happened before and I can reproduce it in 5.3 release.. and I think most users place models to the plate.. i also disabled all post-process-scripts and also arc-welder - just in standard-profile I didn't get that error and will continue testing when you slice it - is the model dropped to the bed in preview or is support below? PRINT_START is a standard command in klipper - just in Cura there is no option for klipper firmware.. I attached the gcode so you see Z-value starts at -1.19 and continues "correct" (-1.09, -.99, -.89) negative_z_53.zip

no, I'm not runninge Octoprint my Start-G-Code is corrent seems to be another Bug in 5.3 - it looked same on my computer until I resized the window - then the full code was visible only post-process is the standard 'Insert at Layer Change', and another script inserting layer-change information I can reproduce it any time when the Model starts 2mm above the bed with tree-support and support-roof active when the model starts on the print-bed everything is fine and working

I added a little tube next to my model so something is touching the buildplate and now the print starts above the build plate but support-brim is missing /edit: it works again after I enabled skirt - before it was set to 'none' as I don't need print a skirt when support-brim is enabled this is how 1st layer looks in Cura 5.2:

i was printing the whole day, since some hours in 5.3 release suddenly my printhead crashed the bed - after some searching I checked the gcode and the first move goes to Z-1.19 G92 E0 G1 F1800 E-0.5 ;LAYER_COUNT:396 ;LAYER:0 M107 G0 F6000 X206.319 Y233.911 Z-1.19 ;TYPE:SUPPORT G1 F720 E0 i don't have a z-offset plugin installed I also don'f find a setting to change Z-offset in Cura currently several instances of Cura are running, all base on same profile, seems like only one instance starts at negative Z byby PEI //edit: after some more testing it seems like Cura 5.3 has a Problem when the model starts in the air and needs to be support on full surface in Cura 5.2 it works fine bed_crash.3mf

oh, i didn't see the answer.. MeshTools are installed and active already - body is not watertight is the only message but that may be fine as the model is open at the bottom Fast-Quadric-Mesh-Simplification is unable to load my STL - tried binary and ascii mode I can send you model and project, is there another way to upload as I don't like to publish the full model? since I needed to change support to 'everywhere' also a part of the model get's supported that should not get supported and the support-blocker get's ignored same model works fine in Cura 4.8 in both cases

~~z-hop (disabled) is the only difference~~

i tried all combing modes but it just got worse travel "withing the model" would be the solution I think, yes I see serveal threads to this topic but all end up in stringing settings or stepper-current as it's not only the stringing I need to solve here it would be great to really find a way to change the travel-moves

as you see in the first 2 screenshots my model is like a bowl and I have a lot of travels "inside" in the 3rd you may see there is one travel "along the model" and on layer-change there is one travel diagonal over the model 'avoid printed part when traveling' seems to have no effect and even when I change the Z-Seam-Alignment to shortest I have travels to the bowl (and also I can't use this option) suggestions? I'd like to print with TPU and that stuff just doesn't stop stringing..