nallath

You're trying to import a single extrusion profile to a multi extrusion machine. The old Cura didn't have multi extrusion, so there just isn't a way to do the conversion (or well, there is, but it's way too complex to put all of that in code).

They were moved as part of the redesign of 4.0, but other than that, they are still there.

Well, that shows that my memory is rubish.

I guess that by now the PITA is on linux as well. I don't think that it's easy to get qt & pyqt for 32 bit, so you will also have to build that from source. For windows it's probably nearly impossible by now.

The front end can be built in 32bit, it's just a complete PITA to do it.

oh, wow. I've never seen it do that before (which is one of those things you never want to hear from any engineer I guess). Could you share your logs? I don't think there is going to be anything in there that is usefull in there, but it's worth a shot.

It's something we're already looking into.

It's not that hard to disable the perspective, all we have to do is re-implement the zoom bit. It's on the back log. I've direct all the requests I've seen about it to our product owner, but in the end, it's up to him to give it a high priority (or not of course).

help-> show configuration folder

There are also openscad mold generators floating around the internet. You can use those to specify how many parts you want the mold to be and they will also generate connectors.

There seems to be some issue with the SSL certificates. I don't know what caused it, but it's quite weird that it didn't cause any errors / warnings to pop up to the user.

By the looks of it, the model is exported incorrectly. Did you check the model in a model checker?

Please share your log files. See https://github.com/ultimaker/cura#logging-issues for more information on where to find them.

Simply put, we don't know. The developers of anti-virus software don't ever share why something is marked as a virus, so we don't know what to do to resolve this.

By the looks of it, something is messing with the connection between the front-end and the backend. Could you try to see what happens if you disable your firewall / virus scanner while you start Cura?

That's probably because your firmware. Cura assumes that all commands it sends are for the active extruder. Some firmware has the (default) option enabled that when no extruder is specified with the command that it sees it at "do it for all extruders"

This was a bug in the first beta, which has been resolved for the next one (but it hasn't been released yet, so a little patience is needed).

I don't know what changes lulzbot made to their version of Cura, so there is little I can do to help with that. I suggest you contact them and ask for support.

Cura assumes that each extruder has one hotend. We can't really test for anything else, since all Ultimaker machines adhere to that assumption.

That's what it should do, yes.

We quite recently found an issue with the maximum resolution being far too aggressive. So you're right with regards to it giving weird results.

If you merge the models, they should use the same system of origin (and thus, line up).

This is a setting you can set in the machine definition. If you set that file extension as the first one in the "file_formats" option, cura should default to it on saving.

We're not planning to do this. It would indeed mean a nearly complete re-write of the code, as well as greatly increasing the maintenance cost.

That's because it's a post processing plugin, not an actual simulation. As such, it only changes the settings (and doesnt re-calculate anything based on those changes)