JDK-8126440 : ES2 pipeline silently fails to load large textures when rendering large images
- Type: Bug
- Component: javafx
- Sub-Component: graphics
- Affected Version: 7u6
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2012-06-19
- Updated: 2015-06-17
- Resolved: 2012-10-16
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 8 |
|---|
8Fixed  |
Related Reports
|
Blocks :
|
|
|
Relates :
|
Description
When running on a Mac with Intel HD, loading an 8K texture (which is reported to be supported) causes serious rendering artifacts. See RT-21998 for a test program. Run it with "-Dprism.maxTextureSize=0" to bypass the clamping that was added to fix that bug. We likely have one or more of the following problems: 1) the texture size really isn't supported. This seems likely, given that Intel HD on Windows with D3D only reports 4K, it seems surprising that it reports 8K on Mac via OpenGL). Also, my NVIDIA card on Windows reports 8K, but the same card also on Windows reports 16K via OpenGL. 2) A failed texture load does not correctly result in a null texture; the resulting texture object just fails to render correctly.
Comments
|