Why does wine write ARBfp2.0 into opengl shaders that originated from DirectX2.0? The shaders I'm seeing all use commands currently available to us [ no branches or anything like that ], but are marked v2.0. As a result the ARB extension fails on them every single time (invalid header - ARBfp2.0), while it could work.
On 12/04/06, Ivan Gyurdiev ivg2@cornell.edu wrote:
Why does wine write ARBfp2.0 into opengl shaders that originated from DirectX2.0? The shaders I'm seeing all use commands currently available to us [ no branches or anything like that ], but are marked v2.0. As a result the ARB extension fails on them every single time (invalid header - ARBfp2.0), while it could work.
No idea, but it's wrong. It should just write ARBfp1.0.
I am 'Dumber' in this area but when it writes ARBfp2.0 into the shaders, it should be printing a FIXME.
check in this function WineD3DPixelShaderImpl_GenerateProgramArbHW from line 1005 to 1039, in pixelelshader.c, in wined3d
here its checking for pixeelshader version for pixelshader versiion 20 it writes the above string.
This is my analysis by looking at the code
On 4/12/06, H. Verbeet hverbeet@gmail.com wrote:
On 12/04/06, Ivan Gyurdiev ivg2@cornell.edu wrote:
Why does wine write ARBfp2.0 into opengl shaders that originated from DirectX2.0? The shaders I'm seeing all use commands currently available to us [ no branches or anything like that ], but are marked v2.0. As a result the ARB extension fails on them every single time (invalid header - ARBfp2.0), while it could work.
No idea, but it's wrong. It should just write ARBfp1.0.
-
H. Verbeet -
Ivan Gyurdiev -
Vijay Kiran Kamuju