Search Issue Tracker
Won't Fix
Votes
0
Found in
6.5.0
Issue ID
UUM-136155
Regression
No
Dynamic Buffer Container page navigation appears when more than 5 Elements are present, regardless of “Show” field value
Reproduction steps:
1. Create a new project
2. Install Entities package (Window > Package Management > Package Manager > Unity Registry > Entities)
3. Right-click on Hierarchy > New Sub Scene > Empty Scene…
4. Enter Play mode
5. Select newly created Sub Scene (Default World > New Sub Scene)
6. Enter any number greater than 5 in the Buffer field in the Inspector
7. Expand the Buffer field, set the “Show” field value to a number greater than the number of Elements (e.g. 10 or 20)
8. Observe the Buffer field
Actual result: Page navigation appears as soon as there are more than 5 elements
Expected result: Page navigation does not appear when the number of elements fits within the selected "Show" field value
Reproducible with: 6.5.0 (6000.5.0a7, 6000.5.0a8)
Couldn’t reproduce with: 1.4.5 (6000.3.10f1), 6.4.0 (6000.4.0b11), 6.5.0 (6000.5.0a6) (No Editor World GameObject)
Reproduced on: macOS Tahoe 26.3 (M4)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.
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.