Jump to content
Cura Connect | Survey Read more... ×
Ultimaker Community of 3D Printing Experts


Team Ultimaker
  • Content count

  • Joined

  • Last visited

  • Days Won


ghostkeeper last won the day on March 7

ghostkeeper had the most liked content!

Community Reputation

68 Excellent

1 Follower

About ghostkeeper

  • Birthday 01/01/2015

Personal Information

  • Country

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. ghostkeeper

    Cura 3.4.1 will not start

    To know what sort of bug this is, we would need to see a log file. See some instructions here: https://github.com/Ultimaker/Cura#logging-issues The "Cura GUI log file" is the important one for this particular issue. If you need to get Cura started no matter what, a surefire way to do that is to delete the configuration folder that this log file is located in. This resets Cura to factory defaults, so you'll lose all your preferences and profiles and such. But it probably resolves your issue. And it would be nice if you could copy the log file out for us so that we can see what the problem was and fix it for the next time 🙂
  2. ghostkeeper

    stuck on User Agreement

    I don't know how it came to be, but it seems that your main configuration file got given a newer version number than what we currently use (version 6 instead of 4). One simple solution is to delete the file: C:\Users\[you]\AppData\Roaming\cura\3.4\cura.cfg This will reset your preferences, such as whether you have auto-slice enabled and that sort of stuff, but will not delete your profiles or the slicing settings. In the preferences window you can set your preferences back to what you prefer to use.
  3. ghostkeeper

    Neosanding - Automatic Layer Sanding

    If you click on "Custom" after Print Setup on the right side of the screen, and then type in the search bar "iron", then you should find some settings.
  4. ghostkeeper

    Possible to make dynamic gcode in cura?

    Yeah, that looks like it should work, actually. I am confuzzled! I would expect a ZeroDivisonError here if the bed temperature is 0, because then you'll evaluate 45 * 0 / 0 = 0 / 0. I think the error is happening underwater and it is just displaying the old value then. Try this: "' M190 S' + ('45' if material_bed_temperature else '0')"
  5. ghostkeeper

    How To Create Single Wall Prints? BUG?

    Yeah, a couple but it depends a bit on your printer. For Ultimaker 3 for instance, we've set the line width to be a formula, equal to 7/8ths the nozzle size. So if you set the nozzle size to 0.35, you'd get lines 0.306mm wide, but if you set the line width to 0.35mm, you'd overwrite the formula and get lines of 0.35mm wide. Apart from that, we've also got some other things depend on the nozzle size, such as Outer Wall Wipe Distance (which is set by default to half a line width), but apart from Line Width it's all really minor. https://github.com/Ultimaker/Cura/blob/b00502d10fdfeac9b87465b693e055c6b6406673/resources/definitions/ultimaker3.def.json#L10 You can see this happen really well in the initial layer if you look closely. If you set the line width higher than your nozzle size you tend to get worse horizontal adhesion because the extruder can't handle the pressure pushing against the filament well. But you should get better adhesion vertically because you're really pushing the filament down hard then. This is why we're setting the initial layer line width to 120% by default, to get better bed adhesion. Personally, in most of my prints, I like to increase the skin line width a little bit and then enable ironing. Increasing the skin line width reduces the printing time a lot because you need fewer lines. Ironing then makes the top surface look nice regardless of the crude lines/underextrusion.
  6. ghostkeeper

    Go to Position After Finishing Each Layer

    There is no guide to post-processing scripts, but I've always recommended people to take a look at the other scripts as example. The search and replace script is really simple and should be clear for adaptation: https://github.com/Ultimaker/Cura/blob/master/plugins/PostProcessingPlugin/scripts/SearchAndReplace.py
  7. ghostkeeper

    Ultimaker Cura Prefix

    We were imagining that you'd type something like: {printer_name}_{model_name}_{date} where {printer_name} gets replaced by the name that you gave the current printer, {model_name} gets replaced by the file name that you loaded and {date} gets replaced by the current date. If you were to type 'Printer 01' then it would always give the same name to the print job regardless of what you're slicing.
  8. ghostkeeper

    Ultimaker Cura Prefix

    Yeah, I was about to! Our final decision was to turn the current check box in the Preference window into a text box where you can fill in a formatting string, similar to media tagging software. It's not all that hard to use but covers everyone's use cases.
  9. ghostkeeper

    Ultimaker Cura Prefix

    I think we have a big enough sample size. We'll discuss the results on Wednesday. This was sort of a pilot to see how people would react to involvement in this way. The issue itself is pretty small (trust me, we're tackling bigger issues first really), but it's interesting to hear how people organise their g-code files. We're hearing your feedback that it needs to be customisable and that it would be more useful to have a suffix instead. The suffix should be no problem (if people agree within the team). Customisable may be a bit too much detail for a preference but we'll discuss that Wednesday then. Thanks for participating in any case!
  10. ghostkeeper

    Ultimaker Cura Prefix

    There is already a preference to disable it: "Add machine prefix to job name"
  11. ghostkeeper

    Brim + Skirt adhesion together?

    What if you add 2 extra lines to your brim? Does that then not function as a skirt?
  12. ghostkeeper

    Ultimaker Cura Prefix

    We could have an incremented slice version number but that would reset if you restart Cura then or rename the file you're slicing. For clarity, with "An acronym based on my selected printer's name" we mean that if you call your printer "Ghostkeeper's Printer" then the acronym would become "GP".
  13. ghostkeeper

    Problem with Cura

    This error happens in Windows when mixing up 32-bit and 64-bit applications. Two things you could try: * Don't install a new version of Cura on top of an old installation. So either select a different directory to install it to, or uninstall the old version first. * Make sure to install the Visual C++ Redistributable when the installer prompts you to. In short, I ask you to install Cura again.
  14. Actually, for some of the settings, I'm sort of putting my foot in the door and try to steer it such that it doesn't become a setting. Because some of these settings are just so complex to use for the user that they will hardly ever be used at all. Or there is just one option that is in every case better than its alternatives (but takes 0.05s longer to compute in the engine or something).
  15. There's more information here: https://github.com/Ultimaker/Cura/issues/3725 It's being investigated.

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!