nallath

There are 400+ people working for Ultimaker. There is no way that everyone can know what is happening at any given moment. So yeah, I do work for Ultimaker, but that doesn't mean that I can give answers about everything that's going on at any given moment. I understand that people are frustrated about it, but there is also no need to start lashing out at anyone working for UM that is responding to things in this topic. I'm trying to help in what limited way I can. Not because I have to (because hey, it's not my job), but because I feel that it's important to do so. Let's turn it around a bit; I'm seeing a lot of frustrated people. But due to me not working on the right project, there is little I can do about it. What I can do is respond at some of the other remarks that were being made. Upon doing so I suddenly get attack for doing that. What kind of message do you think that gives off? If that happened to you, would you feel that it matters that you're trying to help? I doubt it. So yeah. I do respond a bit cranky if my genuine attempts to at least do something get annoyed responses. It frustrates me that what little I can do about this issue isn't going to fix it. I also get that your frustration is even worse because there is even less that you guys can do about the problem and for that, I'm really sorry. There just is no more information than "We're working on it as best we can". I know that's not a satisfactory answer because quite often this is used as a "shut up and leave us alone" response to get people to stop complaining. But it's the best answer I can give because it's the truth. We are working on it, it is something that a lot of people (myself included, even though it isn't my problem) feel strongly / responsible about.

Because I'm not a firmware engineer. So yeah, I reply to things I know something about. Which in this case was scanning & sensors. Or would you rather have me not reply at all or give you false / incorrect information? If you want a nice white lie, I'm more than happy to give it, but I assumed that this is not what you guys want / need.

Cura 3 uses the same file types as Cura 4. You would need to copy another file as well, which can be found under extruders (creatily_cr_10_extruder_0.def.json). If you put those in the same location as where 3.4 put them (but then for 4.0) it should be picked up.

Getting an obstruction sensor in a single line with that tolerance? You're lucky to get that for below a few hundred $ in parts alone. A line scanner of that quality is about 7k ish.

Well, support is a big word. The github issues are handled by us (the Cura developers) ourselves. The main reason asking for posting it there is so that we have one source of information regarding the issues. If we don't we would spend even more time than we have to now keeping track of issues. Github is also the place where non-ultimaker devs look, so it's also sure to get you more attention.

Yes you did. Two people working for Ultimaker have replied to the issue (People with the tag work for Ultimaker

Could you report this on github? The forums aren't that easy to keep track of bugs / issues.

You can set an individual printer to "not available" in the printer tab with the context menu. Alternatively, if a printer is in the change material mode, it won't accept new jobs.

If it's only showing a single image, that's a bug! Could you report it on github?

That just looks like a display bug. Could you report it on github?

There has been in a button in Cura for quite some time now that shows that a post-processing script is active.

S3D also has hardcoded headers for the g-codes that it generates, so pretty much all the remote monitoring of print-jobs (as well as the checking if you have the right material loaded, etc) will work poorly (if at all).

In older versions of Cura, you needed to download the backup plugin from the marketplace. Also; The restoring backups from older versions has been fixed. From 4.1 onward you should be able to restore backups from previous versions.

There is a plugin in the marketplace that puts the sidebar back in the semi old stile it was.

There are two things you can do; You can either create longer squares with the MeshBuilder and move them down a bit (since they are places based on their center) or you can scale the model (check the setScale function of the SceneNode that contains the meshdata)

Please report issues on our github issue tracker (https://github.com/ultimaker/cura)

This feature doesn't exist, because the profile changes that you make don't depend on the material in any way. This is partially caused by having to support dual (or any multi) extrusion machines, because at that point the profile would depend on both materials, which causes all kinds of UX issues.

You should contact the developer that created the plugin. The marketplace should have the contact info.

Do you have an image of how it looks when it didn't print? My best bet is that it's trying to print the PVA, but it has a blocked nozzle.

The stderr and stout are logging files. Deleting them is completely safe to do. It could be that a previous instance of Cura still had a lock on those files (which for some reason was never released) which prevented the next startup of Cura from writing to them.

Plugins can theoretically use .dll files, but it's probably going to be tricky to get it to work properly (if at all).

I've already put the total cost next to the filament length for 4.1 (you're not the first to ask for it!)

Could you log the issue on the Cura github and share the model?

The naming of Cura Connect is a bit unfortunate IMHO as it doesn't actually connect Cura's but only Ultimakers (in that regard Ultimaker Connect would have been a better name). You're not the first to be confused by that. Smithy is indeed correct with his assessment. It's probably possible to support the Makerbot API's, but we won't spend any time building it. I very much doubt that Makerbot will put in the time / effort to make such a plugin either.

Nope. It's currently not possible.