berndjm

Thank you @tinkergnome, your answer finaly lead me in the right direction, placing the script in $USER/.local/share/cura/<Cura version>/scripts was unsuccessful and also was no hint in the log file. But, a little more searching brought me to: $USER/.config/cura/3.2/scripts where I could succesfully place my script. Not that intuitive place for it, I think ...

Just a, maybe silly, question: Where should I store a custom-made postprocessing script that it will be recognized by the postprocessing plugin? In 2xx versions - not using AppImages - I had the complete PostProcessingPlugin folder (including my script) in .local/share/cura/plugins which works fine. If I do the same in 3.2.1 I see the PostProcessingPlugin is loaded twice (I asume 1 time from the AppImage and the other from my local folder) but my script didn't appear in the "Add a script" Selection list.

Maybe this would be helpfull: https://discourse.appimage.org/t/how-to-make-an-appimage-executable/80

Just noticed, that I get a good visible Z-Seam on a spiralized object (a simple soild cylinder). Inspecting the gcode explains where the Z-Seams comes from, but why is the gcode generated this way?!? Here an excerpt from the code around one "layer-change" G1 X84.653 Y88.444 Z4.785 E89.28759G1 X85.095 Y87.794 Z4.787 E89.29991G1 X85.563 Y87.191 Z4.789 E89.31188G1 X86.065 Y86.621 Z4.791 E89.32378G1 X86.621 Y86.065 Z4.793 E89.33611G1 X87.191 Y85.563 Z4.795 E89.34802G1 X87.794 Y85.095 Z4.797 E89.35998G1 X88.444 Y84.653 Z4.8 E89.3723G0 F5400 X88.659 Y84.526G0 X88.659 Y84.526 Z4.6;TIME_ELAPSED:248.010741;LAYER:23G0 X88.444 Y84.653 Z4.8;TYPE:WALL-OUTERG1 F924.4 X89.093 Y84.27 Z4.801 E89.38412G1 X89.792 Y83.913 Z4.803 E89.39642G1 X90.484 Y83.613 Z4.805 E89.40824G1 X91.214 Y83.35 Z4.807 E89.42041G1 X91.956 Y83.135 Z4.809 E89.43252G1 X92.702 Y82.968 Z4.811 E89.4445G1 X93.464 Y82.847 Z4.813 E89.45659G1 X94.232 Y82.775 Z4.815 E89.46868G1 X95 Y82.75 Z4.817 E89.48073G1 X95.768 Y82.775 Z4.819 E89.49278 As you can see Z increases smoothly to 4.8 than makes a move back to 4.6 and to 4.8 again than continue with the smooth incresement ... the backmove is one layer-height (0.2) This behavior repeats on every "layer-change" ....

Registerkarte "Fortgeschritten" gleich ganz oben "Rückzug"

Send it without the : and without any spaces between the parameter and the value: M301 P24.99 or M301 P24.99 I2.10 D74.21

Hi Manfred, this should be possible by sending M92 together with your desired value in the startcode. Have a look at this explanation: http://reprap.org/wiki/G-code#M92:_Set_axis_steps_per_unit Regards Bernd

and than? Remember in which category(s) the setting(s) in question is(are), close the profile manager, open the category(s) ... wouldn't it be nice if a "star" (or whatsoever) in the category headlines indicates "ey man here are changes" ??? 8)

I think I understand what DaHai want to say ;-) Imagine this (o.k. extreme example): O.k. - there is a change (indicated by the star) ... ... but "where the hell" is this change ...

Even Cura's "core-functions" itsself consists of plugins - this plugins you see in this folder ....

Hi, in 15.04.5 (think it's the same in 15.04.4) there is "Infill prints after perimeters" in the Expert-Settings. On the other hand 70°C for the printbed ... for me it seems a bit high (assuming you're printing PLA <-- Hotend at 210°C?), you could try to lower the bed temperature. Regards Bernd

What's about syncing the setting-folders via a cloud service (e.g. Dropbox)?

On Ubuntu (thopiekars ppa) it looks like this: ------------------------------------------------------ Edit: searched a bit around and it seems that the "postprocessing.svg" simply is missing in the postprocessing-plugin folder - at least in the PPA from @thopiekar

The only snag in it is, that the "active post-processing plugin"-indicator now looks like a "stop" button, beside the pause/play button

You realy use , (Komma) as decimal seperator? Use . (Punkt) instead. Maybe the old parser was a bit more tolerant?!?

@GrendelPrime, @yellowshark you are aware that only gcode-files that was generated with Cura have the information included you need for importing as a profile? Gcode files generated by other slicers cannot work, why "the hell" should another slicer know how the necessary variables are named in Cura

You mean this? If it isn't there please explain "latest update" and also mention your OS...

As far as I know this is per default only in the Ultimaker definitions. If you use a custom printer definition you have to add this entry manualy (if you realy need it) ...

The nozzle selectbox only appears if in your printer definition "has_variants" is set to true and there are definitions in /variants

No, thats another problem: you have a 0.6mm nozzle (resulting from this a line-width 0.6mm) and you wanna print a wall-thickness of 1.59mm that wouldn't work well - I assume - because cura didn't know how to calculate this correct. Wall-thickness should be a multiple (or at least near by) of the line-width (nozzle-size).

Profile -> Manage Profiles -> Import -> File Types -> G-code File

Top Layers and Bottom Layers (or Top Thickness / Bottom Thickness) is your friend. Setting 0 here is the same as unchecking the Solid infill ... in 14.x Any number > 0 gives you this number (height) of solid layers (Bottom/Top thickness in 14.x)

Hi In a textfile exist invisible characters to indicate a new line. In many programming languages and under Linux OS this is a simple "LF". But Windows looks for a "CR" + "LF". This is the reason why you can't see the line-feeds in notepad. If you want to learn more about this -> https://en.wikipedia.org/wiki/Newline

Is "Union Overlapping Volumes" in "Mesh Fixes" selected? If so, unselect it should help.

Hi, no idea -why- you want to do this In Cura 2.3 this is possible. Just set "Wall Line Count" (Wall Thickness), "Top Layers" (Top Thickness), "Bottom Layers" (Bottom Thickness) to 0. Regards Bernd