Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
Announcements
FPGA community forums and blogs have moved to the Altera Community. Existing Intel Community members can sign in with their current credentials.
22789 Discussions

OpenGL 3D texture is not loaded correctly from pixel buffer

Marek_Fort
Beginner
2,498 Views

GPU SKU: Intel HD Graphics 4400, Intel HD Graphics 4600
Graphics Driver Version: 10.18.10.3995
Operating System: Windows 7 x64
API: OpenGL core profile.
Occurs on non-Intel GPUs?: No

Steps to Reproduce:
-------------------------------
1. Have PBO with 256kB of unique data
2. Call: glTexSubImage3D(GL_TEXTURE_3D, 0,   0,0,0,  64,64,64, GL_RED, GL_UNSIGNED_BYTE, NULL);
3. Call  glGetTexImage to read it back
4. Compare with original PBO


Expected Results:

- Identical data

 

Actual Results:

- only first 4096 bytes are correct. Then exact copy of the first 4096 bytes are there instead.

 

Additional Information:

Data are loaded incorrectly,verified by both shader and glGetTexImage.

Loading data without PBO works well.

I am not sure why 4096. It could be either a page size or first slice (64*64*1 = 4096).

NVidia and AMD works well with identical code.

 

 

0 Kudos
6 Replies
Michael_C_Intel2
Employee
2,498 Views

Hi Marek,

3995 is a rather old driver version. Have you tried the latest driver 4264?

https://downloadcenter.intel.com/product/81496/Intel-HD-Graphics-4600-for-4th-Generation-Intel-Core-Processors

-Michael

0 Kudos
Marek_Fort
Beginner
2,498 Views

Hi,

tested with 15.36.24.64.4264.

I get the same wrong results.

 

--

Marek

 

0 Kudos
Michael_C_Intel2
Employee
2,498 Views

Hi Marek,

Thanks for the update. I have contacted the OpenGL driver development team and have an internal ticket for the issues. I will update you when we learn something.

-Michael

0 Kudos
Lars_B_
Beginner
2,498 Views

Hi,

any news on this? Still occurring with 10.18.14.4294.

This is breaking our renderer...

Regards,

Lars

 

0 Kudos
Michael_C_Intel2
Employee
2,498 Views

Hi Lars and Marek,

We confirmed it is a driver issue and the root cause. Our driver team is working on a fix, I do not have an ETA of when we will have a driver with the fix yet. Still need to know the complexity of the fix. I hope to know more soon.

-Michael

0 Kudos
Michael_C_Intel2
Employee
2,498 Views

Hi,

We have completed the fix and expect it to be included in the next driver release.

-Michael

0 Kudos
Reply