Created attachment 53964 [details] textureCube test case System Environment: -------------------------- Kernel: (drm-intel-next)9a10f401a401ca69c6537641c8fc0d6b57b5aee8 Libdrm: (master)2.4.27-3-g37ccce5e390a9d757474920f488cafa1cf89854a Xserver: (master)xorg-server-1.11.99.1-43-gb2015a2c01711646bb7ae23d684abee0cd55d4d0 Xf86_video_intel:(master)2.17.0-38-g5b1e9e15738b9001346ab6e0166f861ce308008e Bug detailed description: ------------------------- textureCube failed to link in vertex shader, error: Too many vertex shader texture samplers. the case at the attached can reproduce this issue.
I'm unable to reproduce this issue using the attached vertex shader provided on bug page. Do you have a complete test case to reproduce it? glxinfo on my system shows: OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile x86/MMX/SSE2 OpenGL version string: 2.1 Mesa 7.12-devel (git-636f2fc) OpenGL shading language version string: 1.30 libdrm version: 2.4.27
Created attachment 54735 [details] Piglit test case to verify textureCube support Attaching a piglit test case which i developed to reproduce the issue
System Environment: -------------------------- Libdrm: (master)2.4.29-3-gef20301a11afae50bfe127002913dbd0b81ddccc Mesa: (master)f1d89638c02afafbf82ef657cd6ba9965dad6738 Xserver: (master)xorg-server-1.11.99.2-16-gfcda98c48610fd507ca0b89c6006a5497d9dc1c9 Xf86_video_intel:(master)2.17.0-193-g34cfa15e522ba486d591d37f37d494e399f70354 with the latest mesa to verify, the issue can't be reproduced. (In reply to comment #2) > Created attachment 54735 [details] > Piglit test case to verify textureCube support > Attaching a piglit test case which i developed to reproduce the issue
Can we close this bug if the issue can not be reproduced?
All of bug #29522, bug #43359, and bug #43360 should be fixed by the recent addition of vertex texture support to the i965 driver. *** This bug has been marked as a duplicate of bug 29522 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.