nallath

I think you are the first! Congratulations!

Good news. I found the issue & fixed it. I can't reproduce it anymore. I will ask QA to put some extra testing effort into this. Sorry for the inconvenience.

Because the material might not exist, or it's values could be different. If you always update the existing, it might mess up other settings (or other work you still had in progress). This is why it asks you what to do with it. But yea, right now it seems to be messing up a ton of stuff. We're looking into it. We obviously missed a few reproduction cases, so thanks for helping out.

If you're feeling up to it, you can have a look at our Cura-build repository. But this is not for the faint of heart. Quite a bit of experience is needed to get that running properly. This also means that for every software update, you would also need to make new packages. If you don't feel like that, putting them in the local folders is the best option. Those are also upgraded if a newer version is installed. An easy way to install a local machine on multiple computers is to use project files. A final option is to make a pull request that contains the machine that you have as a definition. The next Cura release will then have that machine and others can also benefit from it.

We just looked into it. It happens if you load a 2.5 project into 2.6 and then load a 2.6 project and the machine in the project is a multi extrusion machine. We had an issue with 2.5 where the internal name of the extruders was weird (eg; id of the machine was ultimaker3, the extruder name would be ultimaker3_extruder_left #2). This was changed for 2.6, but it appearantly messes up the project loading. As it's caused by a old version (which we can't retroactively change), there is no 100% fix for this.

We depend on others to provide the right settings for non ultimaker printers. We don't test those at all. It could well be that the provided files for that printer are wrong.

Disable the plugin in the plugin preferences window.

Nope, I can't explain this. I also can't reproduce this :( Can any of you post logs & project files?

Making a plugin and distribute it under MIT or BSD should be possible. You pretty much have 3 forms of GPL; GPL, AGPL and LGPL. AGPL is slightly more strict as GPL. As ahoeben mentioned, it "fixes" a loophole in GPL, by making the definition of what a distribution is more broad. LGPL is less restrictive; If someone uses Cura (dynamicly!), it does not infect that code. If someone makes changes to Cura itself these must be licenced under LGPL

Have a look at https://github.com/Ghostkeeper/X3GWriter It only works for windows. Not sure if it works at all for the latest Cura versions.

2.6.2 only has changes for older versions of OSX. It could be that you are trying to run 64 bit version on 32 bit machine. We stopped supporting that since 2.3

QML supports gifs, so you can even make it sparkle!

hint hint, developers tend to like thank you cookies

Change the material / nozzle in the second extruder. Cura selects a profile that can be used on both extruders.

I wouldn't recommend using USB printing. It will only add more points of failure, without giving you extra features. We officially don't support USB printing for the UM2, so it's not something that gets a lot of attention when testing.

There are no mirrors that I know of. I just checked and the server seems to be running fine. If you try again I think it should work.

Did cura 2.6.0 or 2.6.1 work for you?

The only change for 2.6.2 is that we fixed it not working for older OSX versions.

Ah right. Well, just using it as if it's the generic material has no impact. We don't have material specific settings based on the color.

Cura uses the exact same settings for Ultimaker Black & Generic ABS. If you are using UM material, your NFC reader should already handle setting it correctly, so why are you manually selecting a material?

It should I made some fixes for this problem in 2.6.1. You're the first to encounter something like it again. I was kinda hoping to have it fixed :( Thopiekar is hired as a freelancer (and intern). So no worries We tend to send job offers to most people that live in the area and help out with software. We're always short on good engineers But the PPA isn't tested by our QA team. So in most cases it will probably work, we can't promise that it will. This is why i'm constantly saying we don't support it (even though we kinda do), but I want to prevent any confusing as to what should work and what might work.

You can remove all machines that you don't need from the resources file. Depending on your operating system this might be something that's easy or quite hard. You need to remove *.def.json files. Take care to never ever delete the fdmprinter.def.json. If you have a UM3, you need to keep the fdmprinter.def.json, ultimaker.def.json & ultimaker3.def.json

Pff, I have little to do with the firmware these days. But any patent application does not prevent us from sharing the firmware. Once you have a "priority data" it doesn't matter that much anymore that the source code to do it is out there.

Yes, but, having to do that to make things go up or down to accommodate the base base of the object can be frustrating. I can usually fix those things as they are basic. Next time I have a model that behaves badly, I can PM a link to someone so they can look. Modeling is one of the areas I am confident on, so I am puzzled by this. It will probably be something silly, but a second set of eyes may be helpful It could be that disabling that feature actually makes them behave that way. Do they properly get put on the bed if you enable it? Feel free to share the models with me. If it's something with the models, it's always good to have a few more edge case models.

Cura 2.6.1 only does autodetect. As for printing with USB, I don't recommend it. There are a lot of issues with it and greatly increases odds of your print failing.