Search Issue Tracker
Fixed
Fixed in 6000.0.49f1, 6000.1.2f1, 6000.2.0a8
Votes
0
Found in
2022.3.60f1
6000.0.40f1
6000.1.0b8
6000.2.0a5
Issue ID
UUM-97850
Regression
No
Converting an output to Mesh output results in broken shader compilation and error
Steps to reproduce:
- Import learning templates
- Open MultiStripSingleBurst VFX
- Convert output to URP/HDRP (Un)Lit Mesh
Actual results: Shader compilation breaks and shader errors are thrown
Reproducible with versions: 6000.0.33f1, 6000.2.0a5
Not reproducible with versions: n/a
Can’t test with versions: n/a
Tested on (OS): Windows
Notes:
- i didn't check other streams to confirm if it is a regression
- seems to happen with Mesh Unlit/Lit Output only, tested converting to quad, point and couldnt repro
Errors:
[Worker4] Shader error in 'Hidden/VFX/MultiStripSingleBurst/Robot Arms/A/Robot Pliers Mesh': undeclared identifier 'id' at Templates/VFX/MultiStripSingleBurst.vfx(3277) (on d3d11)
Compiling Subshader: 0, Pass: <Unnamed Pass 4>, Vertex program with <no keywords>
Platform defines: SHADER_API_DESKTOP UNITY_ENABLE_DETAIL_NORMALMAP
Shader error in 'Hidden/VFX/MultiStripSingleBurst/Robot Arms/A/Robot Pliers Mesh': undeclared identifier 'id' at Templates/VFX/MultiStripSingleBurst.vfx(1142) (on d3d11)
Compiling Subshader: 0, Pass: <Unnamed Pass 1>, Fragment program with <no keywords>
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:
Forward-ports for this version need to be handled at a later time.