Search Issue Tracker
By Design
Votes
2
Found in
2018.1.0b11
2018.1.0b13
Issue ID
1023045
Regression
Yes
[2018.1][Shaders] No matching 4 parameter intrinsic function for tex2D on a specific shader
To reproduce:
1. Open repro project
2. Select 'MicroSplat 1' shader
Expected: shader will work without any errors
Actual: 'Shader error in 'MicroSplat/MicroSplat_demo': 'tex2D': no matching 4 parameter intrinsic function; Possible intrinsic functions are: tex2D(sampler2D, float2|half2|min10float2|min16float2) tex2D(sampler2D, float2|half2|min10float2|min16float2, float2|half2|min10float2|min16float2, float2|half2|min10float2|min16float2) at line 1099 (on d3d11)' error is thrown
Reproduced: 2018.1.0b13
Not reproducible: 2017.1.3f1, 2017.2.1p3, 2017.3.2f1, 2018.1.0b10, 2018.2.0a8
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
JeanSmall
Apr 24, 2018 16:42
Could we have a bit more information as of why this behavior is "by design" ? Nvidia's documentation seems to say that there are 4 intrinsics versions of the function : http://developer.download.nvidia.com/cg/tex2D.html