Jump to content

ahoeben

Ambassador
  • Posts

    4,954
  • Joined

  • Last visited

  • Days Won

    341

Everything posted by ahoeben

  1. Ender printers are made by Creality. Scroll up a bit to the Creality category...
  2. I don't know enough about Proterface to properly answer that. But I though that Pronterface just sends the gcode file you select to the printer. So if you see it sending an M900 gcode command, then surely that would come from the gcode file?
  3. That's how it is supposed to work, yes. I am the creator of the Linear Advance plugin, but I don't have a 3d printer capable of linear advance myself, so I don't know how well it actually works. If it doesn't, see https://github.com/fieldOfView/Cura-LinearAdvanceSettingPlugin/issues
  4. Personally, I think this is bad advice. It will bog down the interface with lots of settings you will never use, especially if you are relatively new to Cura. Make the settings you use regularly visible by default, and use the "Search" on top of the Custom settings for the rest. And consider installing the Tabbed Settings plugin from the Marketplace if you want to "explore" settings, or if you often forget the name of a setting but know what you are looking for. See
  5. I'm still taking all the time I need. Thanks for the reminder though.
  6. The Custom FFF Printer doesn't have a nozzle size dropdown. Instead, you configure the nozzle size in Preferences -> Printers -> Machine Settings -> Extruder. It actually does give you more freedom than printers that have a dropdown for the nozzle size, since you can enter any size you want (instead of being limited to just a few).
  7. I have only skimmed the discussion in this thread, but you could try installing the "Startup Optimiser" plugin from the Marketplace. It adds a button to the "Your configuration seems to be corrupt." dialog that lets you disable just that broken Voron 2 configuration file, and leave the rest intact.
  8. For the benefit of people stumbling onto this thread via a search, this is the official word: https://support.ultimaker.com/s/article/000002968 Having said that, I've been told the issue has been solved on the backend.
  9. You are. Wrong, that is. "Uranium" is a framework that is used by Cura. For all intents and purposes, it is just about half of the source code of the Cura frontend. What you are looking for is "CuraEngine". An instance of the CuraEngine is normally started by the Cura frontend, but you can also start an instance of CuraEngine to talk to a port and then tell Cura not to start its own CuraEngine process. https://github.com/Ultimaker/CuraEngine/wiki/Building-CuraEngine-From-Source#5-connecting-to-cura I don´t know if the --external-backend trick works with remote computers, and it seems that you may need one CuraEngine process for each client that connects.
  10. Pro-tip: you can click the arrow-heads on the hoops to rotate by exactly 90 degrees in one click.
  11. In the configuration folder (see Help -> Show configuration folder...), go to plugins/CuraEngineTiledInfill/CuraEngineTiledInfill/tiles
  12. @Dustin, @MariMakes, an answer from Ultimaker that we could refer to would be nice. Update: there's this page explaining what is going on: https://support.ultimaker.com/s/article/000002968
  13. Apart from that plugin, there's also the option to turn off the prefix altogether in the General preferences inside Cura: "Add machine prefix to job name"
  14. You could try the "Sidebar GUI" plugin from the Marketplace. It extends the settings to the full height of the window (and moves some things around to make much more sense IMHO).
  15. You could try the Material Settings plugin from the Marketplace. It extends the Materials preferences page so you can add many more settings than the handful that is there without the plugin.
  16. Got it. I'll try to look into it today.
  17. I fully agree. Unfortunately I don't have any say in the Ultimaker backend, other than complain. I will do so, loudly, in the "Cura Community ~ Fire Side Chat" this afternoon. The best solution I can offer at this point is to temporarily log out in Cura, then install the plugin(s) via the Marketplace inside Cura. You don't have to be logged in for that. You can (optionally) log back in after installing the plugin(s). This is a much better solution than to go via github.
  18. It is possible to create a very simple ("stub") plugin that registers a postprocessing 'scripts' folder inside its package. Then you can distribute that plugin via the Marketplace. I don't know if the Ultimaker team would accept such plugins though. @Cuq's method is certainly more straightforward.
  19. I would rather focus on getting Cura (or my plugin) to work than on what Github does or doesn't do. Have you had time to check if the Materials page of the preferences works with the Material Settings plugin disabled?
  20. Yes please. I just checked and I cannot replicate the issue with version 3.6.2 of my plugin with version 5.6 of Cura, so it must be related to specific configurations.
  21. I find that unlikely. You just have to attach them in the github webinterface, not as attachments in email replies. In your log file, I see that you have installed the Material Settings plugin, of which I am the author. Since that plugin extensively patches the Materials page, it is a likely culprit for issues like this. Can you try disabling that plugin, restarting Cura, and see if that fixes the Materials preference page?
  22. I am a community contributor. I - and many others who can help you here - have no access to crash reports. In your log file, I see that you have installed the Material Settings plugin, of which I am the author. Since that plugin extensively patches the Materials page, it is a likely culprit for issues like this. Can you try disabling that plugin, restarting Cura, and see if that fixes the Materials preference page?
  23. We can't say much without logs. Cura.log can be found via Help -> Show configuration folder.
×
×
  • Create New...