Enabling Accelerator for v2 on a 2019.3.0b6 project breaks asset imports on 2019.3.0b3

I spent quite a while today debugging why even after a full reset of our project (we tried upgrading to 2019.3.0b6 with Accelerator but decided to go back to 0b3) it still froze on importing.

Turns out, the preference to use Cache Server on v2 asset database is a shared preference between 0b6 and 0b3. So the 0b3 project now had the preference of "Cache Server: on" pointing to the Accelerator server. This resulted in a complete freeze on asset reimport, library deletion didn't bring anything, it would always get stuck at some point.

Workaround was to create a new project on 0b3, disable the Cache Server completely again in Preferences and then launching the original 0b3 project. Voilá, reimporting just fine, processor is doing something, loading bar is progressing...

That's a really weird side effect!

 

Yes you are correct, @fherbst. This is an unfortunate side effect of setting the global editor preferences for using the Accelerator due to bugs in earlier beta versions. Apologies for the crappy freeze, and thanks for coming up with a workaround.

Additionally, if you'd like to continue using the older beta versions, you can also set the server IP values for a specific project instead of relying on the global setting by opening the beta 6 project, go to the "Edit => Project Settings..." menu option and setting the "Cache Server" value: