Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X, 2022.2.X
Votes
0
Found in
2021.3.1f1
2022.1.1f1
2022.2.0a13
Issue ID
UUM-3052
Regression
No
[Linux] "PropertiesGUI() is being called recursively" warning produced when trying to open color picker when object picker is opened
Steps to reproduce:
1. Create a new project or open an existing one
2. Create a Material in Assets (Right-click -> Create -> Material)
3. Select the created Material
4. In Inspector click the Object Picker icon for Detail Mask field (or any other field with Object Picker option)
5. Click on the Color Picker icon next to Albedo field
Expected results: No errors or warnings
Actual results: "PropertiesGUI() is being called recursively. If you want to render the default gui for shader properties then call PropertiesDefaultGUI() instead" warning is produced
Reproducible with: 2020.1.0a22, 2020.3.32f1, 2021.2.16f1, 2022.1.0b14, 2022.2.0a9
Not reproducible with: 2019.4.37f1, 2020.1.0a21
Notes:
- Not reproducible on Mac
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
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
- Mouse and Pointer Events are called incorrectly in ScrollView with XRUIInputModule
- Memory leak occurs when repeatedly minimizing and maximizing the UI Builder window
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2022.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2021.3.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.