GLSL compile failed (’GL_3DL_array_objects’ : extension is disabled or not available)

[Yuya_Fukazawa_bn7]

#version 310 es
precision highp float;
layout(location = 0) out vec4 Output;
void main()
{
	const float arr[3] = float[3]
	(
		0.0, 0.5, 1.0
	);
	Output = vec4( arr[0], arr[1], arr[2], 1.0 );
}

The above fragment shader compiles successfully with Intel® Graphics Driver 31.0.101.1692, but fails to compile with Intel® Graphics Driver 31.0.101.5333.

glGetShaderInfoLog returns "ERROR: 2668:38048.581: ’GL_3DL_array_objects’ : extension is disabled or not available".

I think this compile error is a bug in the driver.

I have attached some files.

・Report/GLSLCompilerTest/bin/GLSLCompilerTest.exe is the executable file that compiles the above fragment shader.

・Report/CompileSucceeded_30.0.101.1692.png is an image of a successful compilation with Intel® Graphics Driver 30.0.101.1692.

・Report/CompileFailed_30.0.101.5333.png is an image of failed compilation with Intel® Graphics Driver 31.0.101.5333.

[그래요ITech]

Hello there Yuya_Fukazawa_bn7...

The issue you're encountering with the fragment shader not compiling on Intel® Graphics Driver 31.0.101.5333, despite being successful on an earlier driver version, does suggest a potential regression or bug in the newer driver. The error message indicating that the 'GL_3DL_array_objects' extension is disabled or not available is particularly telling, as this should not typically occur if the extension was previously supported and no changes were made to the shader code.

Here's what you can do to address this issue:

1.Driver Rollback: As a temporary workaround, consider rolling back to the driver version 31.0.101.1692, which you've confirmed works correctly with your shader.

2.Check for Updates: Regularly check for driver updates that may resolve this issue. Sometimes, driver updates are released specifically to fix such bugs.

Remember to include all relevant files and detailed descriptions of the issue when reporting the bug to ensure that Intel can replicate and address the problem effectively.

Thanks.

Max

[Yuya_Fukazawa_bn7]

Thanks for your reply.

Currently, in our product, we have customers take the workaround (driver rollback).

I hope intel will recognize and correct this issue.

What should I do for that?

[NormanS_Intel]

Hello Yuya_Fukazawa_bn7,

I appreciate your participation in our community. It has come to our attention that you are encountering difficulties during the compilation process. I kindly suggest that you utilize the most recent graphics driver, version 31.0.101.5382, to see if it resolves the issue. Your feedback on this matter would be highly valuable, and we look forward to hearing about your results.

Best regards,

Norman S.

Intel Customer Support Engineer

[Yuya_Fukazawa_bn7]

Hello NormanS_Intel,

Thanks for your reply.

I tried with driver version 30.0.101.5382 and the issue was not resolved.
glGetShaderInfoLog returns "ERROR: 42694:37616.558: ’GL_3DL_array_objects’ : extension is disabled or not available".

I have attached some files.
・Report_31.0.101.5382/CompileFailed_30.0.101.5382.png is an image of failed compilation with Intel® Graphics Driver 31.0.101.5382.
・Report_31.0.101.5382/SSUScanInfo.txt is result of System Support Utility scan. 

[NormanS_Intel]

Hello Yuya_Fukazawa_bn7,

Thank you for your prompt reply and the details you have shared. Please be assured that we will conduct a thorough review of the situation and provide an update as soon as it becomes available.

We appreciate your patience and understanding in this matter.

Best regards,

Norman S.

Intel Customer Support Engineer

[NormanS_Intel]

Hello Yuya_Fukazawa_bn7,

We are attempting to replicate the issue you reported in our simulation room, but we are unable to do so. Therefore, we require your assistance to better replicate it. Can you please provide us with step-by-step instructions on how we can reproduce the issue? Alternatively, you may share a screen recording so we can investigate it further.

Thank you for your understanding, and I look forward to your response.

Best regards,
Norman S.
Intel Customer Support Engineer

[Yuya_Fukazawa_bn7]

Hello NormanS_Intel,

I think you can reproduce the issue by running the Report/GLSLCompilerTest/bin/GLSLCompilerTest.exe in the attachment to my first post.

It require Visual C++ 2015-2022 Redistributable (x64).
You can download latest version redistributable from https://aka.ms/vs/17/release/vc_redist.x64.exe

To load shader source file (Report/GLSLCompilerTest/bin/shader.frag), current directory must be the directory where GLSLCompilerTest.exe exists .

1. Start Command Prompt (cmd.exe).

2. Change current directory to the directory where GLSLCompilerTest.exe exists.

3. Run GLSLCompilerTest.exe.

If you want to know what GLSLCompilerTest.exe does, you can see source code (Report/GLSLCompilerTest/GLSLCompilerTest.cpp).

