Jump to content

Delan

Dormant
  • Posts

    6
  • Joined

  • Last visited

Posts posted by Delan

  1. Quick post to describe a problem I had and the solution I found, hoping it can help somebody else.

     

    Following a reinstall of my Linux (from Mint to Manjaro) and the launching of Cura, I encountered some issues with the backup of my profiles (at this point I probably messed up with the files). However, after deleting all config/personnal files from the /home and reimporting clean .curaprofile files, my prints were inconsistent, weak, porous, almost flexible and transparent, and sometimes broke when I tried to unstick them from the heated bedleft bad print, right correct print from another computer with same model, same material, same settings. 

    20181106_213345.thumb.jpg.5db2e73a3fb5b665a1d9a33819f44621.jpg

     

    After opening the gcode of each of these prints, it appeared that the bad one had severe underextrusion, and all the values (filament used and "E" value after G1 codes) were lower by a factor 0.377039. This value appears to be (1.75mm / 2.85mm)²: somehow, Cura considered that my filament was 2.85mm instead of the 1.75mm specified in the extruder settings. The filament diameter wasn't mentioned anywhere else (material or profile). To solve this, I erased the old 1.75mm in the extruder settings (which didn't seemed to be taken into account) and rewrite it.

    • Like 2
  2. On 10/12/2018 at 9:23 AM, qrti said:

    My workaround:

    Cura desktop icon / right click - properties / compatibility / check compatibility mode for windows 8

     

    Unchecking compatibility mode and starting Cura will work once.

     

    Almost made it for me: I had to let the compatibility mode (Windows 8 ) checked otherwise the problem persisted.

  3. I've tried a few things and now Cura works again:

    1. Uninstalled Cura 3.5.0 (previous versions being already uninstalled). Also, during uninstall process, I selected to delete my configuration files.
    2. At this point, there's nothing in C:\Program Files\Ultimakerwhatsoever or in C:\ProgramData. The are still files in C:\Users\<user>\AppData\Roaming\cura and C:\Users\<user>\AppData\Local\cura (although only related to previous version - 3.3 and 3.4 in my case - as well as stderr and stdout log files. I moved them somewhere else, just in case.
    3. I made a fresh install (no additionnal component selected: no arduino drivers, no visual studio). No other issue, Cura starts at the end (as before), and after adding custom printer, allowed to send date, then closing Cura, it starts again (and again) (and again). One solution of the issue, but still, we lose all the configuration. 
    4. I uninstalled Cura, suppressed the newly created "user" files in both local and roaming, put the ones from previous versions back in place, re-installed Cura, it starts with my old parameters at the end of the install. At this point, Cura runs normally (closes and starts as it should). Moreover, the Cura.exe process in the task manager is bigger than when the bug occured (~200MB instead of ~42MB).

    Something apparently failed during the install process, but I don't know what. I'll repost here if the problem occurs again.

     

    Hope this helps!

  4. I installed Cura 3.5.0 to replace the previous version on Windows 10. After fresh install, Cura launches normally. However, after being closed, Cura won't open again : Cura.exe appears in the task manager (with relevent size : 41MB) but no GUI shows up. Same problem after killing the process and relaunch it.

    I tried to uninstall and reinstall, it worked one time then again, after closing Cura it won't open again.

    Log files (C:\Users\<user>\AppData\Roaming\cura\3.5\cura.log) are empty for this last opening.

     

    Is there another process to kill or something that I missed?

    Thanks in advance!

×
×
  • Create New...