Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.22f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-83433
Regression
No
Clicking on the assigned by default "Lightmap Parameters" pings "Assets" folder even though the Asset is not there
How to reproduce:
1. Create a new HDRP Project
2. In the Project window, right-click -> Create -> Rendering -> Lighting Settings
3. Open the created Asset in the Inspector and navigate to the "Lightmap Parameters" under the "Lighmapping Settings"
4. Click on the field and observe the ping
Expected results: The correct file is pinged in the Project window or nothing is pinged at all
Actual results: "Assets" folder is pinged in the project window even though the Asset is not there
Reproducible with: 6000.0.22f1
Can't test with: 2021.3.44f1, 2022.3.49f1 (Different implementation of the field)
Reproducible on: macOS Sequoia 15.0 (M1)
Not reproducible on: No other environment tested
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:
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.