Closed yetyman closed 1 year ago
I have since learned that the Iris Xe chip is failing to support the Mat4[] parameters of my shader. It compiles, but the access violation is thrown inside the intel driver during the linkProgram call. if i replace the mat4[] uniform with individual mat4 uniforms the access violation no longer occurs. Strange stuff.
Version
3.3.2
Platform
Windows x64
JDK
OpenJDK Corretto-17.0.5.8.1
Module
OpenGL
Bug description
Hello,
I would like to bring this to your attention on the off chance you might see something that I do not as I am fairly new to graphics programming and I do not understand why this basic shader program would have any issue on an Intel Iris xe. I am using a library that wraps LWJGL for JavaFX called OpenGLFX, though I doubt they are related to the cause of this issue.
When I set NVidia Control Panel to give my application the embedded graphics chip(Intel Iris Xe) on my laptop instead of its bigger embedded GPU(RTX 3050 laptop) I start getting issues. I recognize that this is a hardware issue however nothing I look up indicates any lack of support on the Intel Iris Xe and glView is indicating full support for everything.
for reference here's the simplified set of code in init() just after OpenGLFX creates the glContext that leads the an Access_Violation_Exception everytime with the Intel Iris Xe but runs well with the 3050. Its a pretty basic shader program, I'm not aware of anything here being particularly advanced.
The Access Violation occurs within
org.lwjgl.opengl.GL20C.glLinkProgram(I)V+0
as you can see from the attached dumpif it is relevant, here are my shaders though I don't think I'm doing anything interesting here.
Stacktrace or crash log output