This might imply that the shader is not

[next dagger]

Here is the inspector

It could be imperfect tho, perhaps unity has a better tool?

[slim copper]

Can't think of anything aside from it being an issue with loading the shader.🤔

Maybe try reference it directly.

[next dagger]

oh wait one sec, I make a mistake in commenting out new logic, let me fix it

[slim copper]

Or a typo/invisible character somewhere

[next dagger]

ah found an error! I guess I had to click show compiled code for the errors to pop up:

but it compiled correctly before I removed the multi_compile so not sure if this matters

yeah no its anew error I made sorry

[slim copper]

So it still doesn't work if you fix the errors?

[next dagger]

the errors are a result of me improperly removing the multi_compile lines without adjusting the rest of code properly

i put the multi_compile back in because its kinda responsible for the entire logic, let me try refercing directly like you suggest

[slim copper]

Just for the sake of testing, you could comment out one of the results. Multi compile is still a possible culprit if you ask me.

But yeah, try referencing it directly first.

[next dagger]

Not exactly sure how to reference it directly now that I look at it, trying to find constuctor on unity docs

[slim copper]

Wdym? You can just make the field serialized and assign it in the inspector.

[next dagger]

even for non -mono behavior?

[slim copper]

No. But you can serialize it in a different MonoBehaviour and pass the reference to your non MonoBehaviour class

[next dagger]

true, It seems I could also use FindKernel() method

ill do ur approach

[next dagger]

You were right, direct ref didn't help but commenting out everything properly did get rid off the issue

I just dont understand why