Ultimaker Cura 5.0 beta - Feedback

[fvrmr]

Welcome to discussion thread for Ultimaker Cura 5.0 beta

After a alpha and two beta releases to test the Arachne Engine, the new slicing Engine is finally here. This new engine uses variable line widths when preparing files for printing, meaning you can now print thin and intricate parts more accurately and with greater strength.

In the past, sliced files would use a consistent line width, with the exact width depending on the nozzle diameter and the line width settings used. This meant that when slicing a file, if part of the print was two-and-a-half lines thick, Ultimaker Cura would generate two lines and leave a small gap between them. In certain cases (such as with extremely small details) areas of less than one line thick would not be able to print at all. This issue has been completely solved with the latest release. Your printed parts will now have fewer internal gaps which means they’ll not only look better, but they’ll be stronger as well.

Let us know what you think of this new engine and show us your results here in the comments below, you can report your bugs here!

Download the beta here

[looolz]

Always exciting with new updates!

The beta for Mac seems to be Intel, not Universal or native Apple?

[lorenzofanchi]

Same here. Just downloaded v5 beta, tried to launch it on my M1 Mac results in instant crash (I have v4.13.1 installed as well)

[mstaerkle]

happend for me as well i had to delete all configurations to start it dunno if that may be the same for you

[jmger]

hi all if this is not the right place let me know where to go to comment on CURA 5.0. I really really think we need the ability to manually tell Cura which part to print in what order in a multi object print. I want to print 6 identical parts on one build surface. From my research I really can't do this. or not easily. From what I read cure does this, sort of automatically depending on how you place the objects. This seems really complicated and confusing. In Simplify3D I could do this no problem.

[jmger]

Another thing is with Supports. I downloaded the Support plugin setting wants to print the support through my print so I have to lower the infill below the build surface and then lower my part back down to the bed to get things to print correctly. it is the Abutment support type.

[jmger]

I thought I would break this up into 2 posts. The second thing with supports is with the CURA 5.0 standard support setting in Cure 4.x The support from the build plate up would print as a Wall or something like a wall making the support easy to break off. In Cura 5.0 It pretty much welds to the part. This is with out making any real tweaks to the Support settings. That's why I just use the user defined support plugin. It works so much better but takes a lot more time to setup.

[csterlin]

Just downloaded Beta1 of 5.0.0, and cannot access the Marketplace. Other than that it is working well so far, a ten-hour job.
I've no idea if this a bug or a configuration error I made, however I can get to the Marketplace with 4.13.1.

[nallath]

#11858

[keithwins]

I can't get Cura 5.0 to work. Either it won't start at all, or in one case it wouldn't track mouse movements in that window, so I had to close it. I have reinstalled 4 times, Windows 10. I went back to 4.13 and it worked perfectly.

[Cpat39]

Successfully downloaded 5.0.0. Have sliced 3 STL files and printed 1 successfully. Item printed has very fine details and printed much better than the Cura 4.13.1 version. Print was run on Anycubic Vyper using PLA. Have noticed that cannot drag a file from Apple Finder and drop onto Cura located in MacBook Pro Dock 15" 2016 model running macOS Monterey 12.3.1.

[nallath]

Can you also create a bug report for that? Thanks for trying it!

[SystemFailurePR]

Downloaded the beta looking forward to the M1 Support but the process still lists the process as an Intel Process.

[nallath]

But it works, right?

[adam3654]

After installing the 5.0 beta, I got messages after startup stating that all of my plugins were incompatible and to try reinstalling from the marketplace, and the marketplace didn't list any of them to reinstall. Is this normal or at least a known issue?

[nallath]

Yeah, this is a known issue. Because we have changed so much, the plugins need to be changed in order to be compatible again.

[loshlee]

Thank

Yeah, this is a known issue. Because we have changed so much, the plugins need to be changed in order to be compatible again.

Is there a way to remove the nibs for incompatible plugins in the meantime? You know, so they don't try to launch then trigger the error message?

[csterlin]

I sent in a bug report on this issue earlier this evening.

…

