Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
0
Found in
2019.4
2020.3
2021.1
2021.2
2022.1
Issue ID
1345758
Regression
No
Integer variables of a Compute Shader show up as Floats in the Frame Debugger
How to reproduce:
1. Open the attached "case_1345758" project
2. Open the "ComputeUAVTexFlow" Scene
3. Go "Window -> Analysis -> Frame Debugger"
4. In the Frame Debugger window click on Enable
5. Enter the Play Mode
6. Repeat the 3rd step
7. Select the "Compute Shader"
8. Observe Floats values
Expected results: The "_Size" value is an Integer hence not displayed under the Floats field
Actual results: The "_Size" value is a Float and displayed under the Floats field
Reproducible with: 2019.4.31f1, 2020.3.19f1, 2021.1.23f1, 2021.2.0b15, 2022.1.0a10
Note: The 3rd step is repeated because the information is not displayed about an Event if the Frame Debugger hasn't been enabled once before entering the Play Mode
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Package signature validation unexpectedly return an invalid signature status if the validation check is done after the code signing certificate validaty range has passed
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a16
Resolution Note (fix version 2021.2):
Fixed in 2021.2.9f1