Search Issue Tracker
Won't Fix
Votes
6
Found in
2022.3.15f1
2023.2.3f1
2023.3.0a17
Issue ID
UUM-58303
Regression
No
The construction of a specific class breaks the binding Bool references and does not allow them to be toggled on back by hand when working in the Custom Editor window
How to reproduce:
1. Open the “Procedural Map Test“ project
2. Open the “SampleScene“
3. Open the “Assets > WFC Tests > MyGrid.asset“ in the Inspector
4. Switch the Inspector to the Normal mode
5. Press on the “Open Grid Editor“ button
6. Drop down the “Type of Grid“ menu and choose “Square3D“
7. Press on the “Open Grid Editor“ button
8. Toggle on the check-box that is located in the top-right corner of the “Tile” square
Expected result: The “Tile” square check-box gets toggled on
Actual result: The “Tile” square check-box does not get toggled on
Reproducible with: 2022.3.15f1, 2023.2.3f1, 2023.3.0a17
Could not test with: 2021.3.33f1 (Could not fix the Console errors)
Reproducible on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
Notes:
- The issue stems from the 347 and 348 lines in the “GridConfiguration.cs“ script
- Also when restarting the project, and observing the “MyGrid“ asset in the Inspector with Debug mode toggled on the “Connecting Tiles Types Config“ arrays “Tile Type“ element references get “broken“ (set to None) until the “Open Grid Editor“ button is pressed
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
- Crash on ConvertBufferToEXRBuffer when Lighting Generation is cancelled
- [URP] TrailEffect in URP package samples does not draw Trail Effect
- "NullReferenceException" error is thrown when calling UIDocument.runtimePanel in OnEnable with ExecuteInEditMode
- Graphics.Blit() performs the operation only to the last display when a multi-display environment is used
- [Windows] Multiple Separation Lines are present in the Light Create Menu
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.