Jump to content

nallath

Team UltiMaker
  • Posts

    4,499
  • Joined

  • Last visited

  • Days Won

    100

Everything posted by nallath

  1. Nice to hear that people are developing plugins! I assume you found these resources? https://github.com/Ultimaker/Uranium/wiki/Creating-plugins https://github.com/Ultimaker/Uranium/wiki/Backend-&-Plugin-structure https://github.com/Ultimaker/Uranium/wiki/Plugin-Types I just noticed not all of them are fully up to date, but they cover most of what you need to know. With regards to running it from source, you're best of running it from the 15.06 branch (as that is the release branch for 15.06, it only has bug fixes). On 1st of september we will go into feature freeze for 15.10 and release the open beta for that version. We did quite a few changes for 15.10 (re-worked the output device code for instance!), so you might want to wait a bit for that. If you have any specific questions, don't hesitate to ask. If you tag me in a post It's pretty much guaranteed that I read it.
  2. Odd. Now the notification did bring me to the right page. *Edit*; and no notification from my own post and it cleared correctly. Hmm.
  3. Huzzah! Edit: This post gave me a notification, when I clicked it brought me to the first page of this topic. Marking it as read seems to have no effect. Deleting all notifcations does clear them.
  4. I'm on 39.0 on Ubuntu and I don't see it either.
  5. Release date I can give you; 1 september open beta for 15.10
  6. I'm not a 3D model designer, so I can't help you with this.
  7. It's not there yet. At least, not in an easy to use way.
  8. Cura has no such feature. It only has very limited uses cases and makes the workflow much more complicated / confusing. With a little bit of g-code tweaking you could implement this yourself (Do a certain move before you start and reset the zero position). If you want to make that automatic and know a bit of code, you could use https://github.com/nallath/PostProcessingPlugin
  9. Your model is wrong. It's not cura doing this to you, it's blender / 3ds max doing this to you. Try viewing the model in cura 15.04 in x-ray mode. If there are red areas, the model is wrong (we haven't ported that mode to the new cura yet, it's a WIP). Take a look at this excellent writeup about non-manifold meshes; http://blender.stackexchange.com/questions/7910/what-is-non-manifold-geometry
  10. If you have issues, please post them on github using the following guide https://github.com/Ultimaker/Cura#logging-issues
  11. There is even a guide (and an awesome generator made by quillford) which can be found here; https://github.com/Ultimaker/Cura#making-profiles-for-other-printers
  12. Yellow does not mean that you can't do it, it simply tells you; "Well, yeah, you could do it, but unless you know what you are doing it will probably go wrong"
  13. If it wasn't in the change log, don't be suprised it's not in the version But as you can see in the github issue, awhiemstra already fixed this, which means it should be in the 15.10 release.
  14. https://github.com/nallath/PostProcessingPlugin
  15. Cura opent de file correct, sketchup slaat deze niet goed op. Bekijk het object eens in x-ray view. Als er rode gebieden zijn zitten er fouten in je model.
  16. There is no way to automatically convert the slic3r settings to Cura. Most of them will not have an exact match or are splitted / merged into other values. I assume that we even use some different units at certain places aswell.
  17. @GauK I've not heard from you. Did you recieve my message?
  18. The supports generated by the old cura are pretty good if you use lines. The grid support is horrible to remove.
  19. It would make a ton of sense if we did that, but the engine structure just doesn't support it. At some point in the future we will probably refactor the entire structure of the engine.
  20. Oh wow, what a blatant rip of the Ultimaker design. Guess they didn't read the non-commercial CC licence.
  21. We're thinking about giving extentions some space on the main screen (instead of just giving it popups). The main reason that i've not implemented that for this plugin yet is that it would not be usable with 15.06.
  22. You don't have to use the new version. You are free to use the old versions. That's why they are still (and will remain) online. As i've mentioned in a ton of other topics aswell is that the auto slice does not effect the speed; The slicing process is started at the lowest possible priority. This means that your operating system should let every other process get more resources (the GUI included). If the process does slow down, it's a bug in the gui that seems to have something to do with auto slicing or your operating system not adhering to it's own standards. Disabling the auto slicing only treats the symptoms, not the actual problem. Also, someone changed Cura to not have auto slicing. So if you want it, it's there. The new Cura is superior in quite a lot of fields, but most of these need time to be fully noticeable. The amount of contributions has for instance already risen as it has a better architecture and is easier to maintain. There are also a ton of improvements to the engine in how things are handled. The problem that the new Cura does have is maturity. It has not been 'out in the wild' long enough to have all the bugs removed from them. Getting to a polished state just needs time.
  23. If all goes well, there will be an option to change it. The argument that you are an ordinary user is exactly why you should not even be touching the nozzle size in the first place. The machine profile should match the machine that you have and should not be changed.
  24. That's because it's hidden by default because it's a machine setting.
  25. The wire printing is very experimental. Bagelorb is the engineer that made it, he should be able to give some pointers, but i'm not sure if he's on the forum. If you create an issue on the CuraEngine repo he should be able to help you.
×
×
  • Create New...