bagel-orb

Please make a github ticket at Ultimaker.github.com/CuraEngine

Perhaps you can use Uranium, but build your own frontend on top of that instead of Cura?

Hopefully within the month. We're realizing some processes cause too much lag for a nice UX and some mechanisms are a bit counter intuitive. Also we found some new bugs. We're polishing all such problems out right now. Could be a month - maybe even two.

Yes

It's too much computation to check every infill line separately. Instead we just check the whole infill area - disregarding which part of it has already been laid down. It's too much computation to make sure you aren't passing over infill lines that haven't been filled in yet on the way.

There's a support roof which you can set to have a higher density. There is no possibility to make a fluent change from less dense to more dense; there's just two states: less dense (support 'infill') and dense (support roof).

@pm_dude indeed many people see the hysteresis effect as a delay, which is actually an oversimplification of what is happening. The fact is that a given speed requires a certain pressure in the nozzle, which translates to an offset of the filament. Higher speed = higher pressure = higher E values. The effect does take place between every two extrusion moves (if they have an angle other than straight). However, once filament has been put down in a certain place, the pressure increases. This constitutes a self regulating mechanism: as long as the pressure in the nozzle is high enough to obtain the maximum flow required in a single extrusion move the layer below will provide counter pressure at the corners, where the movement speed and the filament flow slow down. When changing the speeds in the gcode, the maximum flow over line segments changes between consecutive segments, which causes the pressure to be too low, which in turn causes under extrusion until the pressure is high enough again.

I wonder whether going slower will actually increase the quality, given the hysteresis effect of a Bowden tube might cause overextrusion and under extrusion around speed changes. Moreover, problems of overhangs are foremost the sagging and falling off material, which I expect to be more of a problem at slower speeds. Have you tried turning the speed down by hand during the printing of overhangs? Before implementing such an idea it's good to have some empirical verification of the idea.

That's a branch. See https://github.com/Ultimaker/CuraEngine/tree/PathOptimizer_RandomInsertion Google "git branch" if you want to learn more.

The pathOrderOptimizer is currently being revised. You should take a look at the feature branch https://github.com/Ultimaker/CuraEngine/tree/PathOptimizer_RandomInsertion

Just to clarify some mistakes made in this thread: - there are no floating point errors because cura engine works with integers at most places - the bucket grid looks at patches of 3x3 buckets, so that consecutive lines falling just on two sides of the border between two buckets won't be treated as distant to each other. - filling small gaps is done as normal line infill

On the new CuraEngine (of Cura >= 15.06) use ./CuraEngine slice -s layer_height=0.2 You can type ./CuraEngine --help to get more info on how to use the tool. What version of CuraEngine are you using?

I cannot reproduce any bug in the infill percentage. Are you sure you haven't set the infill pattern to Grid instead of Lines? With an infill percentage of 50% and the Lines pattern, the lines are as far apart as they are wide. For the Grid pattern they are 3 times as far apart as they are wide. Perhaps this bug was due to the setting update bug which has been solved in the meantime.

The beta is released! https://ultimaker.com/en/community/view/17296-cura-1510-open-beta

I am happy to say that software.ultimaker.com now points to 15.04.2 instead of 15.06.3. 15.06 releases can still be found under the list of all version downloads.

As to the issue on the 15.06 release being beta: indeed we were wrong to communicate it as being a normal release. The old Cura was never released in stages. With the new Cura we moved to a system in which we first do a beta release before we do the real release. This went wrong on the first release of the new software. When we first released the new interface we were too eager and changed the download link to the new release, while we shouldn't have been so eager. The 15.10 beta release should be downloadable this weekend, though it will not be the one directed to by the main download link. There will be a link in a forum post soon.

The issue is [sOLVED] for the next release.

@peetersm Indeed this seems like a pretty serious bug. I've been working to make the next (real) release bugless. The beta of the next release will be released in a day or two. I'm going to do my best to correct the bug before the new beta release. For the next time: please submit a github issue at https://github.com/Ultimaker/CuraEngine/issues/ (or https://github.com/Ultimaker/Cura/issues/ if you don't know whether it's a fronet-end bug). Posting a bug on the forum is unlikely to get me working on it.

The bug is now solved. The next release won't have the bug. @gr5 Please refer to me instead of nallath or daid, since I am currently the CuraEngine software engineer.

Note that the forum is not the correct place to notify us of bugs. Please do so at https://github.com/Ultimaker/Cura/issues

Some minor bugs caused the front-end to crash every time. This is fixed now and will probably be released next week in Cura 15.06.02. Note that the layer view cannot handle wire prints, with their loads of Z moves. While developing I used http://chilipeppr.com/tinyg for viewing the resulting gcode. Also don't be overwhelmed by the shitload of settings for wire printing. Just use the defaults (when using an Ultimaker 2). You can control the density/accuracy/layerheight of the net structure with the 'Wire Print Connection Height' setting. When tweaking, start with the 'fall down' and 'drag along' settings (for 'Wire Printing Strategy' = [Compensate]). PS: If you call CuraEngine directly via the command line there is not problem. e.g. ./build/CuraEngine -v -j ../Cura/resources/settings/fdmprinter.json -j ../Cura/resources/settings/ultimaker2.json -s wireframe_enabled=1 -o "output/test.gcode" ".../3D_models/wireFrame/angles.stl"

Some minor bugs caused the front-end to crash every time. This is fixed now and will probably be released next week in Cura 15.06.02. Note that the layer view cannot handle wire prints, with their loads of Z moves. While developing I used http://chilipeppr.com/tinyg for viewing the resulting gcode. Also don't be overwhelmed by the shitload of settings for wire printing. Just use the defaults (when using an Ultimaker 2). You can control the density/accuracy/layerheight of the net structure with the 'Wire Print Connection Height' setting. When tweaking, start with the 'fall down' and 'drag along' settings (for 'Wire Printing Strategy' = [Compensate]).

The problem is not so much with your BFB printer, as it is with Cura. Cura just doesn't fully support multiple extruders yet. This will all change in a couple of months, though!

It might be that the estimate is now more accurate, or that the actual paths have been changed for the better. I think you should stick to the new version of Cura. Do the models take longer to print in actuality as well? Can you test the actual printing time vs. the predicted printing time?

Shellthickness : 0.4 instead of 0.8