nallath

You can move the tower, so how can you communicate this build volume? "Depending on the location of the prime tower you have nnxnnxnn build area" isn't that helpfull either.

Having a model inside Cura won't change anything with regards to being able to save a profile. I'm 100% sure about that. Those bits of code aren't even aware of each others existence. Duplicate makes a copy of that profile. We found a bug with this after 2.3 release, which is fixed for the 2.3.1 Current settings are changes that you made, but have not saved yet.

I think you still misunderstand me. You don't need to change anything on your machine. Just select UM2+ in Cura. Tadaa, it works.

Poked someone who can.

I haven't updated it to work with 2.3 yet.

As far as I know this is usually caused by material being pushed upwards (warping / overextruding) that creates ridges. When the nozzle passes them, it makes a rumbling sound. Decreasing the speed helps, as does increasing nozzle temp (you pretty much start doing the neo-sanding thing at that point).

Cura will let you slice PLA with BB core, but wont let you slice PVA with an AA core. As a rule of thumb Cura will warn you when we believe the results are wrong, but won't damage your printer (We don't know the truth, so we won't prevent you from doing this). If you are doing something that can damage your printer or is simply physically impossible (Layer height of 0, speeds above the speed of light, etc) slicing wont happen. We've tested quite a bit with nozzle geometries and found out that printing PVA with a AA nozzle will result in PVA getting stuck inside the nozzle, which will then start to degrade and ruin the entire thing. Hence Cura preventing you from doing this.

You can set them in the extruder definitions.

Standard? Metric is standard in almost everywhere in the world. If you have models that were saved in inches, I've created a handy conversion tool; https://github.com/nallath/BarbarianPlugin/

I have a "All files (*)" option there, it's just not selected by default.

There is no planned system. I've added this to our internal issue tracker (for our reference EM-1117)

This is a tolerance of 0.3%, which is in the range of material differences. The only way to get this right is to know the shrinkage per material and compensate for this.

Then it's probably the NFC auto selection

It shouldn't be that hard, but I do think it's the responsibility of the people who made the printer to make a pull request for Cura to add their printers.

Option three was actually something that a lot of people requested in 2.1 (remember last used tool). We got a lot of complaints, especially when using per-object settings that misclicking would cause translation tool to be selected. I've added a feature request to make it a preference (For our reference; Cura-2843)

It also works for me, but it could be that we fixed a few issues since 2.3.0 (which will be in 2.3.1, which I expect to be released in about a week, provided regression tests go well)

Uh, LePaul also tested 1.99, which also left some profiles behind. Those profiles never got a proper upgrade plugin, but the 2.1 to 2.3 upgrader did try and upgrade them, which led to horrible results (profiles with type machine_instance_profile).

Well ya did miss something. Instead of only being able the "drop through" if the value is zero, we now have functions. Lets say for simplicity sake that we have two settings: print_speed and print_speed_infill In the old Cura, if print_speed_infill is zero, it would use print_speed. In the new Cura, if the print_speed_infill is not explicitly overridden by profile or user (by means of a fixed value) it can use a formula like "=print_speed / 2" or "=print_speed". We haven't implemented that you can use those formulas from within the GUI, but snice 2.3 it's possible to set them in the profiles. If you look at the um3_aa0.4_PLA_Normal_quality profile, you can see that the value for cool_fan_full_at_height is "=layer_height_0 + 2 * layer_height"

I've tested Cura with files over 100MB (compressed that is!), which is already quite hard to achieve.

From the software perspective there isn't that much difference between an um2 and um2+. As long as you don't do the firmware update (because then it will select the wrong firmware) all should be well.

Give more information; What operating system, did you have previous versions installed? Post logs, etc.

Changing the line width has almost the same effect as changing the nozzle width. If you have an um2 with olson block, just use a UM2+ machine. This allows you to change the nozzle in Cura.

Yep. Write a post-processing script to do that. Have a look at https://github.com/nallath/PostProcessingPlugin

There is no way to set it automatically.

I don't know. The dual extrusion script never got a whole lot of love from us (I have to admit i'd be hard pressed to find a working UMO dual extrusion in the office)