Junk SKB files
-
Recentlly I noticed my project folders are flooded with parazite skb foles named 1.skb, 2.skb,...etc.skb.
What could generate this chain? -
They're not parasites or junk, they're backup files. If you don't need them any more you can delete them.
See this thread. -
I know what skb files are\for. But for some reason my folders get spammed with those numeric skb files
(my skp files have more complicated names and I have linked skb file- and it's completely OK).
May be it's some ruby activity? -
Running Vista?, I had that also, but since Win 7 it's okay.
-
Sorry, I misunderstood. I'm still on Vista and don't get that. But it might be some kind of Ruby activity, as Pete suggests. For instance, I tried out the Save as Previous script. For me, not only does it not save as the previous version but it saves everything as s.skp.
-
The numerical 0.skb, 1.skb etc files seem to occur occasionally - I think it's if you open a new SKP and later on you save it, and it can't save the first skb as its first backup into the last used directory [e.g. perhaps it was erased in the meanwhile, or has awkward access-rights] so it sticks its first skb in the next best place, naming it numerically since there was no previously 'named version' to save that skb after. If this happens a few times, then to protect 1.skb when it makes its new version it calls it 2.skb... I haven't had it happen for ages - never with SUp8 or Vista SP2.
It seems to be an occasional glitch with Sketchup and Vista that is hard to reproduce when you want it to... -
I have noticed this when involving a usb portable storage device. So it is as mentioned- when there are "awkward access" issues.
-
0.skb, 1.skb, and .skps I think are the files SketchUp writes to before overwriting the existing file. I think it's because SketchUp verifies that the file can be successfully written before replacing the old file.
If these files aren't cleaned up it sounds like there are some permission problems. Are you saving to a network location? Or have you checked that you have full access to where you write?
Also, it could be other applications, such as virus-scanners, which has placed a lock on the file before SU can get around to clean it up.
-
Hmm.. I see.. Yep network glitches may cause skb flooding. (BTW I'm on Win7+ local network (through Novell utility).
-
I get those numbered SKB's when working on a new file for a while without saving with a real name.
Advertisement