bagel-orb

Hmm wait - we could just increase the size of the prime tower disallowed area of course!

Oh dear I missed the official blog post here: https://ultimaker.com/en/blog/35482-cura-24-beta-is-here Perhaps you are loading your project file the wrong way. A project file can be loaded as mesh as well, if you only wish to obtain the mesh data from it. Be sure to do it from [ File ] > [ Open project... ] The profile bug you still experience is one that I have never experienced - not while developing Cura on Ubuntu 16 - nor on the install on my Windows 7 computer at home. Please file a detailed bug report at https://github.com/Ultimaker/Cura/issues A brim on the prime tower is quite problematic since the model might be right next to the prime tower. You don't want the brim to intersect with the model and you don't want the skirt to intersect with the brim. If many people find this an issue I might prioritize it to be implemented in Cura 2.5

That is some mighty strange behaviour! Are you running some post-processing scripts? Do you eject before you remove the drive on which you have saved the gcode? You can try Cura 2.4 beta whch was released today: https://ultimaker.com/en/products/cura-software BTW: The link to the gcode is dead.

Cura 2.4 beta is out! https://ultimaker.com/en/products/cura-software This will have the fill gaps between walls again

It's christmas time and our present to you is ... Cura 2.4 beta! https://ultimaker.com/en/products/cura-software It's got a ton of new features and countless bug fixes. Here's a nice user-friendly changelog if you want to view it before installing: https://ultimaker.com/en/blog/35482-cura-24-beta-is-here'>https://ultimaker.com/en/blog/35482-cura-24-beta-is-here'>https://ultimaker.com/en/blog/35482-cura-24-beta-is-here'>https://ultimaker.com/en/blog/35482-cura-24-beta-is-here My personal favorite new features are: * Project saving & opening * Setting search * Hollow prime tower * Cubic subdivision infill Please complain about any bug you find; we will try to fix it before the final release, but after the holidays EDIT: See https://ultimaker.com/en/blog/35482-cura-24-beta-is-here (Google couldn't find that for me)

The bug was in towers which would get introduced for small layer parts even for top surfaces. These would then be introduced to the support of every layer below. I think you can avoid this bug by disabling the Use Support Towers setting.

This bug is fixed in Cura 2.4, which will be out in a month or so.

You can't do that in cura 2.3, but cura 2.4 has an option to hollow out a model so that support will also be generated on the inside. That's still not really the feature you want, but it's close to it.

You should look at the CuraEngine repository. The commandsocket class handles sending lines to the front end for the layer view. Good luck!

2.x is not really specific enough. 2.1 profile saving can have a bug which creates bad profiles which cause cura to crash. Try to remove your profiles cached in AppData (?) folder. This problem should not be introduced anymore as of cura 2.3, though if introduced by 2.1, cura 2.3 will still crash until the profiles are removed.

I can understand how you run out of PVA filament when you are printing with a support interface of 1.5 mm. That seems like way too much. Could you please link to where Ultimaker UK made those suggestions?

Don't set the support interface pattern to triangles, that's a really bad idea if your interface is 100% full. The problem of support on the raft is that the raft introduces a z gap, which also applied to the support in cura 2.3. This is solved in cura 2.4. The support is also printed on layers in between the raft and the model. If you print the raft with PVA you should set the z gap to zero and the initial layer overlap to zero.

The support is probably printed with the zigzag pattern, which is designed to be like the lines pattern, but all lines are connected to other lines, making for better support while still being relatively easy to remove. I've found that while the main part of zigzag or square support etc is easy to remove, there is some unremovable part still attached to the model. You get the best results using a support roof, but you need to tweak the z distance. When a move is required from support to another piece of support, no retraction is performed which causes stringing. However these strings don't touch the model.

Try Cura 2! It has settings for the order of the outer vs inner walls and for walls vs infill.

The obvious answer is to not print a prime tower. You'd be amazed how far you can get without one! Cura 2.4 has the option for a hollow prime tower, with more controlled wiping. It also comes with more temperature controls, which can further reduce oozing if printing without prime tower.

Sounds like a nice feature to add in a future release! I don't think it will make Cura 2.5, though. We're so swamped :/

You can edit the End gcode when you select a custom machine, or you could edit it by changing the youmagine.def.json file by hand in a text editor.

There is currently no option for that. Hopefully it can be added within the next year, but for the coming period we are swamped with other issues.

I don't understand the problem. Could you explain it in the clearest wat you can, please? What lines of gcode are wrong? What is wrong about that?

Print sequence has been disabled for the um3, because the move to the switching bay could move through already printed parts. These movement constraints make the existing algorithm for one at a time printing inadequate.

Are you using infill meshes in the per object settings? That's pretty cool! Which version of cura are you using? Which steps did you take to make the infill support? Try setting the global infill setting to 1% and see if that helps. Please share your model files so that we can recreate the problem.

Definitely sounds like a bug, not some esoteric feature. I can see you re using cura 2.3.1. could you post a picture of the first layer as it is in the layer view? Can you share your model so that we can reproduce the problem?

The first two layers are probably too small to be printed. You should move your model down by about 0.2mm

Gcode generated by Cura 1.15.x cannot be imported into Cura 2.x...

We're working on it. This should be fixed in version 2.4 Just to be sure: you aren't using a beta version are you? Beta versions don't update automatically...