Jump to content
Ultimaker Community of 3D Printing Experts

ctbeke

Team Ultimaker & Admin
  • Content Count

    377
  • Joined

  • Days Won

    6

Everything posted by ctbeke

  1. Yup, that's because it's very hard to implement. This is just a start to see how to move forward from here. With multiple models it's almost impossible as the layer heights are different per model then, which could cause a collision with the print head. In short, this was the most I could do in ~4 weeks without having to rewrite the entire CuraEngine
  2. Correct. You just need to sync once after unboxing. Connecting it to your phone's WiFi hotspot could be a quick way of doing that. Edit: over time it might be offset slightly (since time-keeping is hard), but then just re-sync and you're set.
  3. Not on the roadmap I think. Is there a reason your UM3 is not allowed to connect to the internet (even just once) to sync the date and time with a timeserver?
  4. Next version of Cura Connect will allow printing without override if the material type is the same (so no brand-checking). Until then, use the override feature in the Cura Connect web UI, or select a different material in Cura that matches the one the printer thinks it has (generic PLA?).
  5. The community event is 23, 24 and 25 February indeed. Both @ghostkeeper and I will be doing a Cura session on the 24th (one about post-processing scripts and one about writing Python plugins). So I guess I'll see all of you there as well
  6. It seems the model is not entirely flat on the bottom. Try sinking it into the build plate a tiny bit and see if the skirt starts generating correctly.
  7. Those are print quality settings, not printER (machine) settings. I don't know which settings are in the quality profile export by head, but it could be that start/end G-code is not one of them. Anyways, this feature didn't change between Cura 2.x and 3.x.
  8. I think the Cura Connect team is aware of this issue, if not I'll alert them. Just a remark: it would be better to file this issue on https://community.ultimaker.com/forum/109-firmware/, as that's where the bug actually is, not in Cura or any plugins. Not all teams check all community sections.
  9. I'm not aware of such a feature in Cura 2.x or 3.x releases. Are you referring to Legacy Cura (15.x and earlier)?
  10. There was a bug in Cura 3.0.4 and 3.1 when using post processing in combination with the network printing (for UM3). These are fixed in 3.2 (Beta due in 1 week). This should solve your issue. In the mean time you can try exporting the G-code to USB and print over USB (as a test). If that also doesn't work there's another bug that we don't know about yet. For reference: https://github.com/Ultimaker/Cura/issues/2855
  11. Cura already has this, it's called support interface in the settings.
  12. Nope, plugins are now full Python code plugins. More details: https://github.com/Ultimaker/Cura/wiki/Plugin-Directory.
  13. I'm not sure if colouring/dual extrusion is in the STL specification (I don't think so, that's why multiple STL's are used to solve this in most softwares). A better solution would be to use the 3MF container format, which supports this in it's specification, and also Cura supports it.
  14. This is an issue in the way that Fusion360 calls Cura. Cura has a --single-instance flag that can be used to solve this. Best would be to contact the Fusion360 developers. For reference, a similar GitHub issue: https://github.com/Ultimaker/Cura/issues/3116 that contains a workaround.
  15. Thanks for suggesting this! As it's not really a core feature I don't think the Cura team will implement it anytime soon. You could however make a pull request on GitHub to add the functionality yourself. Have a look at the image importing plugin to start: https://github.com/Ultimaker/Cura/tree/master/plugins/ImageReader.
  16. Did you connect your printer to a network (that has Internet access)? If not, it might be that the time was not synced with real-world time. Otherwise it's another issue and we need to do some more debugging.
  17. We're patching some things related to nozzle size and line width for Cura 3.2, but planning a larger rewrite for 3.3(?) in order to really fix it. Expect improvements here in the coming releases.
  18. The updates @ahoeben describes are indeed in Cura 3.2. We're also thinking about how to further improve support structures without having to completely re-implement it.
  19. This is actually the 3rd of 4th time I hear about this in 2 days, so I'll discuss during the Cura team stand-up and see if we think it should be picked up.
  20. For reference, here's the related GitHub issue: https://github.com/Ultimaker/Cura/issues/1296. Will indeed be fixed in 3.2.
  21. Hi guys, Thanks for trying out this feature, seeing some great examples already! I head a great time building it (was part of a research sprint, aka do whatever you want but deliver something awesome/useful)! As @ahoeben indicated, this will be in the 3.2 (beta) version of Cura, which is due in roughly 1 week. The stable version will go out about 2 weeks later. We're very interested in hearing how we can improve this feature in the future as well! - Chris
  22. I have one UM3 and the queueing + auto printing system alone is worth the upgrade, I've never printed so much in one evening after installing the firmware update.
  23. Unless the UX peeps feel strongly about this, I would like to have a stab at implementing something like this for Cura 3.1 Would a feature like "favourite settings" solve this? It's not 4 different levels, but adds some freedom in between recommended and custom. I'm afraid that 4 different levels will make things bloated and complex (and favourite settings has been requested before on the forums).
×
×
  • Create New...