BlondieSL
-
Posts
12 -
Joined
-
Last visited
Content Type
Forums
Events
3D Prints
Posts posted by BlondieSL
-
-
I do have the Startup Optimizer loaded. Please note that this is only used for the initial loading of Cura itself.
It has zero effect on this bug where trying to load an .STL file, whether raw or as part of a project, takes MINUTES to appear!
The optimizer can't help with that and in fact, as I'm typing this, I confirmed this by disabling the 2 options, exiting Cura 5.5 and restarting. Starting is never an issue. It always loads quickly enough.
So for clarity, this issue, which many are reporting, affects loading .STL files that take minutes to load the first time. No matter the size or complexity.
Once loaded, then we can close the STL or projects and load any other STL or project and they load instantly.
As a programmer, I can tell that there's "something" in the initial startup code that perhaps isn't loading other things that are required, OR, when trying to load an STL, the code that does that, on 1st init, is getting caught up into some loop or is "looking" for something. Interestingly enough, there's no hard drive thrashing during this point.
Again, after several minutes and it loads, any other STL files load normally and fast. No matter the size or complexity.
For that reason, when I'm going to be working with Cura a lot, I just leave it running and minimize it when not in use. I even put this Lab computer to sleep and when awakened, Cura works fine, because whatever is going on, is already resolved in memory.
I mention things that was in hopes that IF a coder see this, it might trigger some ideas.
I know how that works. LOL Been there, done that.
🙂
-
15Feb2024
I know that this is an old thread, but this problem is still here in 5.5.0.
What I've noticed is that the 1st time I try to load any STL file, it's taking 3.5 minutes or more.
Even a small, simple model, still takes that kind of time.
However, once loaded, I can remove it and drag and drop any other STIL file, big or small and it just pops up immediately!
It's clear to me that upon first launch, Cura is "doing things" or caught in some kind of loop, perhaps loading too many libraries or searching for something.
Once it's found, Cura loads any other projects just fine and fast.
To the programmers, I ask, have you looked at the initial load/run libraries or functions in Cura's code?
I know that version 5 and up are rebuilt (or that's my understanding) so the fact that this problem does NOT exist in versions 4.8, might be meaningless if the entire code has been changed.
PLEASE CURA, please find and fix what's going on. If it turns out that Cura is trying to load specific libraries, depending on a person's personal settings and/or equipment, then perhaps after the initial run, have Cura save that environment and automatically load up what is needed on first run. This could solve the problem.
-
Sadly, not working here.
Windows 10.
Cura 5.1.0
-
I know that this is an older topic, but I still see this same question about the animation (pen) speed thing, even now.
While the file is easy enough to modify to make it fast, I just don't understand why Ultimaker Devs won't just add an option for speed.
Even if a Right Click on the "pen" and then have a speed control (slider), would be great.
It's not difficult to code that.
Just a thought.
-
This is probably not helpful, but installing 4.7.1 and printing, just worked fine.
Before printing, I did go in and confirm that the "machine" settings didn't change.
They were fine.
I only mention this, because with older versions, including 4.3, which I was using all along, would screw up the odd time and do some weird things. Even without changing profiles.
What I discovered is that for some odd reason, Cura would corrupt or change some settings in the printer profile (machine).
Most often, it would change my 1.75 filament size to the larger size! For no reason.
I'm now in the habit of checking it just before saving a sliced object. Just to make sure.
-
Well, I solved this on my printer. First, I had to totally re-align the 2 bed rails. They were not even and not perfectly straight with the frame. But that isn't what fixed the shift.
What fixed my shifting problem and still being able to user higher print speeds (50-60) was to to into Cura and open up ALL the Acceleration and ALL the Jerk options.
For acceleration, my first test was to just put all the numbers down to 800. They were all at 3,000, except one that was at 5,000.
Then, for jerk, they were all at 20 so I put them all at 8.
Before doing that, on a test build, I sliced to see the time.
After the changes to settings, I sliced again to see that time.
To my great surprise, the times were almost the same. After settings added, maybe 1-2 minutes! Well worth it.
Now, SO FAR.... I've not had another shift.
As for replacing the motor, sure, perhaps a bigger, "better" motor could handle it. But the motor on mine is already very big.
It makes sense that a motor, having to move a heavy bed with a glass on it, being jerked and accelerated FAST like that, is going to slip.
I hope someone, who is having this shifting issue, tried the above and reports back.
Also, if after doing this, you find blobbing, just increase the jerk by 1 and acceleration by 50 and test. Repeat until you find that sweet spot.
I only mention this because I read somewhere that too low of these number can cause some issues like blobbing.
To date, I've not had any of that. The prints are FINALLY looking great and nice and solid.
Sure hope that helps.
-
Now months later and the problem is worse than every.
If only I could go back and never buy this P.O.S.
I replaced its glass texture hotbed with a thinner and lighter one. The orig. plate is like 1.8kg while the replacement is only 1.3kg.
It works fine if I slow the print speed down to a crawl.
But today, I started a print that seemed to be doing pretty well. I monitor my printer with a camera that I can access away from home.
Well, the print shifted 3 times!!!
So I flipped over the machine and checked tensions and such. I did notice that the 2 alignment screws where not set right, so the belt would ride on the edge of the roller and the gear (on the stepper). So I've adjusted that.
The tension seems fine.
I did tighten the screw on the gear that's on the stepper, although, that wasn't loose, really.
The ONLY other thing that I"m suspecting and this is from day 1, is that the 2 Y axis rails are not 100% aligned.
This bed has 8 rollers, 4 for each rail. There are 2 screws that adjust each side to balance off the tension on the rollers on each side.
But on one side of both, even backing off the screws to where they are loose, the 1 or 2 rollers remain pretty tight.
That indicates to me that from factory, it was never aligned right.
I'm kind of afraid to try to loosen everything up, maybe even take the rails, rollers and bed right off and try to put them back perfectly aligned. I'm afraid that I'll make things worse.
I'm about to start the printer over with new slicer settings. Slowing things down a lot. What was supposed to be about 12 hours to print is now going to be over 24, due to the slowed down slicing.
We'll see.
I so wish that I did not buy this Wanhua Duplicator 9 400 MK2.
I do hate the thing.
-
DidierKlein:
I'm also new and notice that my comments need to be approved first.
However, I just made a comment and of course, it says it needs to be approved, but I have commented before and it appears there has been no approval (unless I'm just not seeing it) as in my account, it says nothing is there.
How do we newbies know when we can start to comment immediately?
I'm assuming (and I could be very wrong) that the approval thing is for new people for a time period so that the company gets to know that the person isn't a trouble maker but a true member. That's what I suspect, but who knows!? :)
Would you please be able to enlighten me on how long before one can comment without waiting for approval or if we need to do something differently to progress to the point of no approval necessary?
Thanks in advance.
-
Today for the 1st time I had a Y axis shift at about 50% of the print.
It was not like these pictures where it's gradual. It was literally, 0 to 49% correct, then BAMN! The next layer, say 50% started over about 20mm or so!
All the build is, is just an end piece for a 2x8 piece of wood.
It's designed in Fusion 360 is is nothing more that a rectangle that is (using parameters) just slightly over the size of the wood.
It's only filleted. Other than that, a rectangle that is about 30mm "deep."
Nothing special at all.
So, I sliced it with Cura using "Draft" option. Pretty much kept defaults.
I sent it to the printer and the above happened.
I have had this before, BUT in that case, it was the print itself lost adhesion and actually moved.
In this case, it was solid.
The ONLY difference with this build and others I've done, was printing in Draft. This was the first time.
Ok, so I thought, perhaps that's the issue.
I re-sliced in "Normal", again, using mostly defaults. Just some temperature differences.
This time, it's printing just fine.
As for the printer, there is no issue with any belts, rollers, rails, drive gears, nothing. All nice and tight as they should be.
I'm just throwing this out there in case this affects someone else.
If you are printing in draft, perhaps try normal.
-
I first has auto slicing enabled.
Randomly, after changing any number at all, it would say "unable to slice", but after a few seconds it would just go ahead and slice.
I then changed from auto slicing to manual.
Then I noticed that again, the random "unable to slice" message would happen as well.
Again, changing any number, even layer height.. .anything. But not every single time.
Then I noticed if I made a change and clicked the Slice button, rather than the area changing to indicate it's going to slice, it just stayed the same.
So one would think the button didn't press and therefore, we'd press again.
This almost always caused the "unable to slice" message.
Again, it would pause for a few seconds then start to slice without an issue at that point.
Cura doesn't show STL models
in UltiMaker Cura
Posted
I was going to go into a long thing to try to explain this to you, but I'm just not going to bother.
Somehow, you seem to think that I'm saying it is easy to troubleshoot, locate and fix. I did not say that.
I'm an excellent troubleshooter when it comes to buggy code! I made an excellent living coding, including troubleshooting and bug squashing. So yeah, I have a clue of what I speak.
Perhaps I wasn't clear on an important point and this point could help the coders if they see it.
However, I highly suspect that they are already aware of this.
That is, this minutes-delay in loading the first STL ONLY happens on initial load of Cura 5.5.
Once loaded, you can load STLs instantly... any size too! I've tested it with tiny to huge. No issues AFTER that 1st long delay. Driver issues wouldn't normally cause a problem like this then just work fine after the 1st load.
Keep in mind too, as many others have reported, this is ONLY happening in Cura 5+ and not in say, 4.8. I do understand, and I may be wrong, but I think that I read that 5.x is a complete new build, NOT based on 4x code.
Since Cura 5.5 loads STL instantly after the initial load and issue, what I do now, is I just leave Cura running. I do not exit out. I just minimize.
As I'm working on new things, I can just maximize Cura (not loading again) and the STL populates instantly! EVERY TIME!
I even put my Lab Windows 10 PC to sleep when I'm done for the day, and next time I come back to it, I wake up Windows, it does its thing and I can maximize Cura again. I will say too, Cura handles sleep/wake perfectly! Some software does not!
So once maximized again, (not reloaded) STL files appear instantly.
For experienced coders, that info is significant. I get that for inexperienced coders, it may be meaningless. I get that!
So please do not make assumptions when it comes to my decades-long experience in coding! I'd appreciate that a lot.
Not that it matters, but I started coding in the late 1970s in several languages.
As for jumping on board to assist, I would so love to. I really do miss the team environment.
Sadly, I just do not have the time cycles to dedicate to the project. I seriously wish that I did!!!
The fact that I just don't have time to dedicate to something like this, doesn't mean that I can't comment here and there! That is, after all, what a forum is for! 🙂
At this point, this particular thread is closed for me, in that, there's no need for me to go on and on. I know what I know.
Seriously, no point to it in this manner.
Thanks for the interest anyway. I do appreciate it.
Keep up the good work!