Jump to content

Daid

Ambassador
  • Posts

    4,700
  • Joined

  • Last visited

  • Days Won

    19

Everything posted by Daid

  1. After installing freecad, can you do a "start->run->"cmd" in the big black screen run "SET", and report back all the output. Looks like freecad might be setting a global environment variable that's messing up Cura.
  2. If that would be the case I wouldn't be able to sit at my desk right now. Cura actually touches at little from the system as possible, as this makes it easier to go cross-platform.
  3. No bug, just a display difference to speed up the GCode rendering.
  4. TEST1 and TEST2 are the same except for the BFB profile and the Win8 drivers.
  5. You can still use older cura versions to print GCode files to use that feature.
  6. Check the package.sh script to see where Power is fetched from.
  7. Don't know if Octoprint provides an API. If it does, then this can be made. It's already done for the Doodle3D wifibox, which allows printing trough wifi with Cura.
  8. Latest test version should include working drivers: http://software.ultimaker.com/Cura_closed_beta/
  9. FYI, The expert settings dialog is on the chopping block ;-)
  10. If that is the case, then your motherboard producer is at fault. The USB specification specifically talks about protecting against this.
  11. I just noticed I forgot this one. Never spoke to anyone who was happy about their Creatr, spoke to a bunch of people who where unhappy about it. I feel kinda ashamed that they are dutch. http://3dprinter4u.nl/ on the other hand, is also dutch, currently do not provide their own software solution. But, are good people with a good machine. So, if you want to go dutch, but for some reason do not want to go Ultimaker, then go Builder instead of Lpfrg. (Even if the they have a pretty lame URL)
  12. The speed in Cura is in mm/s, the speed on the machine is a % on top of that. So, 50mm/s in Cura, with 90% in the machine, gives 45mm/s
  13. No. That's an unrelated issue, no idea what could be causing that...
  14. Yes, you have to add ;{profile_string} to the end code, or else it won't add it in that version. (The BFB firmware crashes on that line)
  15. TEST1 or TEST2 are equal, except for some of the BitsForBytes support code.
  16. Depends, 14.03 is fine, except for very high detailed models, then 14.03-TEST is a better option.
  17. Yes, but I'm swarmed with work right now...
  18. Looks like it. That's good, as that's the latest with all fixes for quality in it.
  19. There are 2 aspects of any printer. One is hardware. Other is software. As Ultimaker, we want quality for both. So our hardware is top of the line, getting high quality and speed. Software wise, it's awesome. And I'm not only saying that because I made the software. Cura is tailored to work perfectly with the Ultimaker. While still exposing all the knobs&dials under the hood if you want to get there to tweak things. It gets a ready stream of updates, and you can actually talk with me about possible improvements and stuff. Do not know it. But hardware wise looks like a straight up copy of the Makerbot Replicator 2X. Software wise, they just coped OpenSource ReplicatorG, which is old and dated compared to current standards. Most likely invested a tiny bit in software to get their printer support better. Also unknown to me. But hardware wise it looks like an Prusa i3. Nothing wrong with that, but the moving bed will impact quality a bit. Little other information available, most likely a 0.5mm nozzle instead of the 0.4 seen in higher end printers. Software wise they are using Repetier-Host. Works, but not the friendliest package for most users, as it has lots of advanced features exposed by default. Do not invest in software development. The big competitor. I cannot make a proper assessment on them as I would be biased. Software wise they are closed source now, and are not that keen on supporting their older products. And they just released new products. We got one of the newer Replicators at the office last week. Didn't start up, so we have to send it back. And one my co-workers had an Replicator2 at his previous job, and it had lots of play in the axis causing ugly prints. However. That's just 2 samples, and I'm biased.
  20. And we have LOADS of replacements. Whuahahaha! However, no luck, it did not explode, it did not even break. It just lit up the lights and nothing else. So I'm a little bit sad now.
  21. I'm been working with someone on the raft code, the TEST versions contain half completed versions of this, causing problems. However, he is getting awesome results with the final code. A fix for this 45deg angle is already in place.
  22. The Camera feature was causing a lot of issues for people. Not sure if it will be back in the future. It was little used to be honest (I've had it broken for 4 months without anyone complaining at some point)
  23. https://github.com/daid/Cura/wiki/Donations We love chocolate chip cookies.
  24. The support material code isn't that great. You're not missing something, there are just too many internal parameters and dependencies that can mess this up.
  25. *wave* *wave* I generated those files, so I'm pretty confident in what I did... and I was way too busy at that point to tweak files. Now, they where generated with an older and testing version of Cura. So maybe something changed unintentionally. Can you show some photos? That might help.
×
×
  • Create New...