nallath

It will be for sure, OpenSource is the reason why Ultimaker is still here, and still a leader in their market. And it's something they are very proud off and that makes everybody go forward. The open source feeling is something that is strongly supported inside the company. It's part of our core values. It's also a fairly strong recruiting tool, especially for software developers. I don't think that we're going to change that any time soon.

Or;

We would. Everyone in the R&D department takes great care to assign attribution where it's due.

Could be that I'm just overlooking something, but isn't that just the default way of doing it? (eg the same way the UMO Dual extrusion kit does it?)

It's only fair that Ultimaker developers (who do 90-95% of the work) focus on getting the experience right with Ultimaker machines. We've tried getting in contact with other printer companies if they also want to develop for Cura, with very limited success. So if you want your printer to work you can do two things; - Send one of the Cura devs the printer, so we can actually test (If I get a free printer, I'm going to spend some of my own time on this ). - Convince the people who made the printer in the first place to put some resources towards fixing it.

Oh right. Time to get started. I'm sure that this time I'm going to be right; It's clearly a lawn mower! You mean, it's UNclearly a lawn mower... Ofcourse. Silly me.

Oh right. Time to get started. I'm sure that this time I'm going to be right; It's clearly a lawn mower!

Some simple g-codes should do the trick. G28 # Home G0 X0 Y0 Z10 # move to 0,0,10 See; http://reprap.org/wiki/G-code

You could also enable the ooze shield setting in Cura.

Only if someone from the community / another printer company builds it. We (read Ultimaker) aren't going to spend time / resources on it.

The {speed_travel} simply puts the direct value of the travelspeed there (which is in mm/s), without attempting to do any form of conversion.

Yep. There is no way to set line width for layer 0.

Cura doesn't have the temperature, so it can't show what it doesn't have. Back in the day, we thought that settings such as temperature should be material dependant, so you could use the same g-code with different materials. We now know that this is very naive.

This completely depends on the size of your skirt. Due to tolerances, we don't exactly know where the clamps are located. In order to be on the safe side of things, the disallowed area's are to big for most machines. Clearing your local folder should fix this issue. Either that or wait until thopiekar made a new build for the PPA.

Hover over the i. It should show you why it's hiding it. The um2 will never show heated bed temperature; The machine itself decides the bed temp.

Could be a bug of the linux version, because it should be there.

Printer profiles can't be imported. You need to change those by hand. They are too fundamentally different to have a conversion script. The zip file error has been fixed for the release (2.3 is still a beta)

In any case, you explicitly downloaded it as being a beta. The big ass download button points you to 2.1.3. As for the folder, it has to be there. There is no other way that you can have settings saved. Open a terminal and use: rm -rf ~/.local/share/cura to remove the folder.

https://github.com/nallath/PrintCostCalculator <- fur 2.1.3

There is a legacy profile importer. It should get you quite far, but there is no complete 1-1 mapping that works in all cases. In the profile preferences menu you can import legacy (*.ini) profiles.

I think this is an inheritance issue again. The icons to indicate that this is happening aren't enabled in the beta.

As already a mentioned a few times in other topics, there is an issue with the beta and importing existing profiles from 2.1. This will be fixed in the release, but issues like these are why we use beta's. You should expect that some things just don't work a 100% when using a beta. You can fix this by clearing your setting folders and restarting Cura.

Eh. I said, change the value such as num lines. Let me show you the difference; and See the difference? Cura is doing exactly as you ask it. You ask for a print that has a bed adhesion, which also takes up space.

You have a non-zero bed adhesion size. Try changing the bed adhesion (most notably the num lines / width settings)