ahoeben

It is very easy to miss a comma or have an extraneous comma in JSON files, and that will make the respective machine not show up. A validator like http://jsonlint.com/ can be helpful

As a quick fix, set the support overhang value to anything but its default value of 50.

Erm, don't bother. It's broken and I will make sure it is fixed before the next beta drops.

> 1. Layers View IS SCREAMING FAST! Many thanks to Johan Kristensen of 3dverkstan.se for that! > 2. Printer Profile creator is great Glad you like it. I created it in my spare time, and am proud it got included as a standard plugin.

A lot has changed with the configuration files. We try to automatically upgrade all of the configuration files in AppData, but apparently we still have some work to do. Emptying the appdata folder is a good thing to try if you encounter issues, but please keep a backup so we can check out what might have gone wrong. Note: Cura should be quicker to start after the first time (because it does not need to parse all machine definitions again).

I see... The "merge" code turns out to be some pretty crufty code. Because your models are positioned a bit away from their origin, the merged object gets a weird origin, which screws up the positioning. I will try to get this fixed before 2.2 is feature-frozen.

Thanks for the models. I will check them out tomorrow. In the mean time, here's a model I did for experimenting with different settings in one print: https://www.youmagine.com/designs/spire One important bit for successfully merging two objects is that they should share the same origin. In 2.1, the workflow would be to load both objects, and use the Per Object Settings tool to add settings (such as fuzzy skin) to one of them. Next select one of the objects and then Ctrl-click (or Command-click) the other. Now both should be selected, and it should be possible to select "Merge objects". In 2.2 we will have improved this by quite a bit: You will be able to change settings of objects that are already merged, we have added keyboard shortcuts (Ctrl-A to select all objects, Ctrl-G to group, Ctrl-Alt-G to merge, Ctrl-Shift-G to ungroup/unmerge), and more. Moving objects "by numbers" will also be in 2.2. There's already an option to turn off the "push free" feature, but I don't think there's an option to stop the auto-z automatically. I'll raise an issue about that.

Sorry, I was trying to be helpful. Did I say anything to deserve a rant? Perhaps if you posted the models, we could see if they behave in an unexpected manner.

In Cura 2.1, you can select multiple objects with Ctrl-click. In Cura 2.2, we will change that to the more discoverable Shift-click, and we will also add a Ctrl+A to select all objects.

This too will be available in Cura 2.2. The Machine Actions plugin that I wrote was merged into the Cura master branch a couple of days ago: https://github.com/Ultimaker/Cura/pull/924

bei der neuen Software findet mann diesen Punkt noch nicht. ;-)

No need to sift rhough it by hand; you can import the gcode file as a profile (Profile -> Manage profiles -> Import)

Calculating the print time is not trivial. There are a lot of physical aspects to take into account, such as the actual speed and acceleration (and "jerk", the rate at which acceleration changes) of the print-head. With actual physical mass, and things like a bowden-tube pulling on the head, things are a lot more complicated than position = speed * time (or rather, it is complicated to calculate that velocity over time). Having said that we have recently discovered some inaccuracies with the algorithms that simulate these physical aspects in the Cura engine, and future versions of Cura will likely have a better print-time prediction.

A small addition. Since you have a UM2+, ignore the files in the materials folders. These are not used if you have a UM2+ selected as your printer.

This is a (somewhat) known issue, that only happens on the first run of Cura on Windows. What happens on Windows is that the installer must run as "elevated" (admin) user. When it runs Cura after installation, Cura is also ran as elevated user, and that breaks dragging files from the desktop. If you run Cura normally, dropping files should work.

@Rejutka: thanks for reporting. I'm pretty sure we have not seen this behavior ourselves or it would have been flagged. It should behave like any combobox (click to show the dropdown menu, another click to select an option, or click outside the menu to dismiss the menu)

If you never use USBPrinting, you could try removing the USBPrinting folder from the plugins folder. But that may have unexpected sideeffects.

We're reworking that bit in 2.2 and beyond and will make sure it works better. A lot of issues were caused previously when postprocessing options were kept between sessions, so it was decided not to do that. It would probably be nice to make it a preference but I don't know how much work would be involved in doing so, so I cannot make any promises. You're using an Ultimaker 2+, right? That has its own set of profiles, and it does not use the generic material profiles. This too is being reworked for future versions. I've seen that happening too. I will make sure it gets fixed in future versions. USB-printing is also among the things that is set to change going forward. Perhaps there should be an option to only check/use certain serial ports.

Hmm, I added a machine with your machine definition as posted above, and slicing works as expected in 2.1.1 for me. Did you test with any specific model? Is the slicing-loop 100% reproducable for you? What platform (win32/win64/linux/osx) are you using? (Note that I did find an interesting bug where the model is being sliced even if it is in the machine_disallowed_area; I'll report that and get it fixed)

Could you post your machine definition?

Good point, I have raised an issue in our internal tracker. If you feel strongly about it and if you have some QML chops, it may be a nice "community contribution" on github: https://github.com/Ultimaker/Cura/blob/master/resources/qml/AboutDialog.qml

@berndjm: that is along the lines of what we have in mind as well. We just have to find the time to implement it. Ideally, Doodle3d would work similarly.

Whoops, we broke it. I fixed the bug and the next release will have a visible changelog. The changelog is available as a text-file at Cura 2.1\plugins\ChangeLogPlugin\ChangeLog.txt, but it does not contain all the specific fixes since the 2.1.0 beta. If you really want to know what changes, have a look at the commit logs starting from april 15: https://github.com/Ultimaker/Cura/commits/2.1 https://github.com/Ultimaker/Uranium/commits/2.1

Grr, we had good hopes we squashed that bug. Thanks for reporting.

leprechauns?