Search Issue Tracker
Duplicate
Votes
1
Found in
2019.4
2019.4.29f1
Issue ID
1361049
Regression
No
[Android] Cull off Shader throws "Non system-generated input signature parameter" error when using Android Platform
How to reproduce:
1. Open the user's attached "URPTest.zip" project
2. In the Project window select the "NM_Foliage" Shader found in the Assets/NatureManufacture Assets/Foliage Shaders folder
3. Observe the errors in the Inspector
Expected results: No errors are shown
Actual results: The "Non system-generated input signature parameter (TEXCOORD) cannot appear after a system generated value" is shown
Reproducible with: 2019.4.30f1
Could not test with: 2020.3.17f1, and higher because of the "Invalid conditional expression" error
Note:
- Reimporting the Shader ("NM_Foliage" found in the NatureManufacture Assets/Foliage_Shaders folder) removes the error but it will reappear once all Assets are reimported
- Tested and reproduced with URP
- After switching to Standalone Platform and Graphics API to D3D12 and then switching back to Android Platform the error would not appear even after Reimporting all
- Does not reproduce when switched to iOS Platform
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment