Search Issue Tracker
Active
Votes
0
Found in
2021.3.14f1
2022.1.23f1
Issue ID
UUM-21151
Regression
No
Lights are not responsive or sometimes don't work in Build when a model is loaded via Adressables
How to reproduce:
1. Open the user’s attached project “IN_19297“
2. Build And Run
3. Press any key → “SINGLEPLAYER” → “Titanic” → “Move To Spawn Selection” → Choose Region and start the game
4. Using Shift and “A”,” W”,” S”, “D” keys move to the ship side
5. Press Lights → General
6. Observe the Player
Expected result: lights work and are responsive in the Player
Actual result: lights are unresponsive and sometimes don’t work at all in the Player
Reproducible with: 2021.3.14f1, 2022.1.23f1
Couldn’t test with: 2020.3.42f1, 2022.2.0f1 (compiler errors), 2023.1.0a19 (hang while loading the project)
Reproducible on: Windows 10 Pro
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
Add comment