[BUG] "Additional Use Passes" getting randomly deleted??

[jake_from_bend]

Some of our shaders rely on an outline pass from a different shader, using the "Additional Use Passes" feature.
It works great. No complaints.
However, there seems to be a bug with ASE when i leave the shader graph open in the editor and hit "Play." (i'm honestly not certain if those conditions are relevant, but i've only ever noticed this happening while both of those are true.)
Every so often, i'll notice that my "Additional Use Pass" instruction is gone after playing in editor.

Unfortunately, i'm unable to come up with a reliable set of repro steps, but i was wondering if anybody has reported anything similar?

Here's specifically what seems to be happening:

1. Amplify shader points to pass from a different shader:

usepassA.JPG (13.62 KiB) Viewed 1323 times

2. I play the game in editor with the shader graph open in ASE...

3. Pass gets removed from the shader somehow:

usepassB.JPG (12.78 KiB) Viewed 1323 times

[Ricardo Teixeira]

Some of our shaders rely on an outline pass from a different shader, using the "Additional Use Passes" feature.
It works great. No complaints.
However, there seems to be a bug with ASE when i leave the shader graph open in the editor and hit "Play." (i'm honestly not certain if those conditions are relevant, but i've only ever noticed this happening while both of those are true.)
Every so often, i'll notice that my "Additional Use Pass" instruction is gone after playing in editor.

Unfortunately, i'm unable to come up with a reliable set of repro steps, but i was wondering if anybody has reported anything similar?

Here's specifically what seems to be happening:

1. Amplify shader points to pass from a different shader:

usepassA.JPG

2. I play the game in editor with the shader graph open in ASE...

3. Pass gets removed from the shader somehow:

usepassB.JPG

Interesting issue, I was able to replicate it once. Thankfully, it seems to be specific to the UI as the shader itself keeps the pass.

We'll pass it on to our developers for further examination.

Thanks!