Hi! I’m working on some VFX for a an app which include some transitions among other things and I was hoping to use vertex offsets in the ShaderGraph but it seems that anything linked to the inputs on the vertex side of the graph are removed?
I tested this by creating a working shader that animated the y position over time and added an input multiplier. Everything works as expected in the Editor but both the PlayOnDevice and on the headset the multiplier input not only doesn’t update but it feels like both the input get and the multiplier node were both stripped from the shader as the sine movement works, but if the multiplier was there with a zero value the movement shouldn’t happen.
I was wondering if it was somehow related to the timeline bug and as such would the MarkDirty(Renderer) added in 1.2.3 solve this issue?
This is using 0.6.2 which I’m currently stuck with for but knowing this could be fixed with an update might help my case!
Cheers, Stefan
We’ve made a lot of changes since 0.6.2. Without a repro project, I’m not sure exactly what might be going wrong here, or whether it’s fixed in a more recent version. Feel free to submit a repro case and let us know the incident number (IN-#####) if you want us to investigate your specific issue.
That said, how are you setting the property values? If it’s through a MaterialPropertyBlock, that’s something we only added support for recently (1.2.3), so it definitely won’t work in 0.6.2. Material properties animated via the timeline are effected via MaterialPropertyBlocks, also, so that would apply to them as well.
Thanks for getting back to me. I’m painfully aware of the improvements since 0.6.2, I try not to look at the changelist too much as it makes me sad 
I wasn’t using MaterialPropertyBlocks and I ended up bypassing the inputs in question entirely and adjusting the offset texture transitions directly in the compute shader.
But I have found what might have been the issue. I was assuming the inputs weren’t working at all, but it was really inconsistent as some were definitely working so I became confused. I went through many iterations and then realised that regardless of the shader stage, if I drag more than one copy of the input off of the blackboard only the first one one works! So I have very messy, but working graphs now.
That sounds familiar; I think we might have fixed that in 0.6.3 (“Fixed KeyNotFoundException when using multiple instances of the same input property in a shader subgraph.”). There was a previous Discussions thread about it.
Anyway, glad to hear that you found a workaround!
