burtoogle
-
Posts
1,529 -
Joined
-
Last visited
-
Days Won
19
Content Type
Forums
Events
3D Prints
Posts posted by burtoogle
-
-
Thanks for the file. Looking at the gcode you can see that the model is not totally solid. There's an inner ring and the threads are not connected to it. Here's a slice through the gcode that shows what I mean...
I would have expected to only see walls on the inside and outside of the part with infill between the walls. It looks like a modelling problem to me.
-
1
-
-
Can you please attach sample gcode for a good thread print and a bad thread print? Thanks.
-
INSTALL_DIR is set to where I install everything needed (Qt, SIP, etc.) to build Cura.
-
Hi, when I build Cura on Windows, I run this script first
call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64 8.1 set INSTALL_DIR=%HOMEDRIVE%%HOMEPATH%\cura\inst set INSTALL_DIR_UNIX=%HOMEDRIVE%/Users/%USERNAME%/cura/inst set PATH=%INSTALL_DIR%\bin;%PATH% set PATH=%INSTALL_DIR%\scripts;%PATH% set PATH=%INSTALL_DIR%;%PATH% set PYTHONPATH=%cd%\inst\lib\python3.5\site-packages set PATH=%cd%\inst\bin;%PATH% set CURA_BRANCH_OR_TAG=mb-master set CURAENGINE_BRANCH_OR_TAG=mb-master set URANIUM_BRANCH_OR_TAG=mb-master cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_PREFIX_PATH=%INSTALL_DIR_UNIX% -DCMAKE_INSTALL_PREFIX=%INSTALL_DIR_UNIX% -DBUILD_OS_WIN64=ON -DCPACK_GENERATOR=NSIS -G "NMake Makefiles" -DCURA_VERSION=mb-master ..Some of that is specific to my builds (mb-master branches) but the initial call to vcvarsall.bat could be useful to you?
-
It sounds like either Cura is not writing to the SD card correctly or that the printer is having a problem reading the SD card?
-
Hi @hardlyneutral77, if you save a gcode to SD card from Cura and then read it back on the PC is it byte-for-byte the same as the gcode saved to the local hard drive?
-
You may wish to try one of my Cura builds as they support lower resolution versions of the TPMS infills (including gyroid). My releases can be installed alongside the UM releases without conflict. You can find them at https://www.dropbox.com/sh/s43vqzmi4d2bqe2/AAADdYdSu9iwcKa0Knqgurm4a?dl=0 Please read the README file there before using.
-
12 minutes ago, ChaosBlades said:
So you are saying because it is 3 line widths instead of 4, that is the issue?
Yes.
13 minutes ago, ChaosBlades said:Do you know the GitHub issue number, so I can track progress?
AFAIK, there isn't an issue on github specifically about this.
The PR that could form the basis of the solution is https://github.com/Ultimaker/CuraEngine/pull/1210
You can see from the comments there that it still has some way to go before becoming a reality.
-
1
-
-
This is all known behaviour for Cura. It cannot at this time make a good job of walls that are not close to an even number of line widths wide. I believe that the Cura devs are addressing this long standing deficiency.
-
Sorry, I don't know much about models, I expect someone else could answer your question.
-
The problem is that the model's normals are wacky, install the cura mesh tools plugin and use it to fix the normals and then you should be OK...
-
Hi, your model has a problem, this is what Cura mesh tools says...
-
Hello, could you please attach the model(s) that you are having problems with, thanks.
-
If you are using combing, set the max comb distance with no retract to something like 10.
If you are printing PETG you may find that turning off combing completely is best.
-
Hi, sorry for the slow response, it's been a busy day. So, I think this behaviour has been introduced by a recent revamp of the retraction/z-hop code. Arguably, it's a regression. The only workaround I can suggest is to turn off z-hop. For this particular print, that's of no consequence (I think) because it doesn't appear to do any other z-hops in the print. I recommend you open an issue at the cura github as this should get a proper fix.
-
1
-
-
Hi, could you please save a sample project file (File -> Save) and attach the .3mf to this thread, thanks.
-
Yes, I was confused because I thought you were referring to the blue layer, I couldn't see the infill in the walls (crap eyes).
-
Comment deleted.
-
You have done "sudo apt-get install libgles-dev" haven't you?
I can't think of anything else that would cause a problem.
-
Hello @flyhh, it's just the normal Buster (aka debian 10).
What happens when you try to run the image?
-
1 hour ago, JohnRuthroff said:
Could Tinkercad be the issue?
Perhaps. This often happens if the bottom of the model is not completely flat. Try sinking the model into the buildplate slightly by setting its z value slightly negative.
-
Have you tried using the max comb distance with no retract setting?
-
That's a good point. I don't think I mention that in my README so I'll add a comment.
Personally, I keep all of my configuration files in a git repo and every now and again I make a snapshot so I can recover if anything gets trashed. I have had to rewind a few times due to upstream changes causing breakage but that's the price to pay for living on the edge....
-
Sorry, I don't know the answer to your question but in that regard, my releases should be the same as the recent UM releases. So if it is true for them, it will also be true for my releases.
"Open Recent" on Cura 4.5.0 in Linux not updating
in UltiMaker Cura
Posted
I noticed this also. What I have recently discovered is that on Linux, Cura saves the cura.cfg file to ~/.config/cura/RELEASE/cura.cfg but when loading the file it will load it from ~/.local/share/cura/RELEASE/cura.cfg if that file exists. I think this is a bug and I just deleted the old cura.cfg.