Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.1.0p2
Issue ID
955176
Regression
Yes
Building Standalone throws ... program 'frag_surf': Unrecognized sampler 'samplerunity_lightmap' .. error with specific shaders
Steps to reproduce:
1. Download and open the attached project
2. Build for standalone
3. If no error is thrown, repeat step 2
Expected result: no error
Actual result:
"Error building Player: Shader error in 'Custom/ColorPicker': Fragment program 'frag_surf': Unrecognized sampler 'samplerunity_lightmap' - does not match any texture and is not a recognized inline name (should contain filter and wrap modes)."
(on d3d11)
Reproduced on 5.6.0b2, 5.6.3p4, 2017.1.1p4, 2017.2.0f1, 2017.3.0b3
Not reproduced on 5.5.4p2, 5.6.0b1
Regression introduced in 5.6.0b2
Problem disappears if the user goes to Edit -> Project Settings -> Graphics Settings and sets Shader Stripping -> Lightmap Modes to Automatic.
FIXED 2018.3.0a6
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
glitchers
Nov 07, 2018 11:48
My mistake - it doesn't fix the issue - the issue just doesn't occur 100% of the time.
glitchers
Nov 07, 2018 09:58
I had this issue because my custom shader was using the fallback "Diffuse". I changed it to "Standard" and the issue went away.
sbsmith
Jun 12, 2018 23:07
I am seeing this in 2017.3 and the suggested workaround does not solve the issue.
Jonas-Neuston
May 14, 2018 17:42
Is this going to be fixed for 2017?
Erik-Hegen
Feb 19, 2018 14:02
FIXED 2018.3.0a6??
I'll guess you mean Unity 2017.3?