burtoogle

OK, good. I will post a new build later today that has the fix.

Hello @kulfuerst, glad to hear that has done the trick. The problem is caused by very short skin and infill lines being generated by the slicer. Some time back, I suggested to the Cura devs that we filtered those out but they didn't go along with that. I can't remember why, now. So, all I can do is put the fix into my Cura builds which you are welcome to try and submit the fix to the devs with the hope that they accept it. As I still have quite a few contributions outstanding, I don't hold out much hope of the fix being accepted any time soon.

But no, I had to stay up and hack some more! I think I have found the reason for the extraneous travels. Please print the attached gcode which in all other respects should be the same and let me know if it is better. AI3M_Logo2.gcode

I think that red highlighted box is a "red herring" as it also appears when I look at a similar report for other printers. Tomorrow, I will try and find out why I cannot slice your project. Now it's bedtime!

I'm sorry, I can't currently slice your project as Cura says there is some problem with the settings. I don't think it is your project file that's wrong. Maybe it's the printer definition or because my Cura is on the "bleeding edge". If any Cura devs read this, here's something that could be relevant... EDIT - oh, no, I see that other printers have similar red region so I gues that's not relevant to this problem. Meanwhile, all I can suggest is that you try enabling combing (use mode not in skin). Sorry I can't be of more help right now.

Hello @kulfuerst, please attach the project file (File -> Save). I need that to see what setting you are using. Thanks.

The fix is now merged into Ultimaker/master so you don't have to use my repo. Looking at your log, you have other problems: 2019-07-26 15:51:32,769 - ERROR - [MainThread] UM.Logger.logException [84]: Exception: Import error loading module USBPrinting 2019-07-26 15:51:32,769 - ERROR - [MainThread] UM.Logger.logException [88]: Traceback (most recent call last): 2019-07-26 15:51:32,769 - ERROR - [MainThread] UM.Logger.logException [88]: File "/usr/lib/python3.7/site-packages/UM/PluginRegistry.py", line 539, in _findPlugin 2019-07-26 15:51:32,769 - ERROR - [MainThread] UM.Logger.logException [88]: module = imp.load_module(plugin_id, file, path, desc) #type: ignore #MyPy gets the wrong output type from imp .find_module for some reason. 2019-07-26 15:51:32,769 - ERROR - [MainThread] UM.Logger.logException [88]: File "/usr/lib/python3.7/imp.py", line 244, in load_module 2019-07-26 15:51:32,769 - ERROR - [MainThread] UM.Logger.logException [88]: return load_package(name, filename) 2019-07-26 15:51:32,769 - ERROR - [MainThread] UM.Logger.logException [88]: File "/usr/lib/python3.7/imp.py", line 216, in load_package 2019-07-26 15:51:32,769 - ERROR - [MainThread] UM.Logger.logException [88]: return _load(spec) 2019-07-26 15:51:32,770 - ERROR - [MainThread] UM.Logger.logException [88]: File "<frozen importlib._bootstrap>", line 696, in _load 2019-07-26 15:51:32,770 - ERROR - [MainThread] UM.Logger.logException [88]: File "<frozen importlib._bootstrap>", line 677, in _load_unlocked 2019-07-26 15:51:32,770 - ERROR - [MainThread] UM.Logger.logException [88]: File "<frozen importlib._bootstrap_external>", line 728, in exec_module 2019-07-26 15:51:32,770 - ERROR - [MainThread] UM.Logger.logException [88]: File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed 2019-07-26 15:51:32,770 - ERROR - [MainThread] UM.Logger.logException [88]: File "/usr/lib/cura/plugins/USBPrinting/__init__.py", line 4, in <module> 2019-07-26 15:51:32,770 - ERROR - [MainThread] UM.Logger.logException [88]: from . import USBPrinterOutputDeviceManager 2019-07-26 15:51:32,770 - ERROR - [MainThread] UM.Logger.logException [88]: File "/usr/lib/cura/plugins/USBPrinting/USBPrinterOutputDeviceManager.py", line 6, in <module> 2019-07-26 15:51:32,770 - ERROR - [MainThread] UM.Logger.logException [88]: import serial.tools.list_ports 2019-07-26 15:51:32,770 - ERROR - [MainThread] UM.Logger.logException [88]: ModuleNotFoundError: No module named 'serial' Also... 2019-07-26 15:51:32,773 - ERROR - [MainThread] UM.Logger.logException [84]: Exception: Import error loading module AMFReader 2019-07-26 15:51:32,774 - ERROR - [MainThread] UM.Logger.logException [88]: Traceback (most recent call last): 2019-07-26 15:51:32,774 - ERROR - [MainThread] UM.Logger.logException [88]: File "/usr/lib/python3.7/site-packages/UM/PluginRegistry.py", line 539, in _findPlugin 2019-07-26 15:51:32,774 - ERROR - [MainThread] UM.Logger.logException [88]: module = imp.load_module(plugin_id, file, path, desc) #type: ignore #MyPy gets the wrong output type from imp.find_module for some reason. 2019-07-26 15:51:32,774 - ERROR - [MainThread] UM.Logger.logException [88]: File "/usr/lib/python3.7/imp.py", line 244, in load_module 2019-07-26 15:51:32,774 - ERROR - [MainThread] UM.Logger.logException [88]: return load_package(name, filename) 2019-07-26 15:51:32,774 - ERROR - [MainThread] UM.Logger.logException [88]: File "/usr/lib/python3.7/imp.py", line 216, in load_package 2019-07-26 15:51:32,774 - ERROR - [MainThread] UM.Logger.logException [88]: return _load(spec) 2019-07-26 15:51:32,774 - ERROR - [MainThread] UM.Logger.logException [88]: File "<frozen importlib._bootstrap>", line 696, in _load 2019-07-26 15:51:32,774 - ERROR - [MainThread] UM.Logger.logException [88]: File "<frozen importlib._bootstrap>", line 677, in _load_unlocked 2019-07-26 15:51:32,775 - ERROR - [MainThread] UM.Logger.logException [88]: File "<frozen importlib._bootstrap_external>", line 728, in exec_module 2019-07-26 15:51:32,775 - ERROR - [MainThread] UM.Logger.logException [88]: File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed 2019-07-26 15:51:32,775 - ERROR - [MainThread] UM.Logger.logException [88]: File "/usr/lib/cura/plugins/AMFReader/__init__.py", line 4, in <module> 2019-07-26 15:51:32,775 - ERROR - [MainThread] UM.Logger.logException [88]: from . import AMFReader 2019-07-26 15:51:32,775 - ERROR - [MainThread] UM.Logger.logException [88]: File "/usr/lib/cura/plugins/AMFReader/AMFReader.py", line 20, in <module> 2019-07-26 15:51:32,775 - ERROR - [MainThread] UM.Logger.logException [88]: import trimesh 2019-07-26 15:51:32,775 - ERROR - [MainThread] UM.Logger.logException [88]: ModuleNotFoundError: No module named 'trimesh'

