Jump to content
Ultimaker Community of 3D Printing Experts


Team Ultimaker
  • Content Count

  • Joined

  • Last visited

  • Days Won


ghostkeeper last won the day on March 7 2018

ghostkeeper had the most liked content!

Community Reputation

95 Excellent

1 Follower

Personal Information

  • Country

Recent Profile Visitors

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

  1. The last real change to the Marketplace was in July when the rating system was removed. Our main focus lately (the last 3 months) has been the variable line width algorithm. But that all doesn't matter since the prime blob routine is implemented in the printer's firmware, and focus/resources in Cura development do not detract from what happens in firmware. All Cura does is output the "G280" command. We have absolutely no control over how the printer moves the bed then. For that reason it'd be better to post this in a place that is more frequented by firmware developers: https://com
  2. I don't think I should die for this error 😄 At least not as long as the Settings Guide shows it correctly: https://github.com/Ghostkeeper/SettingsGuide/blob/master/resources/articles/support/support_xy_overrides_z.md I'll ping the website content people if they can fix it. They are the maintainers of those pages. Thanks for paying attention!
  3. The 15.04.06 Debian archive specifies that it requires the following packages: python-wxgtk2.8 or python-wxgtk3.0 python-opengl python-serial python-numpy I don't know in how far those are still maintained for modern Ubuntu or Mint versions. You'll probably still be able to find them online somewhere but maybe not in apt. These are for Python 2, mind you, which has reached end-of-life.
  4. I generally respond to those pings, although I don't track issues on the forum itself. If you seek to modify the layer heights, look for the buildLayersWithHeight function of the Slicer class: https://github.com/Ultimaker/CuraEngine/blob/51ee4b7adf6dfd112241cdf3fd5681e87cf6370c/src/slicer.cpp#L929 In this function it determines the Z coordinate of each layer, either by calculating from the layer height and initial layer height, or by asking the AdaptiveLayer class.
  5. > What should do the users with printers with shared heaters? From our understanding, those users, if they choose to stay with 4.6 or modify that QML file to show the checkmark, should disable the Shared Heater checkbox and only print single extrusion prints. Because if they print dual extrusion prints, the filaments will collide in the nozzle. If you think this is not an issue, please share your opinion here: https://github.com/Ultimaker/Cura/issues/8148 . You can read an explanation of the issue here: https://github.com/Ultimaker/Cura/issues/8148#issuecomment-674429133 .
  6. Sorry, deze vertaling is automatisch gemaakt met vertaalsoftware. Het zit vol met fouten. De leukste vond ik: (Vertaald van "Cura's mould generation is not perfect.") Ik kan een automatische vertaling niet toestaan. Ik heb hier een uitgebreide uitleg gegeven waarom vertaalsoftware dit nooit gaat kunnen vertalen: https://github.com/Ghostkeeper/SettingsGuide/pull/27#issuecomment-671659031 Het is natuurlijk heel wat werk om een echte vertaling te maken, dus de plug-in staat het ook toe om niet alle artikelen vertaald te hebben in alle talen. Het mag i
  7. I think you need to look at where the DLL is located relative to Cura's working directory. Cura's working directory is the user home unless executed from the command line. So it's probably better to just give it a full path. Look into PluginRegistry.getPluginPath to get the absolute path to your plug-in's directory, and combine that with the filename of your DLL. I must say though that I've never worked with loading DLLs using CTypes. My SVGToolpathReader works with a DLL (FreeType) that has Python bindings, so that behaves just like any normal module and I can just import it.
  8. At these very low layer heights, aliasing plays a big role. For instance with the 0.0075mm step resolution, it can't step in increments of 0.04mm. It can only step in increments of 0.0375mm or 0.045mm. So for some layers your flow rate will be 11.1% too small and for other layers your flow rate will be 6.7% too much. The Z axis doesn't normally do microstepping (which would reduce the holding force necessary to keep the bed in place).
  9. To be clear, what you're asking doesn't increase or reduce the capabilities of Cura. If you want the layer height to vary in the range of 0.04 to 0.2mm you would currently use a layer height of 0.12mm and a variance of 0.08mm. With your suggested change, you would use a layer height of 0.2mm and a variance of 0.16mm. We've also had suggestions saying that Layer Height should be the minimum layer height: https://github.com/Ultimaker/Cura/issues/7770 With this, you'd set your Layer Height setting to 0.04mm and the variance to 0.16mm to get the same effect. Or that we shou
  10. Indeed if you have 0.2mm layer height with 0.16mm maximum variation, it will vary between 0.04mm and 0.36mm. If instead you'd like it to vary between 0.04mm and 0.2mm, you should set the layer height to 0.12mm, and the maximum variation to 0.08mm. We've chosen to hold the current layer height as median on purpose, because all of the other settings will have been optimised for this median layer height when you enable it. It will then stay closer to this optimised/preferred layer height overall. It's easier to transition to Adaptive Layers that way.
  11. Tree support is moved to the support section for the next release. The other experimental settings are there for a reason: We know significant issues with (most of) them. For instance the Adaptive Layers feature messes up all of the Z distances because CuraEngine normally calculates Z distances by counting layers. So the Support Z Distance is too small or too large, skin is too thick or too thin, etc. Those two settings you mention, Spaghetti Infill and Wire Printing, are actually also the two features that I proposed to delete recently, to reduce maintenance burden and
  12. Yeah I'll be a bit more thorough, also including 2.3.1 which was the latest 32-bit release: http://dulek.net/work/Cura-15.04.06.exe http://dulek.net/work/Cura-15.04.06-Darwin.dmg http://dulek.net/work/Cura-15.04.06-Linux_amd64.deb http://dulek.net/work/Cura-15.04.06-Linux_i386.deb http://dulek.net/work/Cura-2.3.1-win32.exe http://dulek.net/work/Cura-2.3.1-win64.exe http://dulek.net/work/Cura-2.3.1-Darwin.dmg http://dulek.net/work/Cura-2.3.1.AppImage
  13. In case GR5's download ever goes down, I've made a mirror here too: http://dulek.net/work/Ultimaker_Cura-15.04.06.exe
  14. The setExtraOverhang function creates a buffer on which to draw. Think like MS Paint. You're actually drawing just with a black pen on a white canvas. While you're drawing (the mouse is holding down) Cura's rendering system will draw everything that's black on that buffer in red if it's on the object. When you let go of the mouse, Cura will look up all of the black pixels from that buffer and spray tiny cubes on your object by drawing rays from the camera through the centres of those pixels. I don't think it should be replaced, really, although it would need to be moved to the correct plug-in
  15. Hi Lokster! SandervG gave me a ping about this. It's not unusual that it takes a week or so before we get around to reviewing and testing plug-in submissions. There are a lot of things for the developers to take care of nowadays! Sorry for the delay. I'll get it reviewed this afternoon and ask a colleague to test it.
  • Create New...