Jump to content

ctbeke

Team Ultimaker & Admin
  • Content Count

    214
  • Joined

  • Days Won

    1

Everything posted by ctbeke

  1. We're waiting for the author of the solidworks plugin to make an update that is compatible with 3.5. Once that's done, it'll be available for update through the toolbox.
  2. I see several errors: serial.serialutil.SerialException: could not open port 'COM5': PermissionError(13, 'Access is denied.', None, 5) cura.Machines.MaterialManager.__addMaterialMetadataIntoLookupTree [255]: Material custom_material_cartesio_0.4_mm contains a variant 0.4 mm that does not exist. It will not be added into the material lookup tree. UM.VersionUpgradeManager._getUpgradeTasks [278]: Config file [.\Monoprice+Select+Mini+V2+%28E3D%29_user.inst.cfg] is of version [4000005], which is different from the defined version [2000000], no upgrade task for it from type [user]. I've forwarded it to the developers as well (I'm currently not working on Cura).
  3. Can you share the logs? Cura is supposed to upgrade your old configs to the new version, so something must have gone wrong in that process.
  4. You can try a 'Cura Connect reset' which is available via the printer's settings menu.
  5. This has since been solved on the master branch and will make it's way into the next release of Cura.
  6. Luckily it's a plugin, so it can easily be updated by the plugin author (indeed some Cura team members in this case) and distributed through the Toolbox!
  7. That's awesome. Would be nice if those mesh fixing options are available on the context menu when you right-click on the model itself.
  8. Yes, there is an internal system to escalate tickets from 1st to 2nd to 3rd (developers) line support. Anything duplicated gets filtered out before it reaches the devs (to not 'waste' their time). Sometimes resellers can actually provide information on a (temporary) fix as well. So if you want fast support, always contact your reseller.
  9. All 1st line support is done via our resellers. Any support you receive from Ultimaker employees on this forum is purely because they happen to spend time on here, but it's not an official support channel (hence 'community' forum). As @Dim3nsioneer indicates it has been fixed and the next UM3 firmware release will have this fix and much more. Bringing out firmware updates just takes a while as we need to test a LOT before we put something out on everyone's printer.
  10. Hi all, For everyone using the Cura backups plugin, I have an announcement to share: Later today, we will switch the location of the Ultimaker account and authentication service, meaning that the URL that the plugin is currently using will not work anymore. An update of the plugin is available in Cura's toolbox that fixes this. Unfortunately we were not able to migrate without this breaking change. On the other hand, the new account portal gives improved UI/UX, security updates and better integration with the create account and forgot password functionalities. If you have any questions or something is not working for you, please leave a comment below. Thanks! Chris
  11. Thanks for your input! Point 1 will be addressed when we make another iteration on the backup functionality (soon-ish). Point 2 is something that is currently in progress (not sure about the full scope of it though).
  12. There's an option in PyCharm's build settigns called "emulate terminal in output console". You'll need that one enabled to see QML logging.
  13. There is a relatively new setting called "slicing tolerance", maybe you could give that a try? It's in the experimental category. There's also some details about it in this post: https://ultimaker.com/en/blog/52266-whats-new-in-ultimaker-cura-31.
  14. The updated plugin is now in the Toolbox (v1.0.5). The above mentioned issues should be solved by updating to this version. Let me know!
  15. Ultimaker doesn't release the PPA version, only AppImage (as that works on all Linux distro's, and the Linux user group is very small compared to Windows and MacOS, less then 1%).
  16. ctbeke

    Plugins API

    https://github.com/Ultimaker/Cura/wiki/Plugin-Directory would be a good starting point.
  17. There is no Cura 3.5 from Ultimaker... The latest stable version is 3.4.1. Maybe the version number is causing these plugins to fail loading?
  18. I actually got around to is this morning and published an update. You can find the details here: https://github.com/Ultimaker/CuraDrivePlugin/releases/tag/v1.0.5. It should be in the Toolbox somewhere today. You can also download the .curapackage manually from the link above and drad&drop it into Cura.
  19. Thanks for that info. I'll try to make some time this week to release an update of the plugin that properly supports the dark theme.
  20. It should be under %APPDATA%\cura\<Cura version>\cura.log or C:\Users\\<your username>\AppData\Roaming\cura\<Cura version>\cura.log. Now that I think of it, this might have to do with the dark theme you're using? Try switching to the normal theme and see if that gives you correct fonts? If that's the case, I'll prepare an update of the plugin that fixes the UI for dark theme.
  21. Can you share the cura.log file so we can see why the text isn't properly rendering on your system? An overview of you system specs would also help (like graphics card, drivers, etc).
  22. Wow, that seems like a lot of rendering issues. Unfortunately that's hard to fix because that's all in Qt, we're just using their UI components that should work otherwise. Which OS are you running?
  23. An upcoming version of the toolbox will allow plugin authors to publish this themselves ?
  24. Probably a custom configuration file (as it's not shipped in Cura)? It might be that the version number in that file needs to be updated then.
  25. Ultimaker's core team does not add these, the community or machine manufacturer does (or not if they're not interested). Please contact Creality or ask the community for better support on this.
×
×
  • Create New...

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!