Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.8.3
Issue ID
ADDR-1262
Regression
No
[Addressables] GameObject shader is not loaded in when using Use Existing Build in Play Mode Script
To reproduce:
1. Open up users attached project
2. Go into Addressables Groups (Window -> Asset Management -> Addressables -> Groups)
3. Build the scripts (Build -> New Build -> Default Build Script)
4. In Play Mode Script choose Use Existing Build
5. Enter Game View (or open Scene View)
Expected result: GameObject is shaded properly and is yellow coloured because of its material
Actual result: GameObject is completely black
Reproduced in: 1.1.5 (2019.3.13f1), 1.8.3 (2018.4.22f1, 2019.3.13f1, 2020.1.0b8, 2020.2.0a10)
Notes:
-Play Mode Script -> Use Asset Database displays the expected result of this GameObject both in Game View and Scene View
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
Behavior is expected because "Optimize Mesh Data" in PlayerSettings is turned on. To make the GameObject render as intended, turn off "Optimize Mesh Data" and clean the build cache + run a new build.