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
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
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.