Search Issue Tracker
Fixed
Fixed in 2022.3.20f1
Votes
0
Found in
2022.3.19f1
Issue ID
UUM-64703
Regression
Yes
”Field type UnityEngine.UIElements.BoundsIntField is not compatible with Vector3Int property” warning appears when selecting a tilemap in the Tile Palette window if using the Debug window
How to reproduce:
1. Open the attached “grid.zip” project
2. Open “SampleScene” Scene (Assets > Scenes)
3. Set the Inspector window to Debug mode
4. In the Hierarchy window, expand “Grid” GameObject and select “Tilemap”
5. In the Scene window, press the “Open Tile Palette” button
6. In the Tile Palette window, choose select tool and press the “Edit” button
7. Press on the Palette
8. Observe the Console window
Expected result: No warnings
Actual result: “Field type UnityEngine.UIElements.BoundsIntField is not compatible with Vector3Int property "m_Position.m_Position"” warning appears
Reproducible with: 2022.2.0a9, 2022.2.21f1, 2022.3.19f1
Not reproducible with: 2021.3.35f1, 2022.2.0a8, 2023.2.12f1, 2023.3.0b9
Fixed in: 2022.3.20f1
Reproduced on: macOS 14.2.1 (Intel)
Not reproducible on: No other environment tested
Note: The Tilemap Extras package version doesn’t affect the issue
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note (fix version 2022.3.20f1):
Fixed in: 2022.3.20f1