Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X
Votes
8
Found in
2021.3.34f1
2022.3.18f1
2023.2.7f1
2023.3.0b4
6000.0.0b11
Issue ID
UUM-61575
Regression
No
float16_t is not working properly with DXC on DX12
Reproduction steps:
1. Open the attached “Float16Test.zip“ project
2. Open the “Assets/Outdoors.unity“ Scene
3. Enter the Play Mode
4. Observe the Game View
Expected result: The cube on the left is red and the cube on the right is green
Actual result: The cube on the left is black
Reproducible with: 2021.3.34f1, 2022.3.18f1, 2023.2.7f1, 2023.3.0b4
Reproducible on: M1 MacOS 14.2, Windows 10 (22H2)
Not reproducible on: No other environment tested
Note:
- Using the 2021.3.34f1 the cube's on the left shader is red, but it is shifted to the right (it’s behind the green cube instead of next to it). Similar behaviour is seen on all of the versions using M1 MacOS
- The issue is only reproducible when using the DX12 Graphics API
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
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
- [Mobile] The Material is not visible when using the Decal Renderer Feature
- Uncaught TypeError: Cannot read properties of undefined is thrown when the tab is inactive for several minutes
SeanR10Chambers
Jan 25, 2024 12:54
I'm adding a link to the unity forum thread discussing this issue for clarity:
https://forum.unity.com/threads/unity-is-adding-a-new-dxc-hlsl-compiler-backend-option.1086272/page-2