[NormanS_Intel]

Hello Yuya_Fukazawa_bn7,

I appreciate your guidance. We will proceed with the steps you have outlined and inform you of the outcomes following the completion of our simulation.

Your patience is greatly valued. Thank you.

Best regards,

Norman S.

Intel Customer Support Engineer

[filteronme]

Hi Norman S, 

Thanks for looking into the issue. Is there any workaround we can do in the meantime or can you provide an ETA? 

This is causing crashes on our clients computers that use our app and is a serious issue for our company. 

Best

Eddy

[NormanS_Intel]

Hi filteronme,

Could you please confirm if your account is connected to the user Yuya_Fukazawa_bn7 and whether you are experiencing a similar issue? If your situation is different, I kindly recommend starting a new discussion thread. This will allow us to provide you with dedicated assistance and address your specific concerns more effectively.

Hi Yuya_Fukazawa_bn7,

I have reached out to you via private message to share findings from our recent investigation. Your cooperation would be greatly appreciated to help us determine the exact cause of the issue.

Best regards,

Norman S.

Intel Customer Support Engineer

[NormanS_Intel]

Hello Yuya_Fukazawa_bn7,

We have conducted an investigation and would like to inform you that since the product in question is an OEM product, we suggest checking with the system manufacturer to see if they can assist with the errors you are experiencing. Additionally, have you tried updating to a previous version of the driver to determine whether the issue is also happening to other versions provided by the OEM? For instance, the version prior to 31.0.101.1692.

Furthermore, could you please provide us with the installer of driver version 31.0.101.1692 and the link where you downloaded it? I have posted this response in the community thread once again, as I previously sent you a private message, so we can continue the conversation in this thread. I'll wait for your response so we can continue the investigation. 

Best regards,

Norman S.

Intel Customer Support Engineer

[Yuya_Fukazawa_bn7]

Hello NormanS_Intel,

> Additionally, have you tried updating to a previous version of the driver to determine whether the issue is also happening to other versions provided by the OEM? For instance, the version prior to 31.0.101.1692.

I tried driver version 31.0.101.5081 provided by Fujitu (download from https://azby.fmworld.net/app/customer/driversearch/pc/drvdownload?mode=1&driverNumber=E1032081), but failed to compile.

glGetShaderInfoLog returns "ERROR: 838:41264.676: 'GL_3DL_array_objects' : extension is disabled or not available.

I have attached some files.
・Report_31.0.101.5081_Fujitsu/CompileFailed_30.0.101.5081(Fujitsu).png is an image of failed compilation with driver version 30.0.101.5081 provided by Fujitu.
・Report_31.0.101.5081_Fujitsu/SSUScanInfo.txt is result of System Support Utility scan after install driver version 31.0.101.5081 provided by Fujitu.

I could not find driver version prior to 31.0.101.1692 on Fujitu web site.

> Furthermore, could you please provide us with the installer of driver version 31.0.101.1692 and the link where you downloaded it?

Sorry, I don't have installer of Driver version 31.0.101.1692 provided by Fujitsu, and couldn't find download page on Fujitu website.

Driver version 31.0.101.1692 which I use is pre-installed driver.

I have a backup for this.

[NormanS_Intel]

Hello Yuya_Fukazawa_bn7,

I appreciate the update and the details you've shared. Could you kindly confirm whether this issue has been communicated to the Fujitsu? I look forward to hearing from you.

Best regards,

Norman S.

Intel Customer Support Engineer

[NormanS_Intel]

Hello Yuya_Fukazawa_bn7,

I wanted to check if you had the chance to review the questions I posted. Please let me know at your earliest convenience so that we can determine the best course of action to resolve this matter. 

Best regards,

Norman S.

Intel Customer Support Engineer

[Yuya_Fukazawa_bn7]

Hello NormanS_Intel,

Sorry, I don’t know to which contact I should report this problem, so I have not communicated to the Fujitsu.

Do you consider this problem to be Fujitsu's fault?

But

・You said you have successfully replicated this problem and encountered the same message.

・This problem also occurs with Dell Technologies PC with Iris Xe graphics.

So I think this problem is due to Intel generic version of graphics driver

(and this problem remains with OEM driver based on generic driver).

Best regards,

[NormanS_Intel]

Hello Yuya_Fukazawa_bn7,

Your input is greatly appreciated. Rest assured, the intention is not to suggest that Fujitsu is at fault. Rather, we are keen to confirm whether the issue has been communicated to the computer manufacturer for their awareness and further action.

We have indeed replicated the issue and are currently doing an investigation. Following your feedback, we will diligently proceed with our investigation and ensure to keep you informed within this discussion thread as soon as possible.

Best regards,

Norman S.

Intel Customer Support Engineer