Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.4
2019.4.5f1
2020.1
Issue ID
1275444
Regression
No
[Accelerator] -EnableCacheServer command line argument does not properly connect to Accelerator
Reproduction steps:
1. Setup a Unity Accelerator
2. In the same machine, create a new Unity Project
3. In Preferences -> Asset Pipeline (or Cache Server), make sure that "Cache Server Default Mode" is set to "Disabled"
4. In Project Settings -> Editor -> Cache Server, make sure that "Mode" is set to "Use global settings"
5. Close the project
6. Reopen the project with the following command line arguments - "-EnableCacheServer -cacheServerEndpoint localhost"
7. Observe the state of the connection to the Cache Server
Expected result: The project is connected to the specificed Cache Server
Actual result: The project is not connected to the specified Cache Server
Reproducible with: 2019.4.32f1, 2020.1.0a21
Not reproducible with: 2020.1.0a22, 2020.3.22f1, 2021.1.28f1, 2021.2.2f1, 2022.1.0a1, 2022.1.0a15
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on "block_merge_next" when entering PlayMode in a scene from the "POLYGON War Map - WWI - Low Poly 3D Art by Synty" package
- [Win ARM] URP projects fail to build that have a space in the name
- [Android][OpenGL]Soft Shadows contain artifacts when the OpenGL Graphics API is used
- The particle system prewarm flag is ignored when calling the Start function after the Stop function
- The Scene view flickers when moving around if there are visible Hair Shaders
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a22