Search Issue Tracker
Won't Fix
Votes
4
Found in
2021.3.9f1
2022.1.14f1
2022.2.0b6
2023.1.0a8
Issue ID
UUM-12810
Regression
No
[Addressables] Terrain Normal Maps are not loaded when loaded using Addressables
How to reproduce:
1. Open the attached "IN-12293" project
2. Open the Addressable Groups (Window > Asset Management > Addressables > Groups)
3. Build the Addressables (Build > New Build > Default Build Script)
4. Set the Addressables Groups Play Mode Script to "Use Existing Build"
5. Open the "Scene_BOOT" Scene (Assets/Game Framework/Scenes)
6. Enter the Play Mode
7. Press "Press To Start"
8. Build the Base then Exploration Center by pressing on the middle square then the right one
9. Press on the Exploration Center
10. Press "Venture Out" then "Start"
11. Inspect the Terrain in Scene/Game View
Expected results: Terrain has Normal Maps
Actual results: Terrain doesn't have Normal Maps
Reproducible with: 1.20.5 (2021.3.9f1, 2022.1.14f1, 2022.2.0b6, 2023.1.0a8)
Could not test with: 1.20.5 (2020.3.39f1) because of namespace errors from downgrading
Tested on:
Windows 10
Notes:
- The issue isn't reproducible if Play Mode Script is set to "Use Asset Database"
- The issue is also reproducible in Standalone Build and Android
Comments (1)
-
Gamestock
Jun 09, 2023 06:31
any update?
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
- "Browse" button for Xcode in the "Build Profiles" window is too big
- USS styles fail to inherit correctly when contentContainer is overridden in a custom control
- Copying and pasting Animator Transitions leads to unexpected behaviour
- "ShaderGraph" misses a space in the "Project Settings" section
- UI Builder inspector’s checkbox fields can be activated when clicking anywhere in the value field
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.