Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3.0b11
2019.3.3f1
2020.1
2020.2
Issue ID
1225627
Regression
No
Remote Asset Cache fails to download some Artifacts when using Asset Import Pipeline V2 with Unity Accelerator
How to reproduce:
1. Install Unity Accelerator
2. Get its IP from the final screen of the installation
3. Open the attached project
4. Enable the Cache Server in the Project Settings
5. Insert the given IP in the "IP address" field of the Project Settings
6. Close the project
7. Delete the Library folder from the project
8. Open the project
9. Repeat steps 6, 7, 8, 6
10. Open the Editor.log from C:\Users\username\AppData\Local\Unity\Editor\Editor.log
Expected result: Everything from the Remote Asset Cache is downloaded successfully
Actual result: Some of the Artifacts fail to download from the Remote Asset Cache as indicated in the Editor.log
Reproducible with: 2019.3.0b11, 2019.3.7f1, 2020.1.0b3, 2020.2.0a5
Could not test with: 2019.2.21f1 and earlier (no Asset Import Pipeline V2), 2019.3.0a1, 2019.3.0b6 (connection failed), 2019.3.0b10 (uploaded to cahce but didn't read from it)
Notes:
-All the failed downloads are marked by "RemoteAssetCache - Download - Artifact - success:false"
-This occurred with HDRP and URP packages
-This doesn't reproduce with all the packages set to default ones
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
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a21
Resolution Note (fix version 2020.1):
Fixed in 2020.1.4f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.9f1