Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2020.3.35f1
2021.3.6f1
2022.1.9f1
2022.2.0b1
Issue ID
UUM-3330
Regression
No
[HDRP] [DXR] TextMeshPro SG compilation errors when enabling Path Tracer
Version tested:: 2020.3.31f1 + HDRP 10.8.1 + TMP 3.2.0-pre4 (stored locally in repro project)
Steps to reproduce:
1) Open attached project, OutdoorsDXRScene
2) Make sure TMP object in the scene uses TMP_SDF-HDRP LIT or TMP_SDF-HDRP UNLIT Shader Graphs
3) Enable Path Tracer in the scene
4) Observe SG compilation errors and TMP object not being rendered properly
Errors:
Shader error in 'TextMeshPro/SRP/TMP_SDF-HDRP LIT': no matching function for call to 'GetSurfaceNormal_float' at 13637(13) (on d3d11)
Shader error in 'TextMeshPro/SRP/TMP_SDF-HDRP LIT': unknown type name 'texture2D'; did you mean 'texture'? at Pro/Shaders/SDFFunctions.hlsl(25) (on d3d11)
Comments (1)
-
Ciryus
Sep 01, 2022 09:08
Hi,
facing this problem too on Console platforms.
To fix that change texture2D to Texture2D in parameter types in the GetSurfaceNormal_float in SDFFunctions.hlsl(25).
It was:
void GetSurfaceNormal_float(texture2D atlas, float textureWidth, float textureHeight, float2 uv, bool isFront, out float3 nornmal)It will then be:
void GetSurfaceNormal_float(Texture2D atlas, float textureWidth, float textureHeight, float2 uv, bool isFront, out float3 nornmal)
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
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that this issue is not aligned with our current development priorities and focus areas (UI Toolkit). As such, we have decided not to invest time and resources into addressing it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.
Resolution Note (2022.2.X):
Thank you for bringing this issue to our attention. After careful consideration, we have determined that this issue is not aligned with our current development priorities and focus areas (UI Toolkit). As such, we have decided not to invest time and resources into addressing it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.