Iris Xe Bugs and Problems Direct3D .NET WPF, LineTopology, Double Precision, MSAA

[CaptBridgeport]

Hello

I would like to remind Intel we and thousands of our 3rd party customers, and hundreds of thousands of 4th party customers are still waiting (2+ years now) for fixes related to Intel Iris Xe problems bugs shortcomings...

1) .NET WPF component Direct3D rendering with MSAA > 1 causes the app to crash. 

2) Line Topology with MSAA > 1 does not honor anti aliasing and the image looks corrupted.

3) The driver does not support double precision float variables within shaders which causes rendering corruption in cases where double precision is necessary.  

Below are example rendering with Iris Xe latest driver 5/31/23 and MS Basic Driver.  As one can see, the Iris Xe rendering is not acceptable where as the MS Basic rendering is high quality as expected.  

Iris Xe line topology not anti aliased as should beSimilar rendering with MS Basic graphics driver

Given the quantity of Iris Xe problems found on this site (which is likely  .01% of the issues actually happening), it's evident there is a critical-run-away bug list that seems impossible for Intel to resolve. Or can Intel provide any assurance that above Iris Xe problems will be addressed in the next 6 months so rendering is similar to AMD, Nvidia, MS?   We currently have to inspect the system for your Intel driver and revert Direct3D rendering to MSAA=1 to avoid crashes at the expense of a poor quality rendering which is causing issue with thousands of clients. 

[Andres_Intel]

Hello CaptBridgeport,

Thank you for posting on the Intel®️ communities. I am sorry to hear that you are having rendering issues with your Intel® Iris® Xe Graphics, I will be happy to help you.  

This problem has been addressed in driver 31.0.101.4032, please answer the following questions to provide with the correct driver version based on your system hardware:

• Download, run, save and attach the report for the following tool Intel® System Support Utility for Windows (SSU), you can find the steps on the link How to get the Intel® System Support Utility Logs on Windows.  

Regards,  

Andres P. 

Intel Customer Support Technician

[Andres_Intel]

Hello CaptBridgeport,

Were you able to check the previous post?

Let us know if you still need assistance.

Best regards,

Andres P.

Intel Customer Support Technician

[CaptBridgeport]

Hello

I have tested latest driver 4502 dated 6/21/23 for the LineTopology  anti-aliasing bug and it still exists.  And Intel is not answering our question when will this be fixed.  It is a known issue by Intel so please understand everyone reading this thread knows Intel knows about the issue.  Seems Intel is likely hard coding their logic to MSAA = 1 to avoid the previous crash instead of correctly supporting MSAA > 1 for LineTopology rendering.  Again, my example images above show similar results for latest driver 4502.  Please reiterate to the head of the Driver Development Team that hard coding MSAA=1 for line topology rendering is not acceptable (referring to above images) and please provide a future version number this fix is expected.  

[Andres_Intel]

Hello CaptBridgeport,

Thank you for your response, it has been really helpful.

In order to speed up the investigation, please answer the following questions:

• To know you hardware system, driver and firmware versions download, run, save and attach the report for the following tool Intel® System Support Utility for Windows (SSU), you can find the steps on the link How to get the Intel® System Support Utility Logs on Windows.  
• What is the name of the software that your are using for rendering?

Regards,  

Andres P. 

Intel Customer Support Technician 

[CaptBridgeport]

Hello,

Sorry, I've been reporting issues about Iris xe for over 2 years.  Please find my older submissions. Again, Intel knows about the issue.  Please realize the issue is 100% device independent.  A faulty driver that is tied to the CPU is not likely related to any other component of the system.  Any 11th gen and later CPU and the Iris Xe Driver causes the issue of line topology not supporting MSAA > 1.  Intel is so frustratingly incompetent at every level.  It sure be would be nice if an actually engineer could respond.  Intel is going on 3 years now releasing a driver that should never have been released 3 years ago.  Please Please Please Please Please Please Please produce a driver that behaves as all other drivers on the planet behave, as Microsoft fully expects the driver to behave, else systems crash or look defective and everyone gets blamed from MS to software makers, because of Intel.  Doesn't Intel feel any regret or obligation to resolve? 

[Andres_Intel]

Hello CaptBridgeport,

Thank you for your response.

We completely understand your frustration, we also understand that you need this issue solved as soon as possible, we are aware that you have shared the requested files before, but we also need the most updated ones to speed up the investigation. In this case, please provide us with the information requested below as it is going to be really useful to find a solution:

• Attach the report for the following tool Intel® System Support Utility for Windows (SSU).
• What is the name of the software that your are using for rendering?

Regards,  

Andres P. 

Intel Customer Support Technician 

[Andres_Intel]

Hello CaptBridgeport,

Were you able to check the previous post?

Let us know if you still need assistance.

Best regards,

Andres P.

Intel Customer Support Technician

[Andres_Intel]

Hello CaptBridgeport,

We have not heard back from you, so we will close this thread. If you need any additional information, please submit a new question as this thread will no longer be monitored. 

Best regards,

Andres P.

Intel Customer Support Technician