Jump to content

ahoeben

Ambassador
  • Posts

    4,966
  • Joined

  • Last visited

  • Days Won

    342

Everything posted by ahoeben

  1. It is not an SDK in the traditional sense of there being a downloadable package. The SDK is already part of Cura. I would have called it an API.
  2. What sort of plugins would you like to create?
  3. The aforementioned PR has been merged, so the dialog should look like this in the next release:
  4. 175 degrees is the standard "Standby temperature" for PLA. Cura uses the standby temperature to prevent oozing and material degradation by keeping the same material in the hotend.
  5. It does, but there's a missing scrollbar. You can still scroll the list of printers, either with your mousewheel or two-finger-scrolling, or by going to the right of the list and dragging where the scrollbar would be. This pull request fixes this usability issue, but it is not yet clear if it will be accepted for Cura 4.7.
  6. Do you have multiple displays? If so, does it matter which display Cura is on?
  7. Note that there is a scrollbar in the list of printers that can be added, but it is hidden untill you use it.
  8. I'm working on a version of the Custom Job Prefix plugin that also supports a configurable postfix (I'm going to have to change the name of the plugin...). If you would like to test it out, download this development snapshot and drop it onto the Cura buildplate as if you were opening a 3d model.
  9. A "project" is saved with File -> Save..., not with File -> Export... Projects are saved as 3mf files, and include the model and settings. gcode files do not include the model, and only a subset of all settings.
  10. Do you have multiple displays?
  11. Odd. Works for me without "Union Overlapping Volumes" checked.
  12. Yes? No? I don't know? Can you elaborate the question? Sure, it is possible to print with 2 AA printcores. Printing with 2 cores on the UM 3 will always reduce the available buildplate area though; due to the design of the printhead there are parts of the buildplate where each printcore just can't reach. The right printcore cannot print as far to the left as the left printcore, and viceversa.
  13. Waarschijnlijk is het in jullie geval handiger om "projecten" te delen in plaats van profielen. Als je een bestand opslaat als 3MF vanuit Cura (Bestand -> Opslaan), dan worden daarin ook *alle* settings opgeslagen.
  14. There is no separate review process. It looks like your plugin is only marked to be compatible with Cura SDK version 7.2.0, and the Web Marketplace currently shows plugins that are compatible with Cura SDK version 7.0.0, instead of showing plugins that are compatible with 7.0.0, 7.1.0 and 7.2.0 (because all these plugins work with the current version of Cura).
  15. Strange; the "rainbow ring" about the specular highlight specifically points to light being refracted by water. https://en.wikipedia.org/wiki/22°_halo or https://en.wikipedia.org/wiki/Corona_(optical_phenomenon) (OMG, your printer has Corona!) Have you ever used any spray for buildplate adhesion?
  16. Looks familiar. Have you tried clearing the shadercache? In ~/.cache folder, there's a cache called: 'qtshadercache'. See https://github.com/Ultimaker/Cura/issues/5296
  17. Looks like the lens is fogged. Could there be moisture in the camera assembly?
  18. Wouldn't that result in extremely long filenames? There are printers that refuse to load (or even display) gcode files with long names.
  19. Only tablets running Windows. Neither Android nor iOS are supported OSes for Cura.
  20. Great. However, since I am a community member, not an Ultimaker employee, I can not access the crash reports you sent so I don't know what went wrong.
  21. See Extensions -> Post processing -> Modify gcode. Then add a Pause at Height script.
  22. Please add a screenshot. What version of Cura on what OS with what GPU do you use?
  23. You could try with CuraSceneNode.setOutsideBuildArea(True), but as soon as you change the scene Cura will notice that the node is not actually outside the build area and "reenable" it.
  24. “Duplicate”, and then increasing the version is the correct way. The new version of the plugin will need to be approved again. Until it is approved and then published, the current version will remain in the Marketplace.
  25. Does it also happen with newer versions of Cura?
×
×
  • Create New...