Kvanwem
-
Posts
10 -
Joined
-
Last visited
Content Type
Forums
Events
3D Prints
Posts posted by Kvanwem
-
-
Using the same test file
5.2.1 - Infill is causing the slow issue. I set to 100%, slices in about 15 seconds. Set to 20%, >5 minutes (regardless of pattern).
5.0 - Same settings (recommended) with infill at 20%, about 20-25 seconds
4.13.1 - Takes 20-25 seconds
-
Cura 5.1 - 5.2.1 are extremely slow slicing anything but simple models. Same model, same settings, take 30 seconds in Cura 5.0 and 4.x, but takes over 5-10 minutes in anything above 5.1. (yes, I have uninstalled and reinstalled, rebooted, tried a different computer, all the same). Cura 5.x has become useless. It also is using excessive CPU cycles.
Preemptive: No, it's not my computer.
-
4 hours ago, Kvanwem said:
This issue has been going on for me since I bought the S3. I have spent more time clearing jams than printing with the material. I think I'll try what Rachael7 suggests and order some of the BASF BVOH and see how that works.
I am in AZ so I think that the PVA gets dried out making it more brittle. I would sure like to know how Ultamaker did the print in the demo video without a failure. I guess if you can put this in a strictly controlled environment it may work.
I was pondering this whole PVA breaking thing and thought what if I warmed it up first? I took a piece and hit it whoth a heat gun and, as expected it became more pliable. So I put the spool on the build plate and set the temp to 60-C, let it warm up for 10 minutes or so and it appears to have worked.
I am at the end of a 4 hour print of an articulated Rocktopus (don't ask), and the PVA is working great with no breaks or jams. Perhaps warming it acted as a tempering, removing some of the stresses in the coils.
Hope this hope this helps someone.
-
On 5/4/2022 at 12:30 AM, nallath said:
That was a bug, which has been fixed already for the final release 🙂
From wikipedia: " A beta phase generally begins when the software is feature complete but likely to contain a number of known or unknown bugs.[9] Software in the beta phase will generally have many more bugs in it than completed software and speed or performance issues, and may still cause crashes or data loss."
The 5.0 beta is feature complete, but as you have found contains some issues that we have not encountered during our tests. Software systems have become so complex that it running on all of our systems is no indication that it runs on the others. That is also why we kindly ask people to test it.Alpha[edit]
The alpha phase of the release life cycle is the first phase of software testing (alpha is the first letter of the Greek alphabet, used as the number 1). In this phase, developers generally test the software using white-box techniques. Additional validation is then performed using black-box or gray-box techniques, by another testing team. Moving to black-box testing inside the organization is known as alpha release.[3][better source needed]
Alpha software is not thoroughly tested by the developer before it is released to customers. Alpha software may contain serious errors, and any resulting instability could cause crashes or data loss.[4] Alpha software may not contain all of the features that are planned for the final version.[5] In general, external availability of alpha software is uncommon in proprietary software, while open source software often has publicly available alpha versions. The alpha phase usually ends with a feature freeze, indicating that no more features will be added to the software. At this time, the software is said to be feature complete. A beta test is carried out following acceptance testing at the supplier's site (alpha test) and immediately before the general release of the software as a product.[6]
In general an alpha version or release of a software package intends to do something particular, mostly does so, yet isn't guaranteed to do so fully.
-
This issue has been going on for me since I bought the S3. I have spent more time clearing jams than printing with the material. I think I'll try what Rachael7 suggests and order some of the BASF BVOH and see how that works.
I am in AZ so I think that the PVA gets dried out making it more brittle. I would sure like to know how Ultamaker did the print in the demo video without a failure. I guess if you can put this in a strictly controlled environment it may work.
-
1
-
-
Yep, understanding this is a "Beta" and there will be some issues, I wasn't expecting "Unusable".
I run dual monitors, program splash screen loads on second monitor, program opens off screen on primary monitor.
Other issues cascaded from this bug report.
1. Accessing the "Help: About" menu to access version information freezes the program requiring "end task" to close. The "About" popup in hidden and never visible
2. Additionally, when in the frozen state, the GPU is at 10% (Very high compared to Cura 4.x.x at .05%), CPU Usage at >10% Cura 5.0 is a resource hogThe only instance I know of that would be using the GPU when idle is crypto mining. I'm not saying that's what 's happening, but this is being removed from my system.
This is more of an Alpha release, but given the way things are in today's world, it seems that SW designers shove incomplete products out and let users do the debugging.
-
I live in AZ so my humidity is 22-30% typically (indoors). I also store my filaments in a vacuum sealed bag with desiccant, similar to how they come from Ultamaker. It seems that the PVA dries out naturally (the spool is about a year old).
The PVA is now so brittle that it breaks at the feeder due to feed roller pressure when adjusted to center point as recommended, as soon as the tension lever is closed, the PVA snaps. I backed it off to minimum pressure, which helped a bit , but is is still happening. I can hear the "Snap" from 12' away across the room. It has taken 2 days to do a 1 hour print (about 10 prints aborted because on "Resume" the #2 print head resumes .5" off center and destroys the partial print).
I need to figure out how to get some moisture back into the PVA to make it more pliable so it doesn't snap.
When I bought this printer it sounded like a great idea, to me this is a case of over promised and under delivered (as far as the PVA is concerned). I have 4/5 of a spool that will have to be discarded ($50 wasted).
-
On my S3, the PVA constantly breaks at the feeder. It is extremely brittle and I've had it actually break when trying to take out the natural curl when loading it.
Running a simple print today and it has broken 3 times inside of 15 minutes.
I have heard that it "Dry's Out" , which I find curious since it is recommended that it be kept in a humidity free environment so it doesn't absorb moisture.
You can see where it is actually cracked in the center of the tube...
-
My printer is on the other side of the room, so it would be nice if, when you abort a print you didn't have to walk over to the printer and confirm that you stopped the print. Seriously, when monitoring the print it would be somewhat miraculous to open the "manage in browser', click the ellipsis, and select abort print...by accident. Even if they did, why can't there
be a popup that asks (like the printer) "Really?".
The other nicety would be to confirm removal remotely. I have had instances where I confirm on the printer, go back to the computer, send the print...then realize that nothing is happening because the confirm removal is on the touch screen again.
Been using Cura for about a year and those are my biggest gripes.
Ultimaker Cura 5.2 Released
in UltiMaker Cura
Posted
Sorry for the delay.
I included project files for both 5.0 and 5.2.1 In 5.0 the model slices in 23 seconds. Same model, using 5.2.1 it gets to about ~40 seconds then stalls and takes ~51 minutes to complete.
During this time, the Cura Slicing Engine is running at 96.2% CPU Usage.
Cura 5.2.1 UMS3_Snake v2.0.3mf Cura 5.0 UMS3_Snake v2.0.3mf