Cosmos Assets Download Folder not sticking between reboots

Cosmos Issues
1

I seem to be the only on the team having this issue daily. One other user has reported it happening to them occasionally.

The team assets are on a mapped network drive:
Y:\Libraries\Chaos_Cosmos

I set that path, and use it all day long, no issues.
next day I turn the PC back on and its always reset to:
C:\Users\username\Documents\Chaos Cosmos

Every day I have to reset it manually back to to Y: drive.

I discovered a post from a while back to add a delay timer to the service when windows starts, but that had no effect for me. Any ideas?

Thanks.

2

Check if the .json file ( C:\Program Files\Common Files\Chaos\Cosmos\config.json) is updated after you’ve set the path in the Cosmos Browser UI. The “working_dir” should point to the path you’ve set, and it should be updated instantly.

If it’s not, maybe it is a permission thing?

EDIT: You can of course try the opposite, too - stop the Cosmos service, edit the path in the config.json, and restart the Cosmos service. See if it sticks this way.

4

Hi, thanks for replying. The correct Y:\ path is being saved to the json during the current windows session.

I have a theory actually. Those assets are mounted and loaded by Box Drive on Windows start. Sometimes that Box icon in the tray can stay greyed out for a good minute or 2 before it has fully mounted all the library and project assets to Y:\

Would I be right in assuming that if the cosmos service finds no Y:\ its default behaviour is to set it back to a directory that does exist? In this case under C:\Users\… ?

I’m mid rendering jobs all weekend so can’t test right now, but perhaps a tool or batch file that waits to detect if <cosmos user directory> = exists with a long enough time out, before starting the cosmos service might be the fix.

5

This may very well be the cause. Try the following:

  1. Open the .json file mentioned in the earliest post (C:\Program Files\Common Files\Chaos\Cosmos\config.json)
  2. Set the startup_delay parameter to “1m” or whatever time you think is necessary for the network drive to load.
6

I wrote a bat file to wait until “Y:\Libraries\Chaos_Cosmos” exists before starting the Cosmos service.

The folder seems to be sticking now so this one’s solved. Thanks hermit.crab.
Be good if Cosmos did this natively. I imagine a lot of people work on the cloud these days.