So I’m not understanding the new local cache server, am I supposed to launch the cache server daemon or is it all automated from within the editor like Ante implied at Unite?
Because it keeps changing port # and logs an error in the console that it can’t connect to it.
1 Like
I’m having the same problem. I launch the cache server locally using the --path and --port arguments, then after some time (usually on the order of a few hours), Unity will spit out that error. And I can’t just restart the cache server immediately with the new port because it says it’s already in use. I have to shut down Unity completely, start the cache server with the new port specified, then relaunch Unity. This makes the cache server work for a while, until Unity changes the port # again.
1 Like