Jump to content

nallath

Team UltiMaker
  • Posts

    4,499
  • Joined

  • Last visited

  • Days Won

    99

Everything posted by nallath

  1. Its the only reason why there still is a usb port on the UM2. So the firmware updating should work.
  2. Could you check the start / end g-code of the generated file?
  3. Daid actually coded fairly little of the latest release I will post the issue on github for you, as it's a feature request and not a bug.
  4. Could you post this on the github? All feature requests / issues / bugs /etc should be posted there, so we can keep track of it. We should make it clearer that the object scales in this case to prevent confusion.
  5. Officially the USB connectivity is not supported. This is why we haven't spent a lot of time on polishing is. The drivers should work, so could you tell me what the problem is with those?
  6. Could you make a github issue about this (or check if there already is one)? This helps keeping track of issues.
  7. The UMO wants settings such as temperature in the g-code. The UM2 wants this set on the machine. If the um2 sees a temperature setting in the g-code it will give this warning.
  8. That makes it a lot clearer. I've redone some of the layer view stuff, so it could be that i've already fixed this. Also; the layerview not showing in the start is correct; The progress bar in the bottom shows that it's still calculating the view, but it could be clearer.
  9. Yup, thats why we won't promise that it will be there.
  10. Well, those things are better left for private messages
  11. Not even that, as you get the umbrella without buying the suit in the first place (although it does match your suit better if it's an Ultimaker )
  12. Daid did work on this and he does most of his dev work on windows.
  13. @ahoeben; All right, we will keep it in mind for the upcoming GUI changes.
  14. Like I said, fair enough; What would you suggest? It's easy enough to change.
  15. This is one of the most promising options, but we won't make any promises about it until we've tested it.
  16. Allright, had a meeting with the rest of the team. We are going to make readability changes for the next version. We're looking at several different options and we've included your suggestions to the options.
  17. Yeah, sorry about that dependency. We found a critical bug in pyqt 5.2, so we could not use it. The guys of qt were fairly quick with fixing it, but it did result in the 5.4 dependency.
  18. Well, actually. Not if you use a non-um printer. Seeing that UM put tons of money in the development, a bit of branding isn't that weird. We could look at the placement though. Any ideas where else to put it?
  19. I'm going to discuss this with the Cura team. Thanks for putting in the effort.
  20. We are dependent on the community for print profiles. So far we recieved a few, which have been added to Cura.
  21. Version 15.06.02, containing a ton of fixes is online on http://software.ultimaker.com/Cura_closed_beta/15.06/. Depending on your feedback, this will also be released officially. Let us know if the reported issues are fixed (provided they were marked as fixed by us on the github).
  22. I've posted this in another topic, but now it actually works as intended. The plugin ads a menu item to top menu for calculating the price of a print. Just like the old Cura it uses density and price per KG to calculate the cost of a print. Simply download it from https://github.com/nallath/PrintCostCalculator and put the folder in the plugin folder. Cura should automatically load the plugin upon startup.
  23. I've added it to the repo.
  24. Means that your end switches aren't working. Combined with your other problems it probably means your main board is broken.
×
×
  • Create New...