nallath

If printerbot makes a pull request that is of sufficient quality.

Microsoft sells their software. We don't. You cant expect a commercial entity (which ya know, Ultimaker is) to invest in the products of the competitors. IMHO we're being kind enough as it is to even let others use the software. It's fair to draw the line at investing even more resources. Besides; the software windows sells is more valuable when more stuff works on it. They are making more money when they do this. We dont. Actually, we'd even make less as there would be less competitive advantage. You're free to think of it what you will, but if you want the support i'm going to have to fall back to the old open source saying; "Patches welcome!"

Could you send me the log? What OS are you on? What basicly happens is that Cura tries to establish if connected USB devices are actually printers. We've had other reports that this doesn't work correctly on mac for some users.

It's still usuable for non ultimakers, we just havent recieved any profiles yet. Other companies are free to add profiles (which they did in the past) but we're not going to spend resources on tweaking their machine with our software.

The USB print button only maaagically apears when it finds a printer. This is changed from the old cura where it would always show a print button when something that resembled a printer connected (even an Arduino board). The new Cura first validates if it actually speaks g-code before showing it as an option.

Do you get the same error? Because the error Ulti-Arjen posted doesnt seem to have anything to do with the firmware (but with the scene not properly being locked during the push free operation)

There isn't at the moment, but it should be relatively easy to make an extension plugin that does this. Provided I have time, I'm going to try to build it tomorrow.

Well, thats a bit of a harsh comparison. At least Cura runs on 30+ fps I'm well aware that there is a lot missing, which is not all that strange considering that the old Cura is 2+ years old. But because it was that old (and never designed to be easily built upon) the code resembled a lot of the monster of frankenstein. Starting over does set you back with regards to features / functionality but will pay off in the long run.

Not sure if we will be implementing it (or atleast; it won't have a high priority with us, especially not looking at the number of suggested improvements / changes). We haven't made this properly 'pluginable' as far as see now, but it shouldn't be very hard to implement this. As we now have more developers (eg; not just Daid hacking away), we will be much faster in accepting / reviewing pull requests.

What do you mean by this? If you copy one of the json files there, rename it and change stuff in it, it should be picked up by the GUI.

Huh, weird. What OS version are you using?

@danilius; Linux build is up. @kepolas; Yeah sorry. A lot of settings are re-done. It's a complete nightmare to convert the setting list into another. We had to do this in order to keep it maintainable.

Its not exclusively Ultimaker, but we have a lot of new settings. We rely on comunity / other companies to provide us the settings. You can add new machines by adding .json files to the resources/settings folder. Cura should pick up on it automatically.

@danilius; I hope he found his peace. May he swim freely in the everlasting sewer pipes of the plenty.

It should be in the .json settings file. Not a 100% sure anymore if its in the machine configuration list.

It is a setting, just not one that is visible by default, as most users tend to use the default nozzle of the machine.

Yeah, applications is a confusing term.

Same here on a Win 8.1 VM with 15.02.1 being the last installed Cura. We had a bug like this before, where an old version was the problem. It seems that is not the case here. We're working on a hotfix.

Well, beta releases do give an additional step but that 'cost' ensures that the quality of your release improves. The only difference would have been calling it an open-beta (hence my confusion about this). It's all about expectation management; If you download a beta and it crashes, that is sortof to be expected. If you do the same with a release version, it's bad.

Could you report the issues you have with it? Saving to file & USB printing should work.

https://github.com/Ultimaker/Cura/issues/72

Remove the configuration file. You guys have had the beta, which causes problems (appearantly)

Well, the Linux version is the wrong one. So yeah, this is why I thought there was going to be an open beta before shipping it to the world. The latest roadmap I saw had an open beta in it, but it could be that it was scrapped to get a faster release.

As far as I know we were supposed to launch a open beta first. We only had a closed beta with 25 ish people testing it. That will catch a lot of the bugs, but not all of them.

Note that the builder3d-printers only use this to mix fillaments in a gradient. Quite different from dual material.