Search Issue Tracker
Fixed in 2017.2.X
Votes
1
Found in
5.6.0f3
Issue ID
910302
Regression
Yes
Editor returns an Internal compilation error when using 2 or more custom operators in one statement
Steps to reproduce:
1. Download and open the attached project
2. Observe console
Expected result: compilation succeeds normally
Actual result: "Internal compiler error: Index was outside the bounds of the array."
Reproduced on 5.5.0b9, 5.5.3p1, 5.6.0p4, 2017.1.0b4
Not reproduced on 5.4.5f1
Regression introduced in 5.5
Notes:
-The compilation error does not actually appear inside a code editor(Visual Studio)
-1 operator does not cause the error
Verified FIXED 5.6.1p3
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
- Shader Compilation for projects with lots of Shaders can be slow (i.e. VFX Graph asset heavy projects)
- Crash on RebuildTransformHierarchyOrMarkForDestruction when opening a scene
- The Editor hangs when opening a project that uses local packages and Version Control
- Area Light is culled when Camera Frustrum is outside the lights range
- The characters of the bottom option in the Scene View Debug Draw Mode dropdown menu are cut off
Invertex
May 13, 2017 09:16
Seems to be related to this issue which seems to have come back in p3/p4...
https://issuetracker.unity3d.com/issues/shader-errors-appear-in-console-after-building-postprocessing-asset-on-vulkan