Daid

How are you printing, with the UltiController of USB?

Just looked at this, and the normals of the ring are the wrong way around, which is why the ring is filled with "TypeA fix horrible"

The Cura package is a Gui+Engine, but the Gui part will not run on the PI (heavy OpenGL requirements). You only need the engine from https://github.com/Ultimaker/CuraEngine%20on%20the%20Pi%20to%20get%20OctroPrint

Possibly. I do not have a Windows 8.1 machine to test on yet. But I didn't change anything in the way the windows package is made between 14.01 and 14.03

That would mean we have to have printers, sitting in a box, waiting. Then notify that people can pay, and after they pay (which we've seen take weeks sometimes) we can ship them. So we would have a warehouse full of printers waiting for payments? We would much rather not have this added complexity. It's complex enough as it is already. You pay, you get added to the queue. That's how it works right now. We would like to have stock ready to send out, however, currently, we are not producing them fast enough for that yet. We're working on it. But until then, there is a 8 to 10 weeks delivery time. As noted when you order. Pretty much take it or leave it.

I think those warnings can be safely ignored?

I recommend tilting the object so that the icon is at the front instead of the top. This will most likely print better. As the details on the XZ and YZ plane are better then the XY plane.

Can you try this. In C:\program files (x86)\Cura_14.01\python\Lib\OpenGL\DLLS There is a glut32.dll Copy this to C:\program files (x86)\Cura_14.01\python\DLLs And try if it works after that?

On the growing pains. We went from 12 people 1.5 year ago, to 53 full time people right now. It's very hard to keep up with the growth. With such explosive growth we have internal communication issues. Oddly enough, mostly from sales&marketing (who you know, should deal in communication) But, that's no excuse to handle communications and customers like this IMHO. @anon4321 1) We sell and ship world wide. You do not want to know how many orders we have in the system that come from people that promise to pay but never do. And just about any webshop that I know of takes money first and sends products later. 2) Yes. Or at least, tell people if you will not make the date. For the cables, it was out of our hands that we did not make that initial ship date 2.5 week ago. But if we communicate that there are some minor issues with getting the parts the customer at least knows what the hell is going on. 3) In all honesty, there are bigger problems then a simple name. It's "ready for shipment", at which point the logistics people know they can ship it. However, on the back-end side of the shop there are much more pressing issues that need to be fixed.

In theory, yes. But how to you know what is the final object? And how extra confusing it will be towards the user? And how much extra work from me ;-)

This. Because the gantry can hit the other printed objects when finishing the later objects. I'm looking at the PrintrBotXL here for example, and it has about 10-15mm of clearance on the gantry. So no way you can print anything usefull one-at-a-time with a setup like the PrintrBotXL.

Yes. It is unacceptable. And I had a pretty big fight with one of the people from sales&support last week. About a related problem. So I want to thank you Phil. As your post backs up my point. Now, a lot of machines where delayed due to the lack of heated-bed cables. Which where promised to us 2.5 week ago by our supplier, but only got delivered last Friday. So they have been installing the cables on almost finished machines, testing them, and sending them out ASAP. Now, when they ship, you should get a tracking number. So I do not think it's shipped yet. But I cannot be sure (I do not have access to those systems in the company) (David, R&D, Ultimaker. The software guy)

Cura cannot seem to find the GLUT libraries, with are part of OpenGL, which should be part of DirectX or your video card drivers.

In general people that are good at translating do not have the skill to setup git and send a pull request. But the effort to get translations was done already. However, like I said, the result... I'm not that happy with it. So this is a difficult thing. Should I provide crappy translations from the community, or no translations? Also, by providing more language options, I will get bug reports in other languages, that I cannot handle.

It slices fine, but due to changes in the layer view it looks a bit messy for such a small object.

It can also be part of the bottom/top infill. So setting that to 0, and the infill % to 0, they might be gone.

"bug in RC7, fixed already for next release"

You can email it to d.braam@ultimaker.com I'll keep it confidential.

I can see your english is poor (not to be offensive). But can you understand that my polish, german, french, irish, zech, slovak and serbian-bosnian is even worse? Only my dutch might be better (native dutch) Data from wikipedia is always sourced from somewhere else. But, let's grab better that. I mostly care about the European and American market. I think you can agree that the American market is mostly English. Especially for the high technical market. In the European market there is a 65% English as preferred language for international communication. Now, even with all that, we prepared Cura for translations. However, while translating to Dutch and German we already noticed that Cura is filled with 3D printer jargon which is English only. So even the dutch translation was crappy. As I had no way to verify the other translations I disabled language selection for now, as I did not want to set false expectations. The french law is nothing odd. That's actually a European guideline (adopted as law in most European countries, as the EU cannot set laws). Which states that you should provide manuals in the native language of the country where you sell your product. It is something we are working on. (As proved by the disabled translations of Cura) but we are short on manpower. So it's not so much a "should we?", it's more a "should we do this now?"

It's filling up thin wall sections, no bug, a feature.

It should have different start/end code for each machine. But looks like I managed to bug that... I'll fix it soon. But in the RC7 on MacOS, already fixed it.

I've also setup the all important Dogecoin wallet. Such wow. As well as a litecoin one. https://github.com/daid/Cura/wiki/Donations Because I could. I'll buy my cat some extra straws (he loves those for playing around) as well as some extra cat-sweets! He ignores catnip so that's no use.

It's a leftover from development. It has no use right now. (We tried to see if we could fit an over-temperature protection sensor on there, but experiments showed that it triggered too late) The fan could wear out, it also makes noise. The future modification will only be in new printers. (Current fan is wired straight to the 5V, no way to control it) But the update is a bit delayed due to some problems with a tiny layout change causing changes on the motor current. Funny how small things can have so much effect. The fan control is already in the firmware now: https://github.com/Ultimaker/Ultimaker2Marlin/commit/d85409f22204c606a331f49a83d31745b3d961ba

The default print window is now very basic, with just a connect/print/cancel button. You can switch to a more complex dialog in the preferences. This more complex dialog is build by a plugin and the plugin can be edited and expanded on to reflect your needs.

Cura is prepared for translations now (that's why I called the "blast from the past") But the quality and completeness of the translations is not really high...