nallath

What do you mean by that? The values are the thing that needs to be changed. Also, someone contributed profiles. You can find them in the github.

No, it's an engine thing. I never worked on the slicing engine. @bagelorb might know.

I don't see anything that I directly know a solution for. Could you post this on the github issue tracker?

If you make a pull request I can merge it.

Chloroform works. But that's more like welding as you actually dissolve the plastic.

You don't need to compile python for it to work. The package.sh script is only if you want to distribute (and create) an executable. Also, did you try to build the old cura or the new one?

The new cura has some problems with USB printing we've noticed. We're working on it

Someone added a Prusa preset, which has been merged. You can find it on the github.

I've sent this to our quality assurance people as I'm not sure they visit the forum frequently.

Check this with prontoface / printrun. We don't spend much time on the USB interface for the UM2, so its not nearly as impressive as the one from prontoface. It sounds like a hardware issue though, so i'd contact support to get replacement parts.

I'm not quite sure what you mean. Could you try to explain what the expected behaviour is compared to what happens?

It's not a poor decision, just communication that went wrong here. Lot more people involved, so stuff like this is bound to happen. We do need to learn about this and I've advocated this point a lot.

I believe it should also change the distance else it would have massive overlap.

Just doing what needs to be done

@Bird This is not the logfile, but helpfull none the less. The logfile is an actual file (with .log extention)

Oh cool. Last thing I saw of them was the gradient. Pretty awesome that they got it to work.

I wasn't in that loop, so I can't say anything about this. I will check where this went wrong.

I know. I thought this was going to be how we were going to do it, but turned out I was wrong. Because of that, I never poked people why we weren't doing it, so I found out when we released it. But we're getting there. It would definately help if users think about the data we might need to solve the problem. We still get too much issues saying; 'It crashes, fix it!'

UMO has dual extrusion.

All the settings that are in the UM files are settings that you can use (and are recognised by the engine). I don't have a easy list, sorry. Probably. We've had more requests for this. A hack is to use disallowed zones.

Working on a roadmap. There will be one. You're right about the not fully being decided one way or another.

As said a few times in other topics about the new Cura; All non UM presets are provided by others (companies / community). As the setting system has been completely modified, we have no settings for non-ultimakers. Once someone adds them they will be shipped in the next release.

Technically it is a release. But see it a bit more as an open beta. We've learned that we need to be more careful with expectation management. We tested it for 2 months with people from the community, but when building something from the ground up that just isn't enough apparently. Frustrated means you care, that's good. Don't worry, we have thick skins. We also want this to be awesome.

Yes.

Just a quick correction; The Cura GUI is built to be enhanced by plugins. The engine has no such feature (yet... Dont expect it very soon).