ShaderLab's "Integer" type does not work with animations

I’m unsure if anyone has been able to notice this, but when I was using the new Integer type instead of Int while animating the property, for some reason it won’t record the change in values. Is this intended behavior or was this something completely looked over when the new data type was made?

Hey, sounds like a bug to me :slight_smile:
May I ask you to file a bug report?
Thanks!

Report has been submitted, hopefully it will get resolved

1 Like

Apparently it’s something that’s beyond a bug, so I submitted it as a feature request.

1 Like