burtoogle
-
Posts
1,529 -
Joined
-
Last visited
-
Days Won
19
Content Type
Forums
Events
3D Prints
Posts posted by burtoogle
-
-
If Cura 4.6 has the overhanging wall angle setting, try reducing that so that it detects the overhangs and then it should move the z-seam to avoid the overhung areas.
-
1
-
-
Thanks for the new file. I sliced that and can see that weird section but if you put surface mode back to normal then it comes out better. There's still an odd flat section but at least there's less weirdness. Hope this helps!
-
Hello @summerso, welcome to this forum. The file you provided isn't actually a project file, it only contains the model and not your settings. You need to do File -> Save, not File -> Export to create a project file (I know it's confusing, they like it that way!)
Anyway, I sliced your model using my Cura variant and I think it looks OK, there's no weirdness near the top and almost 0 travel moves in the whole file. Mind you, my Cura works somewhat differently to UM Cura so I can't guarantee that you will get the same results using UM Cura. If you wish to try mine, you can find the releases at https://www.dropbox.com/sh/s43vqzmi4d2bqe2/AAADdYdSu9iwcKa0Knqgurm4a?dl=0. Please read the README.md file before installing and using.
-
Good.
-
-
I still don't know why it is failing for you. You could possibly get more information by setting the LIBGL_DEBUG environment variable (set to "verbose" to get maximum info).
-
Set top surface skin layers to 1 (or more) and then the experimental setting top surface skin pattern becomes visible and you can set a different pattern for the very topmost skin(s).
-
2
-
-
But compatibility mode is also used if the Open GL version is less than 4.1. Take a log at the cura.log file and you will see what version is being detected. Maybe a driver update is required?
-
1
-
-
Thanks for the g-code. I can't see anything there that would make the nozzle go back to a corner on each layer.
The only big travel moves are on the first layer.
-
Hello @z-uo, please attach a sample g-code file to this thread so I can see the weird movement you describe. Thanks.
-
Maybe it's a group permissions thing, this is what I have for me...
uid=1001(markb) gid=1001(markb) groups=1001(markb),4(adm),27(sudo),44(video),107(render),109(netdev)Are you a member of the render group?
-
Hi, a possible solution would be to install my Cura that has an extra option to enable bridging over support.
You can find my builds at https://www.dropbox.com/sh/s43vqzmi4d2bqe2/AAADdYdSu9iwcKa0Knqgurm4a?dl=0
Please read the README.md before using.
-
Hi. Looks perhaps like a permissions problem. The files under /opt/mesa-20.1 should be readable and executable by everyone.
-
Hi, that A parameter is specific to the MACH3 gcode flavour. It replaces the E parameter that almost all other printers use to specify extrusion distance.
-
The cura gcode uses 150 mm/S for the travel speed, the S3D code uses 80 mm/S. Try using the same speed in Cura.
-
Hi, I can't see anything wrong with the g-code, could you please provide the g-code that S3D produced so I can compare them. Thanks.
-
Hi, please attach the leaning g-code file to this thread, thanks.
-
56 minutes ago, hussainsail2002 said:
Will it work on windows 7 ?
Sorry, I don't use Windows so I cannot say. I expect someone else will know.
-
That feature is only available if your computer can provide a recent enough version of Open GL. The Open GL version supported needs to be 4.1 or later for this and the full preview mode (with the layer and line sliders) .
-
6 hours ago, j_keiter said:
I still think cura should fix though.
I have submitted a fix to the Cura devs and they will decide whether to incorporate it or not.
-
However, if you were running Linux on that laptop, it could possibly support Open GL 4.2 which would allow you to use the simulation view.
-
I don't think there's anything you can do to alter the behaviour. I have modified the slicer so that it will force the retraction to
occur on that last travel move and sliced your project, I attach the gcode, could you please print it and let me know if it is good. If so, I will submit my changes for the UM devs to include in a future release (if they approve).
-
The UM devs changed the behaviour fairly recently so that Cura never generates a retraction when the travel distance is less than the minimum travel distance setting. This is true even when retract on layer change is set. Maybe there is a case for allowing the retraction in that situation to help with the slow z change.
-
Ah, I think I know what the problem could be, looking at the gcode for the missing retraction just before LAYER:5, the distance travelled is less than the value of retraction minimum travel so the retraction doesn't occur. A workaround would be to reduce the value of that setting.
Could you still please provide the project file, thanks.
Surface Mode Spiralize - Random direction change
in UltiMaker Cura
Posted
Spiralize isn't right for a model with gaps.
Why don't you just cut it out later?