Jump to content

ahoeben

Ambassador
  • Posts

    4,954
  • Joined

  • Last visited

  • Days Won

    341

Everything posted by ahoeben

  1. If you are interested in a version of this plugin for Cura 3.6, please help test this prerelease: http://files.fieldofview.com/cura/PrepareStageCompactor-v5-2018-10-29T14_11_04Z.curapackage
  2. Note that Cura *only* adds its own preheating before the start g-code if it does not see {material_print_temperature} or {material_print_temperature_layer_0} in your start g-code snippet. If you use those strings instead of hardcoding a value, Cura will not have to add its own preheat sequence.
  3. Could you test if this version of the plugin still exhibits the leak when you configure it not to display the camera image? http://files.fieldofview.com/cura/OctoPrintPlugin-v5.0.0-2018-11-14T21_29_30Z.curapackage Just drop the downloaded file into a running Cura window, and restart Cura. I don't think this version will fix the memory leak (though it might), but it will help diagnose where/what is leaking. Version 3.5.2 of the plugin (which I think you have installed) has a bug that even when not displaying the image, it is still being streamed and interpreted (oops).
  4. Have you tried turning the printer off and on again?
  5. There is no start gcode for Ultimaker 2 flavor, since the start sequence is handled by the printer.
  6. The indicator should be seen as a “front-left indicator” instead of an origin (except for delta machines, which normally are the only machines that have the origin at the center). Don’t pay too much attention to it, since it doesn’t “do” anything except indication the front-left.
  7. If you want to run Cura 3.6 with a “clean” configuration folder that is not upgraded from a previous version, do the following: * run Cura 3.6 * go to Help -> Show configuration folder * close Cura * remove all files from the configuration folder, but leave the empty 3.6 folder in place. * restart Cura When Cura cannot find the folder with the correct version name, it will make a copy of the latest configuration and upgrade that (all the way down to legacy Cura if that is all that can be found). When it gets the empty folder though, it starts a new configuration.
  8. I was wrong about this. Cura does not crash while closing, but it does not clean up after itself properly. I made a fix for that here: https://github.com/Ultimaker/Uranium/pull/423 I think in previous versions (before 3.5), the GUI framework cleaned up the tray icon. In 3.5 that GUI framework was updated and apparently it doesn't clean up after Cura anymore. The patch above (which would have to be included in a new version of Cura) does the cleaning up when closing Cura.
  9. That's the wrong folder. You need C:\Users\Jon\AppData\Roaming\cura Create an "archive"/zip of that folder, and upload it here or use a service like wetransfer.com or dropbox and post a link to the zip here.
  10. Check the configuration of the other extruder.
  11. I think a material with a 2.85 mm diameter got selected during an upgrade. Does the materials dropdown Show Ultimaker materials? Could you try reselecting generic PLA?
  12. You can move the support cube down a bit.
  13. You can also use per model settings, and either cut up your model beforehand and reassemble them in Cura, or by using the Mesh Type dropdown you can use a mesh as a modifier mesh. Caveat: you cant change the layer height in this way.
  14. The mesh needs to have uv coordinates. The STL format does not support those, so you need to use OBJ. The OBJ file also needs to include normals, or the UV coordinates get ignored (if I remember correctly)
  15. It seems to be your Intel graphics driver crashing. Have you checked if an updated is available from Intel?
  16. Note that nothing in the profile (or "printer definition") currently affects how Cura interfaces with printers. IE: nothing you can currently add to a printer definition can change if a printer is detected over USB. The issue that some printers are not detected in Cura can only be fixed in the code of Cura.
  17. You are in "Layer view", but the model has not yet been sliced. Press the "Prepare" button in the lower right corner. Alternatively, you can go to the General preferences, and enable Automatic slicing.
  18. The memory issue that I reproduced is fixed, in both 3.5 and 3.6 (the new version of the OctoPrint plugin is compatible with both). But there could be another (or a new) leak that I don’t yet know about, so please test and let me know.
  19. Marketplace should have an updated OctoPrint plugin.
  20. I think in this particular case, the new minor release was pushed forward a bit to get the support for CC cores out.
  21. Once a branch is made for a minor version (3.x), no new feature is allowed in that branch; in revision releaes (3.5.x) only fixes are allowed. The new beta contains new features, so a new minor version is needed.
  22. Note that these orphaned tray icons by themselves are very much harmless. Yes, the not exiting cleanly part may be indicative of something else also not being cleaned up properly, but don't focus too much on the tray icons.
  23. A more proper description would be that Cura does not close cleanly, leaving behind systray icons when you quit Cura (if I understand you correctly). The "silent crash" name was just me trying to separate this from a "memory leak", which this is not. What seems to be happening is that Cura exits ("crashes") before cleaning up the tray icon, without showing an error message ("silently")
  24. And a few old things that are new: * a memory leak in Cura Connect and OctoPrint was fixed. Note that the Toolbox contains a new OctoPrint plugin that works in both 3.5 and 3.6 which includes the fix. * a couple of issues related to USB printing are fixed (temperature updating during heatup sequence, and extraneous "Press to resume" messages during printing with Marlin 1.1.8+
  25. 123d catch used “the cloud” for computation, and the servers have bee shut down 1.5 years ago. Even if you still have the software, it will not work.
×
×
  • Create New...