Jump to content
Ultimaker Community of 3D Printing Experts

nallath

Team Ultimaker
  • Content Count

    3,652
  • Joined

  • Last visited

  • Days Won

    53

nallath last won the day on November 7

nallath had the most liked content!

Community Reputation

826 Excellent

1 Follower

Personal Information

Recent Profile Visitors

17,634 profile views
  1. If it's a full custom printer, it's probably better to start with the custom fff printer.
  2. If you change no settings at all it will print most of the holes Also, is there a specific reason that you set the build plate of the S5 to be so small?
  3. If it's an extruder one it has the "position" metadata. This is also what Cura uses internally (https://github.com/Ultimaker/Cura/blob/69dc54b76334dfe2d08c8f68bcc321a46a3e8800/cura/Settings/CuraContainerRegistry.py#L734-L753) to check if a profile is a global one or an extruder profile
  4. Are you using a 1.75 mm filament printer? If so, there are no 1.75mm filaments in the marketplace.
  5. You can remove the keys from the preferences by hand if you want to.
  6. I don't see anything that really pops up from the logs. Could you create an issue on github and also share your configuration folder?
  7. Could you share the log files? I think it might have something to do with rights.
  8. https://github.com/Ultimaker/Cura/wiki/Profiles-&-Settings
  9. In the case of layer_height, which is a global setting, you need to do it like this: Application.getInstance().getGlobalContainerStack().getProperty("layer_height", "value")
  10. There are too many things that could cause this. Some machines have a lot of issues with the network/octoprint plugin, but we still haven't been able to find out why. We've also gotten reports of slowdowns for other people, but without more information, there is little we can do.
  11. I think one of @ahoeben's plugins also adds an extra setting to the setting list. I'm not sure what trick he uses for that.
  12. I've explained what is going on in another topic: https://community.ultimaker.com/topic/34828-cura-48-and-macos-big-sur —-unable-to-show-preview/?do=findComment&comment=276588
  13. The lack of a playback button is caused by Cura reverting to legacy openGL mode. This is either done because a preference forces it back to legacy mode (this is done from within cura, check preferences) or because your drivers tell Cura that opengl 4.1 isn't supported.
  14. Please report issues on github and fill out the bug template.
  15. For the nex time; please provide logs. Just stating that something doesn't work isn't enough for us to debug it.
×
×
  • Create New...