Jump to content

nallath

Team UltiMaker
  • Posts

    4,500
  • Joined

  • Last visited

  • Days Won

    100

Everything posted by nallath

  1. We don't support it at the moment. It might be a good idea to do so though.
  2. Ultimaker already has marlin on it (it's modified version though)
  3. In the old Cura you could ony define the size of your print had as a rectangle. In the new Cura you can define it to be any 2D polygon. The machine_head_with_fans_polygon defines the entire size of the head.
  4. If you can export point clouds, you could always use pointcloud viewer or meshlab.
  5. CuraEngine isn't uploading any data to the interwebs. It's sending data through a local socket to the front end. Your operating system might (incorrectly) see this as network traffic. The flow is as follows; 1. Cura frontend sends model data to the backend. 2. Backend does a bunch of slicing 3. Backend sends sliced polygons back for visualisation 4. Backend sends g-code back for saving. Every time you change a setting and wait a bit, this process is repeated. The anonymous print information is only sent when a file is written to disk / file sent to usb/ etc (so not every slice). At that point it only sends the values of your settings, your operating system, some info on your processor and a hash of the model. All of which are extremely small. The only data that we ever send to the interwebs is the print data and that is extremely little. Refreshing the ultimaker page will have a greater impact.
  6. Because the buildvolume object has no notion of there being multiple objects on the scene. I will add a issue to our tracker to remedy this. **edit** For our reference; CURA-2312
  7. We are working on setting temperature based on flow (higher flow -> higher temp). But it's a complicated problem. The "slowness" of the heater is not helping and the PID controller doesn't like it if it's target temp is changed all the time.
  8. You're printing one at a time. The distance from the nozzle tip to the axis is the max height at that point. Try changing the print sequence setting to all at once.
  9. You can't protect function through means of copyright. You can only protect form. If he took your design or was inspired by it and simply re-designed it, there is nothing you can do about it. The only way you could have prevented him from doing this is two fold; 1. Trademark; You can also get a trademark on a very specific look, as long as it's unique for a brand. Monique Dekkers (who designs underwear) won a court case over this at some point. 2. Patent; You have a novel (technical) solution for a problem. However, one could argue that in this case the solution is obvious, so a patent is not valid. Legally speaking see no fault here.
  10. Beta is not translated yet. Some places we still had old translations, which are shown.
  11. I have no issues with that. I would suggest that only "user" plugins are placed there (eg; Not plugins that are defaults, as we tend to update them). We would also need a way to handle conflicts (what happens if translate tool is put in plugins folder)
  12. The "deepest" setting is the correct one. If the deepest setting still has it's function (which tends to use the value of the parent), it's updated automatically. If you override it with a fixed value, changing the parent won't do anything for that setting. If all children of a setting are visible and overriden, the parent setting also becomes disabled to indicate that changing it does nothing.
  13. Enabling retraction doesn't save any time. I don't even think there are much retractions in this print. Changing the top/bottom does have a dramatic impact. Cura 2.1 uses wall speed of 40, outer /inner wall of 30 and top/bottom speed of 20. Setting those to 50 will improve print speed from 46 min to 24 min.
  14. It's not so much a matter of being interested, it's a matter of having to do a gazillion things that have higher priority and already too little time to do them.
  15. Changing it to 60 deg should work (just tested it and i get the overridden value). I do remember fixing something regarding this recently, so it could be that was after the beta release.
  16. Yep Machine settings plugin handle this. 2.3 final will have this. For USB printing it doesn't need to be a Ultimaker. The guys from Aleph objects (lulzbot) are also looking into fixing this for Cura. Because we don't have the right data yet. Fixed in 2.3 beta There are multiple infill patterns. Agreed, but it's not a simple feature. I'd love to get it in Cura, but we focused on speed & dual extrusion for the 2.3 release.
  17. Nope. Its a definition thing only. This is due to our profile stack, which works as follows; user->quality_changes->quality->material->variant->definition We first ask if the top (user) has the setting value. If not, we continue down. So if the quality sets a value (say fan speed) and material sets it as well, the one set by the quality is used. We still need to tweak what we put in what profile.
  18. Materials is still quite messed up. It's a know issue.
  19. You're right, but this is a beta. If you want stable software, don't get the beta
  20. It tries to load a profile that it can't find. By the look of it you also had 2.1 installed. We've found some issues with the 2.1 conversion scripts, so clearing your local files will already help quite a bit.
  21. The custom machine settings plugin doesn't support multi extrusion just yet. Sorry about that.
  22. If it starts with new machine assistant, it probably failed to load your old active printer, notices that you don't have an active printer so it tries to add one. Could you give me your .log files saved by Cura. There should be some errors there that show what is going wrong. For the rest, DaHai8 is right on all accounts
×
×
  • Create New...