Jump to content

ahoeben

Ambassador
  • Posts

    5,025
  • Joined

  • Last visited

  • Days Won

    359

Everything posted by ahoeben

  1. Well spotted. I'm guessing they shot the video with a pre-production model, which has a panel that predates the new logo. No logo on the side-panels though. I might start a side-business selling Ultibot stickers to put on there.
  2. Have you tried copying over the entire C:\user\xxxx\appdata\roaming\cura\5.2 folder? That should get you the whole configuration you had on the old installation.
  3. Hey @pegasus, welcome (back?) to the Ultimaker forum. It really does not help you much if you add your problem to a two-year-old and mostly unrelated thread, without adding much detail about your problem. It sounds like you can run the installer just fine, but Cura is crashing when you try to run it after installing it. Is that correct? In that case, we need to see the logs that Cura creates, or we don't know what is going wrong either. Here are instructions on where to find those logs: https://support.makerbot.com/s/article/1667337559413
  4. You would have to create and use a .def.json printer definition for your printer, instead of using the "Custom FFF Printer". The Custom FFF Printer definition does not have an STL, so there is nothing to replace.
  5. Correct. The minimum OpenGL version for full functionality is OpenGL 4.1
  6. Hi, and welcome to the forum @pachan. This forum has an entire german subsection here:https://community.ultimaker.com/forum/124-deutsch/ I would advice you to start a new thread there, instead of hitching on to a mostly unrelated other topic.
  7. According to https://www.techpowerup.com/gpu-specs/nvs-300.c1452, that GPU supports up to OpenGL 3.3. So if you want the full functionality, you will have to get a newer GPU.
  8. Not for Cura itself. Cura itself does not use the registry at all. There's a registry entry for the uninstaller, and some (optional) packages that get installed with Cura, such as the Microsoft Visual C++ runtime, and the "Arduino" serial port driver for USB printing probably have some registry entries. You can open the installer in a zip application (eg 7zip), extract the files from there and run Cura without installing the runtime and driver. That way the registry is not touched.
  9. The "add network printer" is (effectively) for Ultimaker printers only. Though just about any printer that has a USB port can be controlled with the same "protocol", just about all printer manufacturers came up with their own protocol to communicate via the network. Cura only knows about the Ultimaker network printing protocol. There are some plugins that add other network printing protocols (eg via OctoPrint, Moonraker/Klipper, Creality Cloud), but even those generally don't integrate with the "add network printer" UI but have you connect Cura to the network printer in some other way.
  10. I think this is the most up to date information: https://support.makerbot.com/s/article/1667337565436
  11. It could mean that the driver for your GPU is not properly installed. But you could also try to use Cura 4.13.1 instead of the 5.x releases. There seems to be an issue between Cura 5.x and some GPUs. https://github.com/Ultimaker/Cura/releases/4.13.1
  12. Er... no. All versions of Cura since Cura 2.1 (or actually since Cura 15.06) have required OpenGL 2.0 as a minimum. Cura 5 should still work with OpenGL 2.0.
  13. You seem to be having a problem with your Creality Ender hardware. Note that this is a forum for Ultimaker printers and Ultimaker software. Because Ultimaker Cura is also used by users of 3rd party printers, there are some people on this forum that are familiar with your printer, and may have some ideas, but I think you could get much better support if you contacted Creality, or asked in a dedicated Creality user forum.
  14. The short and realistic answer is "no". Not without a rethinking how slicing works and rebuilding most of CuraEngine. Using the GPU is not just a switch a programmer can turn on. A GPU is good at foing specific types of things in specific ways. GPUs are good at doing relatively simple things in parallel. In order to use the GPU you need to be able to divide a task into many of the same "subtasks" that can be executed at the same time without affecting eachother. In slicing most tasks need to be done sequentially. The toolpath that needs to be created on one layer depends on the result of slicing the previous layer.
  15. Sorry, I really can't help you if all the feedback I get from a suggestion is "that did not work". What did not work? Did you not find the dialogs, or were their contents different? Did you not find Ultimaker Cura in the list of applications? Or did you successfully perform all the steps to set the "Graphics preference" of Ultimaker Cura to "High Performance", but it did not change the behavior inside Cura? Did you restart Cura and/or your computer after setting the preference? See, there are a lot of details you could be giving to help us help you. I'm going to stop guessing, until I get more details.
  16. If you don't want others to walk away with your ideas, I would discuss them in the open. That way you have prove that it was your idea in the first place. If you talk directly with devs, how are you going to prove that you had that conversation? A place that is more neutral, and more focused on open source is for example https://reddit.com/r/reprap Having said that, having an idea is infinitely more easy than making it happen. A lot of work needs to be done to make your idea come true, and your idea is probably going to be a small part of a final product that you can use. Chances are someone will have had your gamechanger idea already, but decided it was infeasible to implement it. You "own" your thoughts, but the fact that you have an idea does not mean you are the only owner of thoughts to that idea.
  17. Yes Not so much for slicing, but for displaying the model and previewing the toolpath.
  18. Yes, but you will have to use the local IP address of your printer, instead of the VPN IP address of the printer.
  19. What did you do or try? I don't have Windows 11 installed, so I can't check, but this should do it:
  20. Are you running Cura on a computer that has multiple GPUs? Eg an integrated intel GPU and the nVidia GPU? In that case it could be that (in Windows 11), Cura is running on the integrated GPU. Try if you can force Cura to open on the dedicated NVidia GPU instead.
  21. It depends a bit on the printer you have (and how you have added it to Cura), but most commonly the setting can be found in Preferences -> Printers -> Machine Settings -> Extruder 1
  22. Check if the driver for your GPU was correctly installed and if there's an updated driver from your GPU manufacturer.
  23. I believe Cura takes care of that (or at least it tries to). When you select the "metal" filament, your build volume in Cura will shrink. The model will actually be printed larger than it is shown in Cura, so it becomes the right size after sintering. At least, I think that is the theory.
  24. It would be my guess that the gcode file is not getting written to your sd card correctly. Try formatting the SD-card, and then try again. Having said that, Cura 15.04.6 is at least 7 years old. Old software sometimes stops working reliably. Maybe it is just time to update.
  25. There is a - somewhat elusive - issue with that plugin that is possibly related to Powertoys FancyZone. See fieldOfView/Cura-SidebarGUIPlugin#29 for more information. There's a good chance that this isn't the only issue at play here. Not everybody who is experiencing the problem has that plugin installed. And - fortunately - not everybody who has the plugin installed is experiencing the problem. It could be that the QML trickery that the plugin is doing simply exacerbates an underlying issue that is present in Cura itself or the lower level GUI framework that it uses (Qt).
×
×
  • Create New...