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

99 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 setting Remove Mesh Intersection prevents meshes on multiple extruders from extruding in the same area. If you disable that, you can achieve toolpaths that cover the same area. Getting it to produce exactly the same paths could be tricky though. Need to make sure it has exactly the same settings everywhere, at the very least. With a post-processing script this is pretty doable. That would be the preferred solution in the end at least, but requires programming skills. If you really want to get into the code where this collision prevention is implemented, it'll be her
  2. Need to look into Firefox add-ons like uMatrix and NoScript, since this upload is made directly to the Google Cloud Platform, so you'd need to allow access to those domains.
  3. No, the initial layer is also sliced through the middle of its Z range: https://github.com/Ultimaker/CuraEngine/blob/991cd026ffccc6def5e5b6a937edd6ae1b7cc8bf/src/slicer.cpp#L957
  4. The real answer is that it depends on the Slicing Tolerance setting. But going by the default of "Middle", it would create a cross section from the middle of the Initial Layer Height. So if your Initial Layer Height is 0.2mm, it would create a slice at Z=0.1mm. Thus, you'd need to make sure the bottom of that sphere protrudes by less than 0.1mm.
  5. Indeed, as ahoeben already said, the changes to CuraEngine can't be implemented from a plug-in. You might be able to make changes in a post-processing step that works on the g-code string, but anything involving the polygonal shapes of support, slice layers, etc. will probably be impossible because it's very hard to retrieve the original shapes that were intended to be printed from just g-code. So you can't just perform a polygon offset or anything. Since you need to modify things in FffPolygonGenerator and FffGcodeWriter, I'm pretty sure that you can't do those things from just post-processin
  6. Hey. I can share what I know of the X3G conversion. Thanks for the ping, Greg. The X3GWriter calls upon an executable called GPX to convert g-code to X3G: https://github.com/markwal/GPX The X3G files work slightly differently than g-code files and they need slightly more information. Sometimes this is where mistakes sneak in. GPX accepts extra settings as parameters and Cura translates most of those to machine settings that you can modify through the Printer Settings plug-in on the Marketplace. This means that *machine settings may affect the X3G conversion*. In pa
  7. 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
  8. 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!
  9. 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.
  10. 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.
  11. > 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 .
  12. 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
  13. 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.
  14. 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).
  15. 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
  • Create New...