Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.9f1
2022.1.15f1
2022.2.0b7
2023.1.0a9
2023.2.0a1
Issue ID
UUM-14211
Regression
No
[CacheServer] After you disable CacheServer during ongoing upload, all next uploads will stuck
Steps:
- preparation: clear Accelerator cache folder
1 Create new HDRP project (or use any relatively big project you have)
2 Open project and enable Cache Server in Project Settings (connect to working instance of Accelerator, e.g. local one on your machine)
3.1 Close Editor
3.2 Delete Library folder
3.3 Reopen Editor
4 Wait while Editor loads and becomes responsive, then go to the right lower corner and unfold "Background Tasks" window - there should be "Upload artifacts" progress bar
5 While it is still uploading go to Preferences->AssetPipeline and disable CacheServer
6 Enable CacheServer again
7 Go to Project browser, select any big folder (I use Assets\SampleSceneAssets\Textures for my testing) and RMB->Reimport it
8 After it is finished - there should be a new progress bar in Background Tasks" window
9 Check - that progress bar is stuck
Actual result: progress bar is stuck
Expected result: progress bar is NOT stuck
!image-2022-09-08-17-34-50-110.png!
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Not reproduces on 2023.2.
Most probably it is still reproducible on 2021 and 2022, but because it is low priority and a corner case - we are not going to fix it there
Resolution Note (2023.2.X):
Not reproduces on 2023.2.
Most probably it is still reproducible on 2021 and 2022, but because it is low priority and a corner case - we are not going to fix it there