Stuarts

I've always found that running it in Windows 8 compatibility mode fixes the problem. I have to do this every time a new release comes out and it never fails.

Set the compatibility settings for cura.exe to windows 8.

That should read win 8. I edited it in my original post, but forgot about the other posts that I replied to.

I've just discovered the same fix. I seem to remember having the same problem with an earlier version as well. Took me a while to remember the fix.

I think I just solved this problem. I've been fighting with it for 3 days. I have run the compatibility troubleshooter and it has recommended Windows 8.1 compatibility. I now have it running. It did change some settings in my active profile which it adopted from my 4.1 config. It changed line width and speeds.

I think I just solved this problem. I've been fighting with it for 3 days. I have run the compatibility troubleshooter and it has recommended Windows 8 compatibility. I now have it running. It did change some settings in my active profile which it adopted from my 4.1 config. It changed line width and speeds.

I think I just solved this problem. I've been fighting with it for 3 days. I have run the compatibility troubleshooter and it has recommended Windows 8 compatibility. I now have it running. It did change some settings in my active profile which it adopted from my 4.1 config. It changed line width and speeds.

I have seen the same mentions of problems with thingiverse, but haven't seen any problems with Cura 4.1.0 so it doesn't seem like a thingiverse problem.

This hasn't fixed the problem and I doubt that thingiverse is the issue as 4.1.0 loads without error. I have reinstalled and it now gets past upgrading configuration and now sits at loading preferences.

I've been running 4.1 for a while and just installed 4.2.1. When I start it, the splash screen opens and cycles through loading plugins and then updating configuration. 2 hours later it is unchanged. I have established that if I have my network disabled, it crashes pointing at the thingiverse plugin. I'm not sure if that is significant or not.

Of course, measuring the width accurately enough is another challenge.

If you extrude 10mm of 1.75mm filament and print it as a stripe on the bed. You can measure the thickness and width of the extruded stripe and the length to calculate the volume extruded. Its pretty easy to calculate the volume of 10mm of 1.75 diameter filament. If you compare them you can calculate a correction factor to extrude the correct amount of filament. Stuart

Unfortunately, just changing colour in the same brand of filament can need almost all parameters changing, making a per material flow almost pointless. You will still need to adjust it in your profile. I generally print in eSun pla plus in white grey and black. They need very different profiles.

In my cura there is a flow parameter in Material for each profile. You just have to turn on the visibility of the setting.

Its actually intel hd 520. I had to uninstall the manufacturer driver to install the intel one. Hasn't fixed the problem.

Its been rock solid for me, but I've now installed the 3.3.0 update and have the same problem. I've tried the same fix and it doesn't work. My video drivers are the ones provided by my laptop manufacturer. At the moment I cant get the latest intel driver to install over the top of it as it sees the manufacturer driver and refuses to update.

As I said, I deleted appdata/roaming/cura/3.2. Cura recreated it and all is well.

Problem fixed. deleted appdata/roaming/cura/3.2 folder and let cura create it again. It seems to have pulled in previous configs and profiles. Installed Octoprint plugin. all seems ok.

As flow is set in the material profile, it is specific to the material. You have a different profile for each material.

I've just installed Cura 3.2.1 and I cant get it to start. It crashes while loading interfaces with an error from windows saying that cura.exe stopped. I've tried uninstalling and clearing out all the app data folders of references to 3.2 or 3.2.1. Unfortunately nothing has helped there. I'm running windows10 home. i7 12GB RAM. cura 3.1 runs without an issue. I had previously loaded the 3.2 beta and it appeared to start ok until I tried to install the Octoprint plugin. I haven't been able to make the 3.2 beta or 3.2.1 run since I tried to install the Octoprint plugin on the beta release. I haven't attempted to install it on 3.2.1 as I cant get to the GUI before it crashes. Any thoughts? cura.log excerpt.log