Search Issue Tracker
Fixed in 2018.1.X
Votes
15
Found in
2017.2.0f3
Issue ID
962515
Regression
Yes
Building with VRWorks fails with a shader error in UnityCG
Steps to reproduce:
1. Download and open the project on a 9xx+ Nvidia card
2. Try to build for standalone
Expected: build succeeds
Actual result: Error building Player: Shader error in 'Sprites/Mask': undeclared identifier 'IN' at /Program
Reproduced with 2017.2.0b2, 2017.2.0f3, 2017.3.0b6, 2018.1.0a1
Not reproduced with 2017.2.0b1
Regression introduced in 2017.2.0b2
Notes:
- Forcing a recompile of the project appears to fix the problem until the next launch
- A change in the UnityCG appears to be the cause of interference from the plugin
Comments (2)
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
- Cancelling a Package installation leads to invisible compilation errors preventing the user to enter Play Mode when the “Cancel” button is clicked, and does not actually cancel the package install as it appears in the Project after the Editor is restarted
- NullReferenceException occurs when searching presets in “Select Preset” window after selecting a GLTF Importer preset
- Dynamic TMP_Font asset shows up as modified in source control when TextMeshPro text using it is changed
- “Output value ‘outMotionVec’ is not complete” warning logged after creating Canvas Shader Graph Asset
- SVG Image Component loses Source SVG Image field references when upgrading to a different Vector Graphics package version
majorthom13
Dec 23, 2017 02:00
The problem is NVIDIA VRWorks, uninstall it and everything is 100%.
majorthom13
Dec 23, 2017 01:11
I was having this after updating to 2017.2.0f3, so updated to 2017.3.0f3, same persistent issue. Can't build.
Please fix and update us.