Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.2.0f3
Issue ID
728304
Regression
No
[GL][ES] does not render compute shaders correctly
Steps to reproduce:
1. Download attached project "Fluidity.zip"
2. Open it via console with launch parameter "-force-glcore45"
3. Play scene "_RuinsDemo"
4. Observe that no error or warning is displayed and shaders are displayed wrong
Note: Everything works as expected with standard configuration (no launch parameters) using DX11
For Unity 5.4 launch parameters don't matter, as you have to choose graphics API from Player Settings menu (select GLCore).
Comments (1)
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
- 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
sirshelley
Nov 01, 2015 16:11
Same here with custom shaders