On Thu, Apr 21, 2022 at 7:57 PM adam3654 ***@***.***> wrote: After installing the 5.0 beta, I got messages after startup stating that all of my plugins were incompatible and to try reinstalling from the marketplace, and the marketplace didn't list any of them to reinstall. Is this normal or at least a known issue? — Reply to this email directly, view it on GitHub <#11842 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALFVIY5IZGDZC4UOBZH2REDVGIBQ7ANCNFSM5T7OYBDA> . You are receiving this because you commented.Message ID: ***@***.***>

[nallath]

Yeah, this is a known issue. Because we have changed so much, the plugins need to be changed in order to be compatible again.

[GoTVm]

I'm getting weird results after slicing with Cura 5.0. It should be faster, or at least on par, as is said in the description of the new slicing engine, but I'm seeing a 6-7 minute increase on just a 2 hour print compared to 4.13.1.

[nallath]

It's not always going to be faster. There are quite a few cases where it is, but as you've already found, it can also be a bit slower in others.

[GoTVm]

Alright, good to know!

[johnnieq2]

I cannot get Cura 5 to open. It crashes every time I try.
I reinstalled it and it still happens. :(

[doctorthompson]

Get the same error but hitting Backup and Reset Configuration worked for me (running Linux 5.4.0-109-x86_64) as does simply removing the single_instance = True line in cura.cfg

[johnnieq2]

Editing cura.cfg as doctorthompson advised worked! Thank you.

[walndyn]

I can confirm this. As soon as you check this setting to only use a single instance of cura, it won´t start up anymore and crashes.

[Wildsam7]

I keep getting the same error.

Error traceback
Traceback (most recent call last):
File "cura_app.py", line 239, in
File "cura\CuraApplication.py", line 858, in run
self._welcome_pages_model.initialize()
File "cura\UI\WelcomePagesModel.py", line 230, in initialize
self._initialize()
File "cura\UI\WelcomePagesModel.py", line 255, in _initialize
"page_url": self._getBuiltinWelcomePagePath("WelcomeContent.qml"),
File "cura\UI\WelcomePagesModel.py", line 220, in _getBuiltinWelcomePagePath
return QUrl.fromLocalFile(Resources.getPath(CuraApplication.ResourceTypes.QmlFiles,
File "UM\Resources.py", line 98, in getPath
raise FileNotFoundError("Could not find resource {0} in {1}".format(args, resource_type))
FileNotFoundError: Could not find resource ('WelcomePages\WelcomeContent.qml',) in 129

Logs
Thread 0x0000518c (most recent call first):
File "K:\MAINT\3D printing\Ultimaker Cura 5.1.0\share\cura\plugins\USBPrinting\USBPrinterOutputDeviceManager.py", line 80 in _updateThread
File "threading.py", line 946 in run
File "threading.py", line 1009 in _bootstrap_inner
File "threading.py", line 966 in _bootstrap

Thread 0x000045cc (most recent call first):
File "threading.py", line 324 in wait
File "zeroconf_init_.py", line 2534 in wait
File "zeroconf_init_.py", line 1715 in run
File "threading.py", line 1009 in _bootstrap_inner
File "threading.py", line 966 in _bootstrap

Thread 0x000052a0 (most recent call first):
File "threading.py", line 324 in wait
File "threading.py", line 600 in wait
File "K:\MAINT\3D printing\Ultimaker Cura 5.1.0\share\cura\plugins\UM3NetworkPrinting\src\Network\ZeroConfClient.py", line 81 in _handleOnServiceChangedRequests
File "threading.py", line 946 in run
File "threading.py", line 1009 in _bootstrap_inner
File "threading.py", line 966 in _bootstrap

Thread 0x000015ec (most recent call first):
File "zeroconf_init_.py", line 1369 in run
File "threading.py", line 1009 in _bootstrap_inner
File "threading.py", line 966 in _bootstrap

Thread 0x00004848 (most recent call first):
File "K:\MAINT\3D printing\Ultimaker Cura 5.1.0\share\cura\plugins\RemovableDriveOutputDevice\RemovableDrivePlugin.py", line 61 in _updateThread
File "threading.py", line 946 in run
File "threading.py", line 1009 in _bootstrap_inner
File "threading.py", line 966 in _bootstrap

Thread 0x0000449c (most recent call first):
File "UM\Backend\Backend.py", line 165 in _storeStderrToLogThread
File "threading.py", line 946 in run
File "threading.py", line 1009 in _bootstrap_inner
File "threading.py", line 966 in _bootstrap

Thread 0x00003fa4 (most recent call first):
File "UM\Backend\Backend.py", line 153 in _storeOutputToLogThread
File "threading.py", line 946 in run
File "threading.py", line 1009 in _bootstrap_inner
File "threading.py", line 966 in _bootstrap

Thread 0x00004fd4 (most recent call first):
File "threading.py", line 320 in wait
File "threading.py", line 460 in acquire
File "UM\JobQueue.py", line 98 in _nextJob
File "UM\JobQueue.py", line 124 in run
File "threading.py", line 1009 in _bootstrap_inner
File "threading.py", line 966 in _bootstrap

Thread 0x0000566c (most recent call first):
File "threading.py", line 320 in wait
File "threading.py", line 460 in acquire
File "UM\JobQueue.py", line 98 in _nextJob
File "UM\JobQueue.py", line 124 in run
File "threading.py", line 1009 in _bootstrap_inner
File "threading.py", line 966 in _bootstrap

Thread 0x00002388 (most recent call first):
File "threading.py", line 320 in wait
File "threading.py", line 460 in acquire
File "UM\JobQueue.py", line 98 in _nextJob
File "UM\JobQueue.py", line 124 in run
File "threading.py", line 1009 in _bootstrap_inner
File "threading.py", line 966 in _bootstrap

Thread 0x00004fc0 (most recent call first):
File "threading.py", line 320 in wait
File "threading.py", line 460 in acquire
File "UM\JobQueue.py", line 98 in _nextJob
File "UM\JobQueue.py", line 124 in run
File "threading.py", line 1009 in _bootstrap_inner
File "threading.py", line 966 in _bootstrap

Thread 0x00003958 (most recent call first):
File "threading.py", line 320 in wait
File "threading.py", line 460 in acquire
File "UM\JobQueue.py", line 98 in _nextJob
File "UM\JobQueue.py", line 124 in run
File "threading.py", line 1009 in _bootstrap_inner
File "threading.py", line 966 in _bootstrap

Thread 0x00004568 (most recent call first):
File "threading.py", line 320 in wait
File "threading.py", line 460 in acquire
File "UM\JobQueue.py", line 98 in _nextJob
File "UM\JobQueue.py", line 124 in run
File "threading.py", line 1009 in _bootstrap_inner
File "threading.py", line 966 in _bootstrap

Thread 0x00003ff0 (most recent call first):
File "threading.py", line 320 in wait
File "threading.py", line 460 in acquire
File "UM\JobQueue.py", line 98 in _nextJob
File "UM\JobQueue.py", line 124 in run
File "threading.py", line 1009 in _bootstrap_inner
File "threading.py", line 966 in _bootstrap

Thread 0x00003c14 (most recent call first):
File "threading.py", line 320 in wait
File "threading.py", line 460 in acquire
File "UM\JobQueue.py", line 98 in _nextJob
File "UM\JobQueue.py", line 124 in run
File "threading.py", line 1009 in _bootstrap_inner
File "threading.py", line 966 in _bootstrap

Current thread 0x00003384 (most recent call first):
File "cura\CrashHandler.py", line 397 in _logInfoWidget
File "cura\CrashHandler.py", line 182 in _createDialog
File "cura\CrashHandler.py", line 86 in init
File "cura_app.py", line 165 in exceptHook

Went to cfg file and it shows this.
[general]
last_run_version = 5.1.0
version = 7

[view]

[cura]

[local_file]

[info]

[cura_drive]

[backend]

[gcodereader]

I have tried uninstalling and reinstalling the program multiple times.
Also tried the backup and reset configuration multiple times.

I have been using cura 4.12.1

Thanks Steve

[ajmerisahil171199]

hey @Wildsam7 did you get the rid of this problem ?
i am having same issue while running exe that build using pyinstaller cmd.
the project runs when i use "python cura_app.py" but build exe and run the execution file getting me an error that you faced.
how did you solved?
any solutions ?

[mlee12382]

Can we get native integration for Elegoo's Neptune 2 / 2S / 2D FDM printers please?

[nallath]

If someone makes a pull request we can merge it. We will not create it ourselves (as we don't have the printer)

[csterlin]

Yes, it works thus far. I've only tried the one job listed in my bug report, and it worked well, although I should have done a better job setting it up.

…

On Fri, Apr 22, 2022 at 2:48 AM Jaime van Kessel ***@***.***> wrote: But it works, right? — Reply to this email directly, view it on GitHub <#11842 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALFVIY4ICDURQRYRFARIYKDVGJRVVANCNFSM5T7OYBDA> . You are receiving this because you commented.Message ID: ***@***.***>

[csterlin]

When I installed 5.0.0 Beta-1 I found the profiles created under 4.13.1 were not available, and I had to recreate them all from scratch. They were retained under 4.13.1 which continues to work as before adding 5.0. Attaching project and log files:
CE3_Borderlands_Buggy_Thickened.zip
cura.log

[jmcazaban]

Spiralize mode always uses concentric lines for the bottom, no matter what I choose.
Is it a bug?
I have the older Arachne Beta 2 also installed, maybe I should remove both and reinstall if this shouldn't be happening.
Thanks!

[doctorthompson]

Not getting any handles rendered for move/scale/rotate operations.

Note: OpenGL is effectively v3.1 on this box (environment shown below), but no version warnings were given at startup or anything.

Seems to be spitting this out each time I select one of the move/scale/rotate tools with a model selected:

QOpenGLShader::compile(Fragment): 0:13(1): error: `frag_color' undeclared
0:13(1): error: value of type vec4 cannot be assigned to variable of type error
0:17(1): error: `frag_color' undeclared
0:17(1): error: value of type vec4 cannot be assigned to variable of type error

*** Problematic Fragment shader source code ***
#ifdef GL_KHR_blend_equation_advanced
#extension GL_ARB_fragment_coord_conventions : enable
#extension GL_KHR_blend_equation_advanced : enable
#endif
#define lowp
#define mediump
#define highp
#line 1

uniform lowp vec4 u_disabledColor;
uniform lowp vec4 u_activeColor;
uniform lowp float u_enableMultiplier;

varying lowp vec4 v_color;

void main()
{
if(u_activeColor == v_color)
{
frag_color = v_color * u_enableMultiplier;
}
else
{
frag_color = v_color;
}
}
***
QOpenGLShaderProgram::attributeLocation(a_vertex): shader program is not linked
QOpenGLShaderProgram::attributeLocation(a_color): shader program is not linked
QOpenGLShader::compile(Fragment): 0:13(1): error: `frag_color' undeclared
0:13(1): error: value of type vec4 cannot be assigned to variable of type error
0:17(1): error: `frag_color' undeclared
0:17(1): error: value of type vec4 cannot be assigned to variable of type error

Environment

System:    Kernel: 5.4.0-107-generic x86_64 bits: 64 compiler: gcc v: 9.4.0 Desktop: Xfce 4.16.0 tk: Gtk 3.24.20 
           info: xfce4-panel wm: xfwm4 dm: LightDM 1.30.0 Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal 
CPU:       Topology: 2x Quad Core model: Intel Xeon E5462 bits: 64 type: MCP SMP arch: Penryn rev: 6 L1 cache: 512 KiB 
           L2 cache: 12.0 MiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 44689 
           Speed: 2396 MHz min/max: 2400/2800 MHz Core speeds (MHz): 1: 2392 2: 2399 3: 2394 4: 2394 5: 2394 6: 2394 7: 2398 
           8: 2399 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Juniper XT [Radeon HD 5770] vendor: Apple MacPro5 1 driver: radeon 
           v: kernel bus ID: 01:00.0 chip ID: 1002:68b8 
           Display: server: X.Org 1.20.13 driver: ati,radeon unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD JUNIPER (DRM 2.50.0 / 5.4.0-107-generic LLVM 12.0.0) v: 3.3 Mesa 21.2.6 compat-v: 3.1 
           direct render: Yes 

Anything else you need? I'm gonna try compatible mode.

[doctorthompson]

Here's a clean cura.log file showing the toolhandle errors. I open the app, open a model, and cycle through the move, rotate, and scale tools.
cura.log

[fieldOfView]

Fixed here: Ultimaker/Uranium#811

[Silvermoon75]

Hi, are you going to add missing printer like Artillery Sidewinder X2 on the list of printer?

Thanks...

[fieldOfView]

If someone, either the printer manufacturer or a community member, makes a pull request it can be merged. Ultimaker will not create it (as they don't have the printer to test the profile with)

[doctorevil30564]

attempted to try out the 5.0 beta, it doesn't like my current Cura 4.13.1 profile, keeps crashing every single time I try to run it. I made a backup of my profile and let it create a new one. not really thrilled about this though, as I had a lot of stuff tweaked and setup on my original profile. I let it send crash reports several times, so hopefully they'll help you guys with ironing out any issues before this version gets released. Also any chance for new optimized profiles for the Ender 3 V2 or the Voxelab Aquila? both do ok on the default ender 3 pro profile, but I figure there is always room for improvement

[nallath]

It's probably crashing because of the single instance flag being set. We missed that during testing, but have already created a fix for that for the stable release. Could you check if it's indeed the same: #11952

[DrRob]

5.0.0-beta+1 makes my Macbook run hot even when it's doing nothing so I'm having to quit Cura far more often than I used to.

[seaniepie]

Indeed it does. This tends to be the case for Beta's. If I leave it running for long enough (even with nothing loaded into it) it has been known to cause the whole system to reset. That's on me for not closing it down while not in use. Having said that, it's only using 20% CPU and 25% GPU. So, it's not really taxing the system. But having a model loaded in did cause the fan to start up gently. When I switched to Chrome with Cura sitting in the background and behind the Chrome window, Cura CPU and GPU usage fell to near 0% and the fan fell quiet. So not really that bad.

[m-sundman]

So not really that bad.

Heh, no, it's really quite bad. Programs doing nothing should, well, do nothing. Not busy-loop in an UI event thread or whatever.

[nallath]

Something that was invisible was causing UI updates to be triggered. That shouldn't have happened (Qt shouldn't trigger redraws for something that is invisible), but it did.

Anyhow, this should be fixed for the final 5.0 release.

[HomeCovilha]

Downloaded the new 5.0.0+1 Beta for Windows.

Running on a AMD 3900X with 32gb of RAM and crashes 4 times on the first print I've tryed. The first 3 crashes was using the print from USB option, the last one was with an SD card.
The print from usb ones cura just crashed on me living me with half of a print and the print head stopped, the one from the SD card printed 3 layers at most and the print head parked near the home position. Every single time i had to restart the printer so it could work again.

Gave up waisting PLA and got back to Cura 4.3.1 and the same print with the same settings worked perfectly on the first try.

I like the idea of the new Cura 5, but i won't use it while in Beta...

[KimmoHop]

When I add a support blocker, roughly at the middle of the Benchy, it is created at viewpoint:

If this is not known by Cura team, I can create new issue ;)

[nallath]

Uuh, that's not one i've seen before. Please create a new ticket :)

[KimmoHop]

#12187

[ariasfelipe2070]

Installed in windows 11, in a dell workstation, the installer run ok, I run cura from the installer and there was no problem, however windows did not found the icons until I restarted the laptop.

Then cura did not started.... it stayed in the splash, until I run it as administrator ir launched. I will try some prints now.

[nallath]

Please create a ticket for that and provide us with the logs.

[CarVac]

I'm getting an OpenGL error on Pop!OS 22.04 with an RX 480.

PyInstaller/loader/pyimod03_importers.py:495: DeprecationWarning: the imp module is deprecated in favour of importlib and slated for removal in Python 3.12; see the module's documentation for alternative uses
libGL error: MESA-LOADER: failed to open radeonsi: /usr/lib/dri/radeonsi_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: radeonsi
libGL error: MESA-LOADER: failed to open radeonsi: /usr/lib/dri/radeonsi_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: radeonsi
libGL error: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: swrast

[mstaerkle]

I really like Cura i would like some featurs like choosing firmware Marlin Klipper etc since i use both, and since Cura does not work as good as SuperSlicer with klipper i take SuSl for klipper and cura for marlin. For this beta i just can say it is quit nice, since the gui is faster the marked place is faster. But there is still much to do, like you cant import your backup from 4.13. with the profiles and so on. When the bugs are gone i think it will be a great improvement to 4.13.1. Still the Klipper stuff will remain a wish for now >.<

[Kaicura]

Is there a chance to get Cura5 for Win7

?

[fieldOfView]

Unfortunately, no, there is no chance that Cura 5 will run on Windows 7

[VK1IAN]

The decision to not support xUbuntu 18.04 is disappointing. I am still getting updates so it is must be still supported surely?
Why are you pushing people to run the latest and (un)greatest?? What about backwards compatibility??
Sounds very Microsoftish to me :-(
Might have to look at other slicers or stick with the current version that does work for me.

[VK1IAN]

I'm away from home at the moment so my options for trying things are somewhat limited. I'm still using 18.04 LTS because I spent a bit of time customizing it to do what I want. Upgrading to later versions just mess that up. I have done a few "apt dist-upgrade" over the years (14.04 to 16.04 from memory), but moving to 20.04 broke stuff, so I restored and stuck with 18.04.
I have a ubuntu 20.04 VM but couldn't open files. I reported that 2 months ago (others have also) but have yet to see a solution. There have been a few workarounds suggested but none have worked for me. I also tried a 22.04 VM but that didn't work either (can't remember what the error was and given the lack of response to my last report, I haven't bothered reporting it).
Whilst Xubuntu has reached end of support, all my repos are pointing at ubuntu servers. Xubuntu after all is really Ubuntu with the Xfce window manager. So all my core applications (firefox, thunderbird, libreoffice, gcc tool chain, etc) are coming from Ubuntu (18.04 LTS is not EOL until 2028); hence my I'm somewhat disappointed that Cura has decided to abandon "us".
Now I don't know the business case for Cura going down the current rat hole, but if support was the problem (technical or financial), I'm sure people would have stepped up if asked. Anyway, the milk has been spilt and that bridge burnt. Cura and Kicad have pushed me to never support another open source project.
In so far as other slicers, I've managed to download 2 versions of Prusaslicer; one using GTK2 and the other GTK3. Both run on my 18.04 LTS system, with no obvious difference between the two. I just need to get my head around where "stuff" is and will probably stick with that. At least it works.
To the Cura team, so long and thanks for the fish.

[nallath]

Now I don't know the business case for Cura going down the current rat hole, but if support was the problem (technical or financial), I'm sure people would have stepped up if asked.

Would they? We're talking about about one fulltime FTE here, which is already much more than what we receive in contributions right now. I also strongly doubt that we would have been able to get this in financial donations. I've already clearly outlined the business decision that was at the root here. It's a pretty clear one, you just refuse to accept or understand it.

Cura and Kicad have pushed me to never support another open source project.

Let's be frank here, if this is your response to a project, that you contribute nothing significant to, I think that you're doing the other contributors a favor by not "supporting". Reactions like this is why open source developers burn out and stop developing software. Do the Prusa developers a favor and don't respond to them like you're doing now. They deserve better.

Let's be even more frank; No open source project owes you anything. What we give away is up to us do decide. We will listen to feedback and try to make something that benefits as many people as possible. But don't you dare pretend that you are being betrayed or try to shame people into doing what you want.

[VK1IAN]

I don't know and neither would you; if you need help you need to ask for it.
I think you are misunderstanding my point. What you "give away" as a developer "costs me" as a consumer.
It would be remiss of me not to voice my opinion; the developers deserve to know why I'm withdrawing my support. Maybe I should have said nothing and you would be none the wiser. This would show a lack of intestinal fortitude....in my opinion.
Let me be frank, your response is exactly why open source projects fail; "my way or the highway". Perhaps we should talk again in a few years??

[nallath]

There is a massive difference between saying "This doesn't work for me" and saying "I will withdraw my support from this project". The first is notifying someone so that it might be fixed, the second is shaming / blackmailing / entitled. I hope you can see the difference between the two.

I don't know and neither would you; if you need help you need to ask for it.

An open source project always needs help. Don't you think it's a bit of an easy cop out to now say that it's too late? This is the exact moment where you can prove me wrong (and I'm gladly proven wrong in this instance!). Sorry to say, but talk is cheap.

What you "give away" as a developer "costs me" as a consumer.

Cost you? How? First you had nothing and now you have Cura 4.13.1 that you never paid anything for. I fail to see how I cost you anything.

Let me be frank, your response is exactly why open source projects fail; "my way or the highway".

Is it? Have you ran an open source project? Have you tried negotiating with hundreds of users while you only have the ability to build the features that maybe half of them request? With triage you always have to disappoint someone. Unless we would magically get 20 extra developers (and even then I'd doubt if we would be able to handle all feature requests!), this is what has to happen. I don't like it any more than the people we disappoint.

[VK1IAN]

You are right. I know nothing.
I'll step away from the keyboard now.

[tato1989]

It happened again on Cura 5.0 Final Relese on Snapmaker 2.0 A350 Printer.
Both models was same file, same settings.
One printed perfectly and another print failed with same file.
Little confused what 's the reason

[rburema]

If it's the same sliced file, then it's unlikely to be Cura.

I'm not sure if that printer uses belts, but if it did, I'd check the belt-tension, it may be too low (especially the axis the offset occurs in -- of that's exactly x or y, then it's more likely).

[Sonicboom247]

any chance for another nightly build?

[Filmman586]

Didn't know where to post this Question? Looking to create a Platform_Texture for my printer, I know that the build plate obj or stl goes in MESHES, do I put the .png file in there too? Thanks.

[rburema]

It goes in resources/images. Look at all the files names (something-)backplate in that folder for the UltiMaker examples.

[Zielblank]

I want to make a suggestion, in the new beta release 5.2.0, there are more control in the flow of the initial layer to prevent the elephant foot issue, which is very good, but I think it's not enough, it can control the flow of ONLY the first layer, I think it will be much better if you make it for the at least the 5-10 layers, also I think the bottom layer flow and the top layer flow should be separated instances.

[seaniepie]

I've made a patch for the Zoom Toward Mouse Position issue we've had for some time. This is my first to the repository. Can someone check it over for me. Ultimaker/Uranium@00a897c Thanks

…

Message ID: ***@***.*** .com>

[SineVVAVz]

When working with an IDEX printer (Sovol SV04 in my case), would like to be able to switch extruders at a certain layer.

Anyway to add this?

[rburema]

You can try the pause-at-height script in the post-processing menu maybe. Then swap the material when it's paused. This may or may not work for that printer though.

[Khronos666]

I ran into a problem..I couldn't decide in any way... printing the tube in one line, the rolling disappears and the " cleaning distance of the outer wall" stops working... and printing in two lines works fine... is this a bug of the program or does some kind of setting affect it?

[rburema]

Please post use the 'new issue' button here. Preferably with images and/or a model attached, as I have a hard time parsing what you mean.

[Khronos666]

I have already posted a new comment on version 5.3.0 beta...yes, and on 5.3.0 in one line, too, the roll does not go further than the seam... the result is a hole... for a better understanding of Watson plastic
Я уже выкладывал новый коментарий на версию 5.3.0 бета...да и на 5.3.0 в одну линию тоже дальше шва накат не идет... в результате получается дырка...

here is the link #14637 (comment)