Jump to content

Msuurmond

Dormant
  • Posts

    192
  • Joined

  • Last visited

Everything posted by Msuurmond

  1. The developer of the Autodesk-plugin has to update the plugin to be compatible with Cura 4.0
  2. You can find the location on where the logs are here: https://github.com/Ultimaker/Cura/wiki/Cura-Preferences-and-Settings-Locations
  3. OpenGL support depends on your videocard drivers. You can check the logs to see what OpenGL version Cura detects on your system.
  4. Is it possible for you to share your settings folder with us? Than we can try to recreate your scenario on our computers and maybe fix it.
  5. This is fixed in the 3.6.0 stable that will be released today. If you connect your S5 through your network, Cura will sync the materialprofiles in the background when connected to that printer (printer needs to have firmware 5.1+) After that you can select it on your printer. (The CPE+ trick should also result in good prints)
  6. @kmanstudios I have asked the Cura team to investigate your issues. When a newer version of Cura doesn't find a settings directory for its version and finds an old settings directory, it will copy it and then convert it (when needed). So what you would need to do is to move your settings directory, start Cura 3.6.0-BETA, close it. And then copy back the settings of the Cura versions you still want to run. The settings can be found in (Windows) /Users/[username]/AppData/Roaming/cura
  7. I noticed on my windows 10 machine that when I startup and close Cura rapidly a few times, the notification icon indeed is multiplied. When I hover with my mouse over these icons they a removed until the last one (that actually is the Cura that is running). Do the notification icons also disappear when you move your mouse over them? Memory usage is 220MB here, it increases when loading a model, but doesn't grow when I'm not doing anything. Is it possible for you to start 3.6-BETA without your old configuration? How big is your settings folder? C:\Users\[user]\AppData\Roaming\cura
  8. Having multiple installed should not be a problem. Does it also get slower if the memory usage grows?
  9. Do you run mutliple Cura's at the same time? What plugins do you have installed?
  10. The memory leak will be fixed in Cura 3.6. Are the 'silent crashes' a result from the memory leak?
  11. On MacOS Mojave with Cura 3.5.1 Cura uses around 300Mb of memory and is stable. Switching Prepare <-> Monitor doesn't change this allocation. No network connected printer available here tho.
  12. Check this for a workaround untill Cura 3.6 is released: https://github.com/Ultimaker/Cura/issues/4575
  13. This is model specific right? You can change the 'Support Floor pattern' to 'lines' and then in should work ok.
  14. This fix had too much of an impact to be included into 3.5.1 It will be fixed in Cura 3.6
  15. We are still looking into this, MacOS 10.9 is 4 years old. We rely heavily on Qt and version 5.8 is out of support starting this year. 5.8 is the last version that supports MacOS 10.9 You can still keep on using Cura 3.4.1 as a current 'workaround'.
  16. We will update the Setting Plugin this week, lot of the pictures in it are not compatible with the dark theme.
  17. The remarks here don't do justice to all the hard work the Cura team and system testing is putting into making sure every release is more stable than the previous one. It is certainly not the case that we don't test stuff and 'just put it out there'. We followed the same development and testing process for 3.5.0 as we did for all previous 3.*.* releases. With an expanding automated test I would even argue we tested 3.5.0 better than the previous releases. During the 3.5.0-BETA we got very little bug reports so we assumed 3.5.0 was ready to be released. From our point of view 3.5.0-BETA was ready to be released to the public. When looking into the crash reports, we see that two bugs (crash in the Lockfile and a TypeError when searching for containers) contribute for 88% of the crashes we see. Without these two we would have a a new record low of startup crashes. Of course we want to reach 0, but we have to do this in steps. We are finishing up 3.5.1 and think all major bugs are fixed but of course it is difficult to determine if it is fixed when we can 't reproduce it, we haven't seen these two bugs at any system here at Ultimaker.
  18. So even with a deletion of /Users/[username]/Library/Application Support/cura and a reinstall of Cura 3.5.1-BETA it is still slow?
  19. We are work hard on a bug fix release. Please try and give us some feedback: https://drive.google.com/drive/folders/0B5IvTu1iM1pNMnE5YnlwZUlRSUE?usp=sharing
  20. Awesome, nice work! - Yes you can use the Cura icon. - You don't need a developers license only a license for your plugin (e.g. LGPL) - We would really like to add this to the ToolBox: https://github.com/Ultimaker/Cura/wiki/Plugin-Directory
  21. And have you tried Cura 3.4.0?
  22. Could you check your log-files to see if there are lines that indicate upgrading has gone wrong?
×
×
  • Create New...