Jump to content

Why does Cura relentlessly try to create a file in a directory that does not exist?


rgelb

Recommended Posts

Posted · Why does Cura relentlessly try to create a file in a directory that does not exist?

For whatever reason, Cura (even when it's not doing anything and is sitting idle in the background) relentlessly tries to create a file in the C:\Windows\CSC\v2.0.6\namespace\RT-N56U.

Directory C:\Windows\CSC\v2.0.6\namespace does exist but RT-N56U folder does not. \\RT-N56U\TwoTB also happens to be a share that I am accessing (mapped to the Z:\ drive).

Why does Cura need to create a file there? And it does so relentlessly, over and over again. My computer physically slows down because of it and File/Open operation on Cura is so slow (probably because of this).

5a33413fe4b13_2017-11-2615_54_17-ProcessMonitor-Sysinternals_www.sysinternals_com.thumb.png.34a068b7a9cbb1bbb94332a19abc2c1a.png

5a33413fe4b13_2017-11-2615_54_17-ProcessMonitor-Sysinternals_www.sysinternals_com.thumb.png.34a068b7a9cbb1bbb94332a19abc2c1a.png

  • Link to post
    Share on other sites

    Posted · Why does Cura relentlessly try to create a file in a directory that does not exist?

    What version of Cura is doing this? Does it happen continuously while using Cura, or only when opening an Open/Save dialog?

    Do you use the "offline files" functionality in Windows?

    • Like 1
    Link to post
    Share on other sites

    Posted · Why does Cura relentlessly try to create a file in a directory that does not exist?

    As i never heard of the Windows\CSC combi before (and I'm pretty sure that this isn't something that we hardcoded), i just googled this. So yeah, ahoeben seems to be onto something, as it's about the offline files functionality from windows itself.

  • Link to post
    Share on other sites

    Posted (edited) · Why does Cura relentlessly try to create a file in a directory that does not exist?

    As i never heard of the Windows\CSC combi before

    Yes, it's offline files and I've turned it off.  Still, Cura beats on a network mapped drive I have every 5 seconds.   Note in the image:

    5a334141e892a_27-11-201710-13.thumb.png.b49fc13b9b1fca08d189511b8beeca62.png

    I did figure it out with help of some folks.  It's the "Removable Drive Output Device Plugin".  https://github.com/Ultimaker/Cura/blob/3.1/plugins/RemovableDriveOutputDevice/WindowsRemovableDrivePlugin.py#L50

    The implementation has some issues:  

    1. It loops through all the drives.  It should only be looping removable drives. There is a SO question about this.
    2. And it shouldn't be looping at all.  The app should register for notification of insertion/removal of USB devices to see if removable drives are present.
      I did this several years ago to detect insertion/removal of USB headphones and the method was pretty reliable.  I would contribute the code but it was in C#

    Edited by Guest
  • Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    • Our picks

      • UltiMaker Cura 5.7 stable released
        Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more. 
         
          • Like
        • 13 replies
      • S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
         
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
          • Like
        • 0 replies
    ×
    ×
    • Create New...