texelFetch does not have enough precision.

[devMiyax]

I have shader code following

Code: Select all

"  vec4 txindex = texelFetch( s_texture, ivec2(int(v_texcoord.x),int(v_texcoord.y)) ,0 );\n"
"  vec4 txcol = texelFetch( s_color,  ivec2( ( int(txindex.g*65280.0) | int(txindex.r*255.0)) ,0 )  , 0 );\n"

it seems txindex does not have enough precision, the seccond texelFetch retuns bad color.
This code works fine on Snapdragon and Tegra X1. Is there anyone know how can manage this issue?

Entire code is here.
https://github.com/devmiyax/yabause/blo ... shaderes.c

Thanks in advance.

[Daniel Gessel]

Have you tried specifying highp? Which pi is this on, pi4 or other?

[Notthesameman]

This is happening on the pi4

[Daniel Gessel]

Rumor is the VC6 in the Pi4 has support for f16 at double rate, so it may default to that lower precision unless you specify highp. I haven’t tested with the latest drivers so I’m not sure.

[Notthesameman]

okay, here again, it seems that this is what we got so precision highp is set at that, the code is here

Code: Select all

#if defined(_OGLES3_)
"#version 300 es \n"
"precision highp float;\n"
"precision highp int;\n"
#else
"#version 330 \n"
#endif

they asked me to post back here maybe something else is giving this error

[dankcushions]

Info in the previous post had been updated (since it was an edit, I'm not sure if subscribers would see it)

[Notthesameman]

Info in the previous post had been updated (since it was an edit, I'm not sure if subscribers would see it)

how do we know if they read it, i been on theses fourms but not to sure how they work, the last post i edited was cos i felt that the info was not good enough and i been waiting for about a month, so he might of not seen it like you said, do we need to create a new post?