Inconsistent behavior loading textures in stride

I need to load a sequence of 16bit images, so i tried with the node ImagePlayer (FrameBased Stride).
I then realized that the loaded textures out of a normal FileTexture node and the ImagePlayer node (which internally uses a TextureReader) are different.
It looks like the Texturereader node cannot load the 16bit images.

Is there an alternative to ImagePlayer that can load 16bit images?
…also, is this a stride bug or just a known feature?

Have you tried converting your PNG to DDS using R16_Unorm?

I was looking for a solution that doesn’t imply converting files… (big pipeline here. that would be another step).
…and mainly i was curious about the finding, this difference between the two nodes, and why is that, if there’s a reason for it.
@tonfilm might be the one that knows everything about :)

Ok, but I’d consider a format different than PNG. It’s really bad performance-wise for loading/playback.

2 Likes