JCD

You will have a much better work with PSPAD.exe

look at the fdmprinter.def.json file in the definition folder of the cura forlder with a text editor search for the text you have in the parameter list on the right of the cura window, this text appears in the label parameter and what you want is just before the ':{' sample "speed_wall_x": { "label": "Inner Wall Speed",

If you want to change this behavior, open the fdmprinter file in the definition folder in the cura folder, with a text editor. 1) look for the text : "speed_wall_x": 2) a few lines below, you can see the text : "value": "speed_wall * 2", 3) change the 2 by the text 1.5 save the file That's it ! This has to be done each time a new version is used, otherwise, you have to create a new definition file , overrriding these values

It would be nice if you give the 2 gcode files, the default one and one you sliced with Cura, just to see what Z coordinate are set in both files at the beginning Your printer has an auto leveling at the beginning, did you correctly check it in the case you're slicing with cura?

@gr5 Yes I have a glass on my heated bed, but with PLA I use a bed temperature of 37° (with a really tiny spray of repositionable glue) with a brim to prevent - The warping effect - The 'Elephant Foot' effect you're describing (the higher the bed temp is, more elasticity the first layer (and a little the following layers above it) has and so naturally is leaking outside the model if there is no border)

When you are not on the 1st layer it could be dangerous to sloww down the speed, specially when you begin the top layers, which may be above an empty zone (in an infill). If the speed is too slow the filament is not making a 'bridge'. This bridge (even in low quality) is used to build the upper top layers above. Those layers hide the low quality of the bridge

excellent ! and if implemented i'll use it (only for the 1st layer) !

@smartavionics the problem looks excatly the same but is your link for an existing plug-in ? Furthermore i think this is mainly for the 1st layer as the adhesion is much better material on material than material on build plate . The advantage is to modify only the first layer GCode

This is a real question, and I ll say the reason is the low adhesion on the build plate resulting of the 'angle-dragging effect in the tiny circles'. If you look at the filament on the build plate when a tiny circle (diameter < 4 mm) is printed, you can often see that the filament is 'dragged' by the latest filament exiting the nozzle, which is going in a direction sligtly different. As the circle is made of tiny lines with a little angle between them (the meshes), the dragged effect is cumulative as after the first tiny angle there is almost at once a new deviation in the same way ... and so on So the filament is moving 'inside' the circle and if the effect lasts there is a non adhesion of the circle. You have not the same effect when there is an angle like in a square, as the new direction (at 90° form the preceding one) is lasting for a while. The filament in the new direction has the time to cool and stick to the plate, so the angle dragging effect occurs in this case only once during the first 0.1-0.2 mm and after it doesn-t move. It is the same for the larger circles as the length of each mesh (and/or the angle between meshes is smaller) in the circle gives the time for the adhesion to prevail over the angle-dragged effect. So the solutions would be : 1) lower the speed for the bottom layer, a kind of 'brutal force' solution 2) via a plugin lower the speed in the 1st layer for each movement in a wall with an extraction length below a certain value, indicating that the mesh is really tiny and there is a risk of angle-dragging It would be fine if the team implement the second solution in CURA

here are the system informations I have presently with Cura and Firefox running For the performance Firefox has the worst effect sometimes, with a lot of windows opened in firefox, it can reach 500-600K in memory usage

Cura is starting in 25 seconds, it's not so bad but longer than other software And windows is starting in 22 seconds

Here is a picture of my system control panel

Myself i have Cura 3.4 - Slice automatically unchecked - no check for updates at start up - no printing information sent - I have suppress 90% of printers and materials and 70% of quality profiles Windows 7 64 bits, 4GO Ram, SSD disk drive 250GO Start up last less than 30 seconds For the team, I think it would be very nice to clearly show when the User has clicked on the 'prepare' button that Cura is working. Currently, you have to wait until the slicing bar is moving to see that Cura is really working, which can be a long ...long time if the STL File is large

I work on Cura 3.4 windows7 with an Anet A8 printer (1.75mm platic materials) If I duplicate one of the generic materials (ABS as example on the picture below) there is a configuration error happening ! Do'nt click on the Reset Button or you'll loose all your settings ! This error involves the cartesio as you can see . You can avoid this type of error by 2 ways 1) Remove the cartesio definition file in the definition folder of the cura ressources folder 2) Modify the generic material file, removing inside all the lines between the <machine> and </machine> tag I think there is a conflict between the definition files and the generic material files

Have you try to make a hole in your model up to the flat part and insert a big screw inside ?