Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
Issue ID
1041696
Regression
No
When the pipeline package changes, old shadergraphs may be broken until they're manually opened and re-saved by users.
If the pipeline has changed in such a way that the shaders are broken and need to be recompiled, can we recognize that and recompile them?
Currently if you have a shader graph that you made in e.g. SG 0.1.7, and then you move to SG 0.1.14 / LW 0.1.23, the shader will be pink until you open it and click Save to recompile your shader. Automating this would be nice as it's very scary and confusing for users at first, and then really annoying and boring for users later.
stramit commented on Jan 24
This uses Scripted importer (see: ShaderGraphImporter.cs) you should be able to bump the version which will cause reimport.
stramit commented on Jan 24
hrrm looks like this isn't working. Reached out the asset team.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Linux] Cannot reorder GameObjects in the Hierarchy when the AI Assistant package is installed
- [iOS] Text Input field stops receiving changes when the "Cancel" button is used on the soft keyboard
- [WebGPU] URP RenderGraph RenderPass doesn't clear textures
- Query Builder items display raw code style names instead of human readable labels in search field
- “+” button does nothing and has no functionality when clicked in Human Template "Bone Template" list
Add comment