[Feature Request] Set Local storage path for downloads
All my data files are on separate drives. Putting anything on the C drive is a hard pass for me. Wish I had known that before I deleted my downloaded copies. Oh well. Please move this to the top priority!
That Cargo removes all files referenced by (e.g.) Blender when initiating a "clear cache" is a showstopper, since the projects become unusable that way. This is very badly implemented and needs to be addressed urgently.
Since we all now create symlinks as a workaround to the missing option to set custom paths it is imperative that a future update honors that symlink for compatibility reasons. I know from Redshift for C4D installations on Windows that they overwrite the symlink breaking it. That must not happen!
Merged in a post:
Let the user change download folder
You download all kits to %appdata%/kits
That is not acceptable (or even standard), you should at least give the user the option to choose the data folder, since the room on c: may be sparse. Nearly all artists I know have dedicated data drives for these resources. Another option could be to delete the kits after the program is closed, but I see the advantage in cacheing them. So a user-selectable data folder is the preferred solution.
A workaround is to create a hardlink to a folder on the data drive.
Merged in a post:
Shared Cache Folder
Daniel Vesterbæk Jensen
I am working with multiple workstations and keep all my texture files on a shared drive, so all workstations can access them with the same path. Is it possible to change the "cache/texture" folder location that Cargo is downloading assets and textures to?
I couldn't find out how to do it in the UI.
Thanks a lot.
Tip: I couldn't find any way the change the download folder for the kits and assets, but I used a symlink to retarget the original folder to a different drive from C:\Users***\AppData\Roaming\kitbash3d
step 1. close the apps
step 2. move the kits folder to a drive where you have enough space.
step 3. run the Command Prompt as admin
step 4. navigate to your kitbash folder:
step 5. use the command to create the symlink.
mklink /D kits S:\kits
this will create folder symlink inside the current folder pointing to the S:\kits folder.
Denes Dankhazi: we appreciate you posting this to help out other KitBashers!
For other upvoters:
Custom folder locations are on the roadmap for the next major release, and in the mean time, this is a work around that comes from the community, but has not been tested and may cause bugs or issues with Cargo. Love to see this excitement from the community. :)