- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I'm developing a cross-platform application that utilizes OpenGL (2.0). While implementing omni-directional shadowmapping, I have noticed that on my Intel Graphics HD 4000 when rendering depth cube maps, only the positive-x face contains rendered data in my FBO. The other five faces of the cube map are black (0.0 depth). From the imagery it appears all six sides are rendering, but the target is always the positive-x face. I have tested hardcoding the face to always write to negative-z, but it continues to write all data to the positive-x face.
I have tested this exact code on NVidia hardware (NVidia 660M) and each of the six faces of the depth cube map appear correct. I have debugged the application via AMD gDebugger and have found no GL/FBO errors being reported either. Out of curiousity I even created a GL3.2 context and continue to receive this error. Since I am targeting multiple platforms (Win,Linux,Mac,iOS,Android) I am trying to target GL2.0 for compatibility but am open to creating specific contexts if needed.
I am running the drivers "9.17.10.2932", with an Core i7 Notebook (Alienware 17m with NVidia 660m Optimus Tech). I'm trying very hard to keep the Intel HD 4000 card compatible with this game which is being released in the summer so any assistance on the matter would be greatly appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Chris. I wanted to let you know that one of our engineers has tested and verified the issue you're referring to, and that you can expect a fix in the future (no ETA yet). I'll let you know when a driver is released with the solution.
Thanks,
-Nic
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Chris. I wanted to let you know that one of our engineers has tested and verified the issue you're referring to, and that you can expect a fix in the future (no ETA yet). I'll let you know when a driver is released with the solution.
Thanks,
-Nic
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This issue should be resolved with the latest release driver. The download for it is here;
32-bit:https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=22610&lang=eng Download Center
64-bit: https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=22605&lang=eng Download Center
Thanks,
-Nic
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello All,
Please note that Intel® has developed a new driver version. This driver contains several fixes and new features.
You can download the latest driver at the following link:
For Windows* 7 64 Bit:
https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=22842&lang=eng&OSVersion=Windows%207%20%2864-bit%29*&DownloadType=Drivers https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=22842&lang=eng&OSVersion=Windows%207%20%2864-bit%29*&DownloadType=Drivers
For Windows* 7 32 Bit:
https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=22840&lang=eng&OSVersion=Windows%207%20%2832-bit%29*&DownloadType=Drivers https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=22840&lang=eng&OSVersion=Windows%207%20%2832-bit%29*&DownloadType=Drivers
Please, test this driver and report any issue with it so we can pass the feedback to the corresponding department.
Regards
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page