Search Issue Tracker
Fixed in 2018.2
Fixed in 2017.4, 2018.1
The Editor is failing to check the CacheServer when increasing AssetPostProcessor Version and adding new assets
How to reproduce:
1. Download attached project (Ensure that CacheServer is enabled in the editor, I have reproduced using Local Mode)
2. Open project, allow the library to build
3. Close Project
4. Open Assets\Editor\EditorPostProcessor.cs, increase m_Version to next number
5. Copy in "FolderToCopyIntoAssets" into Assets directory of the project
6. Reopen project
Actual result: The Editor is failing to check the CacheServer when increasing AssetPostProcessor Version and adding new assets.
Also attached are an example of good and bad behaviour logs, good contains a line like this:
----- Cache Server detail: Total assets requested: 100, Cached Assets: 0, Not available: 100, Not supported: 0.
If the cached assets already exist, then it should read :
----- Cache Server detail: Total assets requested: 100, Cached Assets: 100, Not available: 0, Not supported: 0.
Bad does not produce this line, it does not appear to check the cache server for assets, note that both contain an initial check for a small number of"not supported" assets, I have observed this in customer project also,
To reproduce the "good" log, repeat the steps, but omit step 4.
Reproduced with: 5.6.2p4, 2017.1.3p1, 2017.2.2f1, 2017.3.1p3, 2018.1.0b10, 2018.2.0a3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Custom Inspectors OnDisable still called after Asset has been deleted
- Native Plugin regression from 2018.x results in "DllNotFoundException" error
- [Android] "AndroidETC2FallbackOverride.Quality32BitDownscaled" does not work on an Atlas created with the Legacy Sprite Packer
- Debug.Log() Context not highlighted when pressed after printing in Test Runner's EditMode
- [Terrain] Painting on newly created neighboring terrains results in null reference errors