haddad

Hello, Since Cura 4.2, when I noticed that it was taking too long to start, I opened the Task Manager and killed to Cura process before restarting it as administrator. It used to happen once or twice a week, no matter how many times I used Cura in between. After that, Cura would run normally again. Then came version 4.3 and version 4.4, but it continued that way. About a month ago, I had the Windows update for version 1909 applied and since then I did not have to do that... yet... My motherboard has Intel Graphics 630, but I don't think it poses much of a difference. Anyway it also got an update applied recently. Best regards,

Hello all, I had Cura 4.2.1 running fine since its debut. My Windows 10 Pro 64bits was version 1803, but it decided to update itself to version 1903 last week, and it crashed my system beyond repair. After formatting and reinstalling everything, already with Win10 ver 1903, I installed Cura and faced this same issue, i did not even get the Cura splash screen. The solution was to kill Cura task on Task Manager, because it was kept on background, and start it as administrator once. It came up normally and I disabled that checkbox "Send (anonymous) print information" on Cura's preferences config. I guess now that I could just allow Cura through the firewall as well. Anyway, the important thing is that I did not delete any previous config folder and did not loose my printers and materials personal settings. And no need for keeping Cura on compatibility mode, after the first run as administrator, it will run every time as normal. Hopping for having been helpful to someone, best regards.

Hello, I'm searching for any method to copy my customized printer settings, materials and profiles to another computer. This topic is the closest thing to it that I've found. I'm not sure if I should start a new topic... So, I guess that if it's not possible to backup all settings, it won't also be possible to transfer them to another computer. Hopping to be wrong, best regards.

ahoeben, That's realy a good idea. I didn't know about these postprocessing scripts, but it was easy to find and to make it work. Thanks!

Hello, I have a very high power heater (200W) for my bed and it rises my bed temperature up to 150°C faster than the extruder takes to reach 200°C. So I was also struggling with that same Cura auto generated code. Thanks to ahoeben it is solved. I'm using only the following lines, though: M104 S{material_print_temperature} ;Start heating extruder M190 S{material_bed_temperature} ;Start heating bed and wait to bed reach temp before proceeding M109 S{material_print_temperature} ;Wait for extruder to reach temp before proceeding But I have another auto generated code issue: the very last commands generated are 'M82' and 'M104 S0' which inexplicably locks up my controller board. I have inserted the 'M104 S0' earlier on the End G-code setting and it works fine since I manually delete the last auto generated 'M104 S0' on the saved file. So, is there a similar way to make Cura understand that 'M104 S0' was already sent and avoid the last one? Best regards,