yellowshark

That is true too

Yup 2.4 is very poor compared to 15.n in terms of placement; but I must say auto slicing has not stopped me moving copies around the bed.

Actually I think it is. I think what @DaHai8 was saying was that if you use PrintBite you do not have to squish the filament down so hard and so the dimension of the lower layer will not be extended - ofc I may be wrong!!

Lordy well I am glad I did not admonish you for putting your t-glase in a furnace, which I almost. I have just looked at their site and see that the 212c they recommended was a misprint and it should be 235-245. No wonder I could never get the stuff to sick on the bed and so gave up!!!

Not necessarily. I understand why you are saying that and until a month or so ago I would have agreed. But I had a similar problem with a part recently which had openings on each side for a belt and then a larger solid middle piece. The infill on the first layer around the narrow outer side of the belt slots was fine but when the infill in the middle started it gradually ended up like the first two pics above (not quite as bad maybe). It took me a long time to work out what was going one and it was due to the nozzle being being too close to the bed. I am not saying that THAT is the problem, but it is worth checking.

Nice one; I need to give that a try. I rarely print 3rd party designs so if I know I need to really squish the part down, I automatically reduce the dims of the bottom .3mm of the model and then it comes out fine. Of course if I can use a brim then all that is not needed.

We have similar threads going. Yes this is where it is stored but on my laptop with Cura 2.4 release this is not the file that Cura is using. So the start gcode changes I am making are not being used by Cura even though they have been stored in this file in ...cura/machine-settings

Hi @ahoeben. I just tried that but it still did not update. I investigated a bit more. I checked the printer file abc_settings.inst.cfg in folder ....cura/machine_instances and saw that the timestamp for the file had been updated. I opened the file and saw that my changed gcode statement had been saved correctly . I then loaded a model and checked the generated gcode and this was using the old gcode not the new gcode stored in the ....settings.inst.cfg file. Double checking the machine settings in Cura, they were showing the old gcode. So it seems like the settings are being updated but the file that is saved by Cura is not the file that Cura is using.

Yup I agree, that looks like the results you get when the nozzle is too close to the bed.

This was OK with the beta versions of 2.4 but does not work with the Release. I installed 2.4R and setup my custom printer – actually the sequence was 1. Install 2.4R; 2 delete my custom printer files abc.stack.cfg and abc.settings.inst.cfg from the …cura/machine_instances folder ; 3. setup my custom printer definition including importantly my start and end gcode statements– and everything works. BUT I cannot modify the gcode statements once setup, i.e. I change them, hit the Close button but they are not saved. All the Settings above the gcode boxes are saved if they are changed. If I change the nozzle size and a line of gcode and hit the Close button – when I redisplay the printer settings, the new nozzle size is displayed but the gcode change is not there. Currently I am changing my z offset statement frequently so this is a real pain as I have to remember to change it in the gcode file. Fyi @nallath

Also if you can put a filet on that bottom edge, I find that helps with removal and if necessary masking the deburring, as does using a very high quality file. If dimensional accuracy is important, constraining you with just how much you can squish that 1st layer into the bed, a brim is the best solution imho. But yes it can add work and ruin an edge if you are sloppy.

It does not answer your question but if you save your settings to a unique name every time you create a gcode file then you will always have the settings available to you, apart from any changes you made to the printer settings such as start gcode, gcode flavour and nozzle size

Yup good idea, unfortunately I do not think it will fit between the object and my lovely brim, 8)

There are other fan settings - suggest you go to visibility settings and turn them all on and then you will see what your settings are - e.g. at what layer height do fans reach 100%. There are 11 Cooling options and you are only looking at 4 of them. 8)

You need to print Ngen hotter than PLA, in my case about 45 degrees hotter. It would help us if you told us your settings.

They are not really print head dimensions. The smaller grey oblong is the area that you are printing, I assume you are using a brim. The larger grey oblong is there because you have selected "Print one at a time". If you change that momentarily to "Print all at once" you will see the larger grey oblong disappear. If you select "Print one at a time" then Cura will spread out your models to ensure that when you print the 2nd model the print assembly does not hit your 1st model - not relevant if "Print all at once" is used. The grey area represents a no-go area as far as another model is concerned. The size of the larger grey oblong is determined using the dimensions stored for your printer and yes you would want to change those if you are using a non UM printer - as per @SandervG instructions above. Whether or not the larger grey oblong is exactly the same as your print dimensions I know not, but they will be close.

Well we probably have to agree to differ! " If the new Cura overrides the old one, this would be a justified note to include" I absolutely agree this should be there. "There can be only one!" This is not true and IMHO should not be stated, otherwise users will understandably take it as being true. Using a 2nd account is not a hack, it is using Windows capability. It requires no code or other funny things that most users would not understand. It just needs a paragraph in the installation instructions - which do not exist!! - explaining how to install a new version without losing the current version; which I personally find comforting when dealing with Beta software and indeed any new release which by definition will always introduce bugs.

Hmn well it takes about 10secs to save an STL file from Solidworks and another 10secs to load the STL into Cura, hardly a big deal. I would rather have my model sliced by software built by a dedicated 3D slicer team than by fundamentally an engineering team providing an add on to their software. Of course what they could do is just add an invoking function and pass the model (converted to STL) direct to Cura. Repetier Host has been doing that for a number of years to Slic3r, Kisslicer and Cura - of course from an stl file not an sldprt file.

Well actually not true, there can be more than 1 - as suggested by someone else recently - not my idea. I know because I tried and it worked. Create or use another existing account and install the 2nd version under the 2nd account, This provides a second separate appdata folder for Cura with all the settings. No idea if you can actually have both Cura versions loaded at the same time.

Yup I have been caught out by that too, assuming it is saving .stl files. IMHO it makes more sense to default to .stl file type. I will change settings a number of times and when I am happy then save the project.

Cura can certainly produce a result comparable to the piece on the rhs. Well 15.n could and I am sure 2.4 can, probably more so. A picture is great but it would help to know what your settings were, primary settings and detail retraction settings, to help debug the problem

Ahem, back it up first otherwise you will lose any printer or settings profiles that you created with 2.4 beta and, I suspect but not sure, 2.3. Obviously if you are coming from 15.n or 2.1? not relevant

Do not forget that patents stopped the development of an Ultimaker and other RepRap style printers until just a few years ago when the patents ran out

Yup Repetier Host. I have used it for 3 years now. In Cura go to your printer definition and set the gcode flavour to Reprap - probably the Marlin/Sprinter version. Then save your stl to disk and then load it into Repetier then start the printer within Repetier and away you go. You will need to do some configuration but pretty simple. I guess you may find config sample for your printer on the Repetier website. You need to

Hi @nallath I have just lost my customised printer definition from 2.4Bete 2 again. Above you requested log files. What/which exactly do you need and where will I fine it/them. Using Win10