Search Issue Tracker
Not Reproducible
Votes
0
Found in
2021.3.22f1
Issue ID
UUM-33339
Regression
No
Custom Shader is rendered differently in Build
Reproduction steps:
1. Open the attached “ml.zip“ project
2. Open the “SampleScene” scene
3. Build And Run the project
4. Observe the Build and Game window
Expected result: Build and Game window render the same
Actual result: Build and Game window are not rendered the same (Grass in standalone Build gets diagonal lines, in WebGL Build turns darker and stretches out vertically)
Reproducible with: 2021.3.22f1
Could not test with: 2020.3.47f1, 2022.2.15f1, 2023.1.0b11, 2023.2.0a10 (.blend files get corrupted after upgrading and downgrading streams preventing reproduction, importing them from a not-downgraded copy of the project doesn't work either)
Reproduced on: Windows 10
Not reproduced on: macOS Monterey 12.6 (Intel)
Notes:
-Not reproducible when Debug Mode and Frame Debugger are enabled
-Custom Shader renders differently in Standalone and WebGL Builds
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Please provide a simplified repo that identifies the issue.