You may be interested in these discussions: https://github.com/smartavionics/Cura/issues/8 https://github.com/smartavionics/Cura/issues/11

Hi @kulfuerst, glad that was useful. If you have further suggestions it's probably best to either create a thread here or open an issue at https://github.com/smartavionics/Cura.

Hello @johnse, thanks for that info. However, I doubt if I can summon the enthusiasm to investigate that. Getting an OS X build working in the first place was a PITA so I will stick to Windows and Linux builds from now on. If anyone else can be bothered to do it, the source code is all available.

Hello @litwi, it sounds like there are problems with the model. Could you either attach the model file to this thread. Alternatively, install the mesh tools plugin from the cura marketplace and check the model to see that it is actually printable. Thanks.

Hello @SysGhost, I have been working on this issue and think I have a solution. If you are using Cura from source could you please try using the mb-master branch in git@github.com:smartavionics/Uranium.git and see if it fixes the problem. Thanks. Alternative URL for repo is https://github.com/smartavionics/Uranium.git

A new feature of the 4.2 (beta) release is that you can set the flows for features individually. So using that you could crank up the inner wall flow...

For me, the red line always points in the +ve X direction (aka right) and the green line in the +ve Y direction (aka back).

Hi @MarissaP, thanks for the file. I recommend the following changes: 1 - set the outer wall wipe distance to 0. 2 - set the min wall flow to something like 50. You may also wish to reduce the max resolution setting from the default value to something smaller as that will make the z-seam wander around less. Hope this helps.

Hello @MarissaP, please save the project file (File -> Save) and attach the .3mf file to this thread. Thanks.

Not entirely true. The Cura developers are working on improving the wall gap filling and thin wall printing. In the meantime you could try one of my builds that has a completely different implementation of those features and, generally, works a lot better. You can find my builds (Windows and Linux only, sorry) at https://www.dropbox.com/sh/s43vqzmi4d2bqe2/AAADdYdSu9iwcKa0Knqgurm4a?dl=0. Hope this helps.

TBH, I don't seriously expect Ultimaker to embark upon a(nother) major rewrite of Cura. But I still think that there's a case for creating a browser based UI that will reliably work across all platforms (that support WebGL). I'm gonna keep thinking about that...

No, I'm not suggesting that the profiles & definitions are handled in the browser. You could still have a python app like now except the UI would be browser based and use WebGL (or whatever it is called) for the 3d part. The app would be a web server that you just point a browser at.

Over and over again, we see people having problems with OpenGL and graphics drivers, etc. On all platforms. It occurs to me that Cura would be much improved by moving the entire UI into a browser and use the browser's native 3d graphics capabilities to do the heavy lifting. You could still keep all the python config stuff (or not, it would be a lot of work to replace it all). But all of the Qt and PyQt stuff could be replaced with web technology (HTML, Javascript, etc.) Solve a lot of problems and make remote access a doddle. Discuss.

Thanks for the file @cerons. It only contains the model and not the settings (you need to do File -> Save to save the settings and the model). Anyway, the model has problems. The mesh tools say it's not watertight (bad news for a water slide!). To be printable, the model needs to be watertight.

Ah, I just realised that you probably want all the lines printed in the same direction (i.e. bottom to top) but even when setting the directions as I mention above, alternate lines are printed in opposite directions (i.e. first line bottom to top, 2nd line top to bottom, etc.)

You can set the direction of skin and infill lines. By default, the skin lines are at +45 and -45 degrees but if you change the top/bottom line directions to [0] then all the skin lines will be printed at 0 degrees. Similar for infill. Hope this helps.

Hello @cerons, it's hard to tell looking at your images exactly what is wrong. My first guess is that the model is too thin compared to the line widths, layer height, etc. It would help a lot if you could save the project file (File -> Save) and attach the .3mf file to this thread. Thanks.

Here's the system it was built on. Very nice case from thingiverse sliced without top/bottom skins, just gyroid infill. The SSD wasn't actually used during the build as all files were on the SD card.