Search Issue Tracker

Fixed in 7.1.0

Votes

3

Found in [Package]

5.13.0

Issue ID

1153419

Regression

Yes

[ShaderGraph] Unlit Graph doesn't compile when it has a property called "_BaseMap"

Package: Shader Graph

-

How to reproduce:
1. Open the attached "case_1153419-ShaderGraphRef" project
2. In the Project window, reimport the "UnlitGraph-broken.shadergraph" asset

Expected results: The shader compiles successfully
Actual results: The shader doesn't compile with a "redefinition of '_BaseMap'" error

Reproducible with:
ShaderGraph 5.13.0 (using 2019.1.3f1, 2019.2.0b2)
ShaderGraph 6.5.3 (using 2019.2.0b2, 2019.3.0a2)

Not reproducible with:
ShaderGraph 4.10.0 (using 2018.4.0f1)

Comments (2)

  1. LW

    Sep 05, 2019 11:56

    I've become very frustrated with all of the talk for almost 2 years of moving to a scriptable pipeline and it's still not in a production ready state. Perhaps it would have been better to not announce this 'exerpimental' feature until it's closer to live....

  2. Jackrabbit82

    May 14, 2019 03:08

    Really need for efficient solution on this whole graph pipeline. Using common naming in shaderlab has always been the key to avoid mismatched textures when changing shader type. This is definitely one of the most annoying issues I've had with SRP and shadergraph.

    Let's say you're converting packages bought on the store for the SRP you'll be stuck relinking everything by hand or creating a bunch of editor tools to correctly replace textures. There should be a standardized naming convention in shadergraph as well.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.