Jump to content

ahoeben

Ambassador
  • Content Count

    2,105
  • Joined

  • Last visited

  • Days Won

    54

Everything posted by ahoeben

  1. Go to %APPDATA%/cura/4.0 and remove cura.cfg
  2. No, sorry, I don't. I know the camera can do 1600x1200 because when the UM3 was being developed I working for Ultimaker. Back then I was involved in getting the stream visible in Cura. But I know very little about the firmware (or the exact hardware, actually). Edit: I would not be terribly surprised if the camera were at least very similar to this one (since the linux board it interfaces with is an Olimex A20): https://www.olimex.com/Products/Components/Camera/CAM-GT2005/
  3. How many screens do you have? There’s a known issue on some combinations of gpus and multiple monitors.
  4. This is often done using a plugin in OctoPrint named OctoLapse.
  5. You need to do libArcus before CuraEngine, because CuraEngine requires libArcus (right?).
  6. Couldn't you do that with a postprocessing script though? Duplicate each layer, adjust the extrusion.
  7. It depends what you want to change. If it is all frontend stuff, you might be able to just edit python files in the released version.
  8. I’ll just quote myself, from a couple of replies above this: Also note:
  9. Liked for the thread title
  10. Bugs happen in Cura. I don't think you really want automatic updates. Sometimes you want to hold back on an update. Having said that, you can extract the files from the Windows installer with just about any archiving application (eg 7zip), and run Cura.exe from there without installing it to Program Files. That should make it possible to use a newer version without bothering asking your IT department for support.
  11. Note that a new version of the plugin, which singles out Ultimaker 3 and S5 printers, is now available in the Marketplace. This fixes this issue, specifically for these printers.
  12. If @ahoeben did not do this (to *some* of his plugins), every user upgrading from Cura 4.0 to Cura 4.1 with the OctoPrint Connection plugin installed would have been greeted with a crash dialog with the option to kill all their settings, because once again this SDK update was messed up like it has been many times in the past. Please don't suggest that I do this "out of a personal decision". Time and time again this has proven to be a necessity.
  13. A prerelease version of the OctoPrint Plugin for Cura 4.1 can be dowloaded here: http://files.fieldofview.com/cura/OctoPrintPlugin-v6.1.0-2019-05-16T10_29_36Z.curapackage Please drop the downloaded file into a running Cura application window, and restart Cura. Unless issues are reported with this version of the plugin, it should be available as an update on the Marketplace soon.
  14. Between the Settings and the Preferences menu. In the same menubar as File, Edit and View.
  15. I think this would have been better suited at the OctoPrint forum (as I said in my email). This needs to be solved at the OctoPrint end first. There is currently no way to link a gcode file to a user in OctoPrint, or to add other metadata to the gcode file. If that were possible, the OctoPrint Connection plugin would be able to send this data. Currently there is nothing on the receiving end (OctoPrint) that would register this additional data, so there is no use sending it.
  16. The gpu in the first laptop does not support the required functionality for the normal layerview, so it falls back to the compatibility mode. The gpu in the second laptop should support the required functionality. There are two possibilities why it does not work: * You may have changed the preference on the General pane of the preference to force the compatibility mode * The driver you have installed on the laptop may disable OpenGL 4.1
  17. I can tell you how the barbarian plugin works, but other plugins work differently. Some plugins (like the Barbarian plugin) add an entry in the Extensions menu. The Barbarian plugin adds a menu item "Extensions -> Barbarian plugin -> Convert to metric". You select an object that was imported in inches and use that menu option to scale it up. Note that this thread is specifically about the list of plugins listed in the opening post, for the beta of Cura 4.0. Your post would have been more appropriate as its own thread.
  18. That's because your layerview is in compatibility mode. This happens because of two reasons; You either selected this in preferences or your graphics card doesn't support opengl 4.1. Note that in the first screenshot, the Sidebar GUI plugin is used to rearrange the UI. This made the vertical slider move to the left of the settings.
  19. Not before a Cura 4.1 beta is available.
  20. The article you link to is for multi-extrusion printers. On single extruder printers like yours, you have to "manually" insert material change gcode with postprocessing scripts. The article does include how to "merge" your models after importing. I'm not familiar enough with Blender or Fusion 360 to tell you how to export multiple objects with the same origin.
  21. It has been reported by another user here: https://github.com/fieldOfView/Cura-SidebarGUIPlugin/issues/2 I have yet to look in to the issue. Does it also happen when you don't switch to the monitor tab? How do you connect to the printer? USB, OctoPrint, Cura Connect?
  22. Sounds like it has the wrong firmware. The Ultimaker 2+ has an additional gear in the extruder, which means that the extruder needs to be inversed. If you have an Ultimaker 2+ (or upgraded Ultimaker 2) with Ultimaker 2 firmware, or vice versa (an Ultimaker 2 with Ultimaker 2+ firmware), the extrusion will be inversed.
  23. You can open a gcode file to inspect it, but you can not change parameters and reslice it. This is because the original information of the 3d models is missing in the gcode files.
  24. That’s pretty much what my therapist told me.
×
×
  • 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!