Jump to content

ElleCross

Member
  • Content Count

    18
  • Joined

  • Last visited

Everything posted by ElleCross

  1. Hey @drdave! I also got the file, and same as @Msuurmond, I see only the cache and it looks like it's 3.3. Can you please check the \Application Support\Cura again and look for the whole 3.2 folder? That's what we need to check. Thanks
  2. Hey @pgrunwald, yes. But first make sure to delete the 3.3 configuration folder before you launch the 3.3.1. Let me know how it goes!
  3. @ngwpower or @ngwpower18, @jose06 and to others that had problems with 3.3 yesterday. Please try this: 1. Delete the 3.3 folder only in the Cura configuration folder. Make sure to leave 3.2 folder. In Windows, you can find it in Appdata\Roaming\cura. In Mac, you'll find it in \Application Support\Cura. 2. Install the new version 3.3.1 with fixes https://ultimaker.com/en/products/ultimaker-cura-software 3. If you are still encountering some issues, can you please zip and attach the 3.2 folder from the configuration folder and attach it here?
  4. hi @Drdave, I've replied to you in the other thread.
  5. @Duncan_B and @pgrunwald, can you please try with the new version: https://ultimaker.com/en/products/ultimaker-cura-software Cura 3.3.1 Before you install and launch it, please make sure to delete the 3.3 folder in the configuration folder. In Windows, you can find it in Appdata\Roaming\cura. In Mac, you'll find it in \Application Support\Cura.
  6. Hi @Drdave, to be sure, the 3.2.1 option that you said you did not delete, do you mean the 3.2 folder in the Cura configuration folder? In Windows, you can find it in Appdata\Roaming\cura. In Mac, you'll find it in \Application Support\Cura. If that's not what you mean, can you try and go into those directories and delete 3.3 folder - make sure to leave 3.2 So that when Cura 3.3.1 upgrades, it will copy the old settings you have in 3.2. If you are still encountering some issues, can you please zip and attach the 3.2 folder from the configuration folder and attach it here? That way we can see and reproduce your issue and find out what is causing this for you.
  7. Hey @harald25, we have just released a new build yesterday with some fixes that addresses your issue. You can get it from here. https://ultimaker.com/en/products/ultimaker-cura-software Before you install and launch Cura 3.3.1, can you please make sure to delete the 3.3 folder in your cura configuration folder? \Application Support\cura\ Let me know if this helps.
  8. Hey Jake! Good news, we have a new build that contains a fix for your issue - Cura 3.3.1. It will come out in the next few minutes When you install that, make sure to remove the 3.3 folder. When you upgrade to 3.3.1, Cura will create a new 3.3. folder, then you'll see the profiles enabled and can be selected again! :D
  9. Hey @JawzX indeed. This is a bug that we're working on now. You can see the rest of the discussion here: https://github.com/Ultimaker/Cura/issues/3702 Good news is, we may have a fix soon!
  10. Hi @Jakeddesign, I think they have the *.curaprofile if they are exported. I'm going to check what caused your issue, but can you attach the whole 3.2 folder please? I will load your same configuration and figure out why all the profiles are grayed-out for you. In the meantime, can you check if your Material + Nozzle combination is correct as well? Based on your attached screenshot above, I see the warning icon that's some material incompatibility. This can cause some profiles to appear unsupported.
  11. Hey! I use silent install to install Cura on a test machine. I had to change the user account control settings to "Never Notify" and then proceed with the silent installation though. :/
  12. Hmm that's weird. I've never seen this. What OS are you on?
  13. Hi saymon, check my reply above. The link provided is a workaround to this issue. Thanks!
  14. Sounds like you have something similar as the user above ^. Can you check your logs if it's the same error you're getting? If it is, you can replace the shader file as well.
  15. It's a known issue that was fixed but unfortunately was not included in 3.0.3. As workaround, fieldOfView has provided a file that you can replace C:\Program Files\Cura 3.0\resources\shaders\grid.shader with. Link to the shader file that will solve your issue. Check out: https://github.com/Ultimaker/Cura/issues/2644
  16. Appdata is a hidden folder under C:\Users\[user]\ directory. When you unhide that, you'll find the Cura folders under: C:\Users\[user]\Appdata\Local\Cura and C:\Users\[user]\Appdata\Roaming.
  17. Hello @Printers_Unite, you said that this problem happens with Cura 2.7 and Cura 3.0. Can you tell me what printers (and their configuration) do you have in 2.6? Alternatively, do you still happen to have your two cura folders in \AppData\Local and in \AppData\Roaming? If you won't mind, you can upload them so that I can take a look at the configuration you have and then check why Cura does not launch for you at all.
  18. From the image you attached, it looks like you are modifying the Infill Density setting of Extruder 1, yet your model is being printed by Extruder 2.
×
×
  • Create New...

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!