Search Issue Tracker
Fixed
Fixed in 6000.0.60f1, 6000.2.9f1, 6000.3.0b6, 6000.4.0a2
Votes
0
Found in
6000.0.58f1
6000.2.6f1
6000.3.0b3
6000.4.0a1
Issue ID
UUM-120318
Regression
No
Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
How to reproduce:
1. Open the project “IN-117238_DDSLRGGPUUploadIssue”
2. In the Game tab, notice the metallic, rough, reflective shading
3. Change the Graphics API from Direct3D11 to Vulkan (Edit → Project Settings → Player → Other Settings → move Vulkan to the top of the list)
4. In the Game tab, notice the shading change
Expected result: The object remains metallic, rough and reflective
Actual result: The object loses the metallic, rough and reflective properties
Reproducible with: 6000.0.8f1, 6000.0.58f1, 6000.2.6f1, 6000.3.0b3, 6000.4.0a1
Could not test with: 2023.1.0a1, 6000.0.7f1 (many package dependency issues)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: The issue is only present with Vulkan, DX12 and DX11 works as expected
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment