Jump to content

nallath

Team UltiMaker
  • Posts

    4,499
  • Joined

  • Last visited

  • Days Won

    100

Everything posted by nallath

  1. A printer definition can say that they support higher temperatures, but they will need to do so. By default, Marlin (the most common used printer firmware) refuses to print at 365deg C. So that's what we set the default at. If your printer can do more, this is something you will have to change in the definition file.
  2. The same trick as that you used there can be used. The research linked before does this. The idea is to use some form of distortion matrix to transform the model in a certain way. You then slice the model (So you have flat slice paths on a deformed model). Then you perform the inverse of the distortion on the g-code to get curved paths again.
  3. The default is "do not override", not extruder 1.
  4. Could you share a project file? From what you've shown so far it should work, but a project fill will tell us more
  5. The materials on the marketplace are for Ultimaker printers (and therefore; 2.85mm). Printers that are 1.75mm don't show that material as they are not compatible.
  6. Ah, Could you create a new ticket on https://github.com/Ultimaker/Cura/issues (if you didn't do so already?)
  7. You can make that a 100% 😉 As for the G29 command; The engine does not add it. It is only ever added by the start / end gcode as set in the frontend. If a project file could be shared with the setup, I could have a look.
  8. "Unsupported MSVC version" The problem seems to be that you're using a compiler that isn't supported. It's been a while since I created a setup for windows, but it seems that you're using MSVC 2022, whereas the instructions indicate that you need to use the 2019 version.
  9. Are you using Cura 4.13? That issue should have been fixed for that version. If that isn't the case, please report it on Github.
  10. It's also including the platform adhesion in the size in the header. That's why the x & y are different but the z is the same.
  11. Yeah, combing is going to be a nightmare for a model like this. We are still working on optimizing that for Arachne.
  12. You might also want to check out Cura Arachne. It has a different slicing algorithm that should do a much better job for cases like this.
  13. There are multiple reasons. First off is the compiler for OSX that is just more outdated than those for Linux and Windows, making it much harder to get certain multi threading options available. We're looking into porting it, but that is why the osx version of Cura has less multi threading options. Another (more fundamental) problem is that large parts of the slicing process are simply serial; The results of one layer depend on the results of the previous layer. As such, you can't calculate them in parallel.
  14. You have to be a lot more specific than that. What printer do you have? What is your operating system?
  15. Because Ultimaker doesn't have printers with duplication / mirror mode. As such, we never spent time on implementing that. Unfortunately, the companies that do use Cura and have IDEX systems never contributed their changes back.
  16. We first had to wait for other parties to update their software, which is also what we communicated. We're working on these changes as we speak. If you want to get mad at something, get mad at Apple for pulling the rug underneath developers, forcing them to make changes in order to still continue supporting their platform. I get that it's frustrating that it doesn't work, but it's equally frustrating for us (although it's a little less frustrating now since we can actually work on fixing it)
  17. Alternatively, we have a plugin that allows you to read SVG files directly into Cura now: https://marketplace.ultimaker.com/app/cura/plugins/Ghostkeeper/SVGToolpathReader
  18. Print sequence is only enabled if you have a single extruder active. If your machine has multiple, disable all but one and the setting should become visible.
  19. Another user that posts partial log files and assumes that we understand what is going on and also believes that a single crash is an indication that no QA has been performed. Wow. Now that both of us have that out of their system, could you please provide the full log files so that we can figure out what happened.
  20. If you want them included in a next version of Cura, please make a pull request on github.
  21. Uh. The code as developed by Creality. I have no idea what changes they made. Perhaps it's best to contact them for support / help regarding their fork of Cura.
  22. It's not a plugin that can be installed with Cura (if it was, we would have already implemented this in the main code years ago!). Getting this to work with Cura in such a way that we can release it as a full release would take a lot of work. We are currently super busy with making sure that apple M1 hardware is supported, as well as finishing up Arachne. There is also some other work in the same area https://xyzdims.com/
  23. Please post the logs. We can't help you without them. Even better; Please report this on our github. It's super hard to keep track of bugs on the forum. You can do that here: https://github.com/Ultimaker/Cura/issues
  24. You could also have a look at Cura Arachne. That should also have a positive impact on your results.
×
×
  • Create New...