Daid

The raft and the layer view have some... relationship problems ;-)

I think, that's short sighted of you. 3D mouses are pretty much standard equipment in high end 3D CAD environments. These users are a very nice target for 3D printing. And the added value for them is actually quite high, as they don't have to switch control scheme in their mind when they switch. So for certain environments supporting 3D mouses is good added value and a nice sales argument. (My GF does CAD design, and their office is fully equiped with these. She loves it, so I might be biased)

By setting the gantry height to 10000 and the head size X min and head size X max to 1000 you could achieve the same affect I think.

Same goes for U-PET. The PLA we use does not have the food safe certification from our manufacturers. (Not even natural PLA) This topic on the RepRap forums has quite a bit of info on food safety: http://forums.reprap.org/read.php?1,164077,168351

You might want to look at custom firmware for those printers, I think there is firmware that accepts the GCode that Cura generates.

In the latest versions of Cura (latest release and latest betas) the settings have moved to a location that isn't cleared on uninstall. On previous version, in windows, the settings where all stored in the installation directory, and thus get removed.

There is a 0.5 second delay already. But in the released version there are still some bugs causing less then optimal behaviour, with the beta it should behave a bit better already. Also note, the slowdown when scaling/rotating is due to boundary box calculations, not the slicing process starting. (Something pretty much impossible to change in the current code architecture without causing a shitload of other bugs)

Just looked it up. The rules (as of this year) for airsoft in The Netherlands are that: * You need to be 18 * Need to be a registered member (90 euros per year) * You need to store your guns at home, in a properly locked cabinet * Guns may not be too powerful (3.5Joule, 600 FPS, whatever that means) * Sales need to register who bought guns * Transportation needs to be handled like weapons (shortest route, in a closed bag, ammo separated) Note that transportation is illegal unless for the reasons of going to an event, going to a shop or going across the border. (If you want to go to a friend with it, you need to register it as a private event) http://www.airsoftclubnederland.nl/regels-airsoft-nederland/ So, pretty much, it's seen as a firearm. But also, we (at ultimaker) got told not to print anything that looks like a firearm at the office. Just for press related reasons (Ultimaker prints guns! is just a bad headline)

Can the leds in the right one also be switched off?

Yes, but they are not in the build space for the UMO.

I hear a challenge! To bad we're not actually allowed to print guns at the office. Designspark mechanical. I use it a lot. I have no real prior experience in CAD drawing. I drew a whole 3D printer in it.

The latest official release has a bug with high poly models, causing it to use a lot more memory then needed. The beta solves this problem (not sure which RC had this patch). I'm actually using a 3mil poly model for testing these issues now. And that model slices fine. But, if you have a model that still crashes the CuraEngine with the latest RC, send a copy of the model in my mail (I never share any models that I get from other people, not even in the office, so it's safe with me) at d.braam@ultimaker.com And the engine compiles fine in 64bit. As it runs as a 64bit application on linux and OSX.

I was updating to RC8, but the OSX version failed to build, so I fixed that, and uploaded it as well now.

I think that's the "this developer is not known by apple" warning. Which is a horrible move for small independent developers. Every time you see that flag, remember yourself, that if Apple has it's way, then Cura would never have seen the light of day. As Cura started in my own free time, with zero funding. See the tag as a "I bought equipment from a company that wants to restrict freedom" tag.

That bug has been around forever. It's an optimization thing. If the "gap" is smaller then the top/bottom thinkness, strange things happen in the top/bottom skin.

The UM2 feeder I printed in PLA finally failed after deforming due to "car heat". Other then that, it worked fine with normal 20% infill.

Just uploaded RC8 to: http://software.ultimaker.com/Cura_closed_beta/ Compared to RC7, this contains changes for: * New version of TweakAtZ from Dim3nsioneer * Improved memory handling a bit, so big models slice a bit better (less chance of "MemoryErrors") * Fixed UltiGCode plugin handling (material and time was not filled) * Finally fixed the #F_AMNT# and friends tags in the start GCode. * Added 3D clips to the UM2 bed, and fixed the clip sizes on the right size. You have slightly more print area now. * Added the single-layer-view button by pm_dude * Fixed a few minor issues New UM2 firmware update: * Added option to change material when the print is paused, still a bit experimental, the feature works fine. But I'm not happy about the menus just yet. * Made "PauseAtZ" function the same as a pause on the printer menu. (So you can use the above feature with the PauseAtZ plugin) * Few tweaks on the dreaded "HEATER ERROR" * Temperature display jitter removed (by TinkerGnome) * Fixed the "umlaut" bug for SD files. See: http://umforum.ultimaker.com/index.php?/topic/9093-special-chars-in-filenames-printing-with-ultictrl/ New UMO firmware update: * Fixed the "umlaut" bug for SD files. See: http://umforum.ultimaker.com/index.php?/topic/9093-special-chars-in-filenames-printing-with-ultictrl/ We are closing in on a new official release. So this can be considered very stable.

It puts the origin of the models at the same position. Nothing else.

Tweaks can mess with the estimate, if you are changing the speed.

Seems to happen to people at random. Currently we do not know why, but the latest release candidate seems to solve it: http://software.ultimaker.com/Cura_closed_beta/

Simple example of a dual color print I made long ago: http://www.thingiverse.com/thing:23008 Note that the print quality is a bit better then shown there, as some progress on software has been made.

Solid top on/off was already available in 14.09, but it has become more accessible in 14.12 (due to the "..." buttons)

No, the intention is that it's a semi secret link. People that have the link also know where to contact me to report issues.

I can only give you the same info as I already gave you trough the support staff. It's calculated with that code. That's the algorithm. It's a complex whole where that code calculates exactly what the firmware will do any how much time that will take. https://github.com/Ultimaker/CuraEngine/blob/master/src/timeEstimate.cpp

It's not that hard with Qt. We'll just have to check that it's possible with the python bindings. And we have one of these devices at the office.