Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.17.6-preview
Issue ID
ADDR-1871
Regression
No
Addressables don't detect IPreprocessShaders changes after building new script
How to reproduce:
1. Open the user's attached "BugAddressablesIPreprocessShader.zip" project
2. Go to Window -> Asset Management -> Addressables -> Groups
3. Clean the Cache (Build -> Clean Build -> All)
4. Build the Script (Build -> New Build -> Default Build Script)
5. Uncomment everything in the "StripShader" script
6. Repeat step 4 and then Build And Run
7. Observe the Cube in the Player
Expected result: Cube is green (IPreprocessShaders change was detected)
Actual result: Cube is red (IPreprocessShaders change was not detected)
Reproducible with: 1.16.6, 1.17.6-preview (2018.4.32f1, 2019.4.22f1, 2020.3.1f1, 2021.1.0b12, 2021.2.0a9)
Note:
- It's possible to work around this by cleaning the Cache in step 6 before building a new script
Comments (1)
-
Peter77
Mar 18, 2021 15:22
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
[VersionedCallback] was implemented for adding basic change detection to existing build callbacks. To support the requested use case, this would require changes to the engine callback interfaces which are API breaking changes, additional changes to SBP and the native engine build pipelines would be necessary to support this as well. Due to the scope of that work, and the breaking nature of the requested change, this is not a change we will do at this time.