nallath

Contact TNO (Dutch research institute). They have technology that can create those kind of beads.

Because there are things that you need to check for that have nothing to do with settings. We handle a big number of edge cases much better. Old Cura had some rather naive approaches for a number of edge cases, which have now been properly addressed. But a number of these fixes do cost at a performance decrease. That being said; the time estimation is rather rubbish. We are working on getting that better, but it just hasn't been our focus for the past few months.

I just run Cura from source. If there is an error it's printed into the console.

Virtual machines and openGL are always a bit difficult. The warning that you get has nothing to do with your issue. I still think that the drivers are the most likely culprit in this case.

https://ultimaker.com/en/resources/20511-change-machine-settings

Could you share the log files? See https://github.com/Ultimaker/Cura#logging-issues

The next release will have a more precise cutoff tool.

You can get it to work, but it's far from perfect. As you can see from the current state of the source code; we made a number of changes that makes dual a lot easier. I can understand. But we did make a conscious choice there. Once you have a .json file, it can be much easier shared with others (even put in a next release).

Cura tries to check all com ports and all possible baud rates. At that point it asks for the temperature a few times. If it also gets a correct answer, it adds the printer to be used with USB printing. So if it's not found, your printer did not give the right answers.

That's because -non- of the ports are found to give the right replies when spoken to Setting them by hand would not have changed anything.

The Rostock Max v2 is not in Cura 2.1.2. If anyone made a file, they should make a pull request so it can be in the next releases.

As far as I know is that the guy that works on the engine just gives all the commands in commandline (without the .ini file). I don't think he has plans to make any changes to it. It shouldn't be that hard to write a little script that generates that though.

The errors are pretty clear. The contents of the .ini file isn't correct. It's also unable to open / create the .gcode file (probably due to rights)

You can if you want to. You don't have to.

Nozzle tip to any part of the gantry that can hit the print. This variable is only used in one at a time printing. Yes.

Thats actually an old setting that isn't used anymore (but we didn't purge everywhere)

Did you use the lastest version of the engine? You are using nightly builds (which do work for me, but you might not have updated everything)

The slicing is slower for 2.1, mostly because it can do a whole lot more. Being able to detect more special cases simply makes slicing slower. As for the layer view; we're working on a fix for that. We should be able to make that significantly faster. The rendering (layers are actually processes) should be quite a bit faster in 2.1.2 though. Another thing to take into account is that 15.04 already shows "inbetween" results, which also gives you the feeling that it's much faster.

It's not implemented at the moment. We're considering doing this though. One of the reasons why we didn't do it right away was due to confusing with the old version, where people had postprocessing scripts active without them noticing.

We have so many things that we work on at any given moment that it's almost impossible for me to keep track of everything we fix. The best way to find out is to just test it.

Yup My personal pet project.

If anyone from the community builds it.

Change your print sequence to all at once.

I tend to use the turntable a lot. It simply saves a lot of time. Instead of having to babysit the scanner while its doing a scan (Make a scan, move object, repeat), you can place the object on the table and tell it to make 50 scans and auto stitch it. In most cases having 8 - 12 scans of a single object gives pretty good results, but more data tends to increase the quality of the scans. Especially the smarter smoothing algorithms that are used to filter out the high frequency noise of structured light scanners benefit from more data (at the obvious cost of memory & cpu cycles).

Dual extrusion is far from perfect. It's hardly tested, so I wouldn't recommend using that in your first attemt to add a machine.