Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.44f1
2022.3.47f1
6000.0.21f1
6000.1.0a7
Issue ID
UUM-82687
Regression
No
Imported Object section disappears after deselecting file from the Materials tab
Steps to reproduce:
- Create a new URP project.
- Import the files in the attached Tree.zip.
- Select the Decal_and_Mesh_Detail.st file in Project view.
- In the Import Settings (view in Inspector), select the Materials tab. Scroll down and see the "Imported Object" section.
- Select another file in the Project view, then reselect Decal_and_Mesh_Detail.st.
- Scroll down in the Inspector and look for the "Imported Object" section.
Actual results: The "Imported Object" section is no longer there, and does not reappear if you deselect and reselect.
Expected results: The "Imported Object" section does not disappear.
Reproducible with versions: 6000.0.21f1, 2022.3.47f1, 2021.3.44f1, 2021.2.0a1
Tested on (OS): MacOS Sonoma 14.6.1
Notes:
- This section will not return until you select the Model tab, then deselect and reselect the .st file.
- This section will not be visible if your imported object opens on the Material tab immediately after import.
- This also occurs with .fbx imports, so it is not SpeedTree specific.
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
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.