New Issues For the 4575 Beta Drivers

[L0G1C-B0M8]

Hey Intel,

I do not know the exact place to report beta driver issues, hence why I'm using this thread. If there is a proper channel, guidance would be appreciated. I have attached an SSU info sheet on my system to help.

I have been using the 4575 beta drivers for a few days now (Running Windows 11 Home) and some results have cropped up:

• Horizon Zero Dawn (obtained via Steam) - I have seen a much improved performance of my Arc A750 when compared to the official 4502 WHQL drivers. It got to the point where CPU activity went up to 42% (which I call "chewing") and GPU activity went down to the 50%-60% range ("slogging") while simply standing still in nearly every location of the game. The beta drivers have corrected that issue and the game is almost as smooth as can be). There's still an issue of slowdown around heavy activity places like Meridian. It's noticeable but not to the point of crippling. Additional note: I let the game do a scan of my GPU and it recommended "Ultimate Quality" settings, which is the game's maximum graphics option.
• Destiny 2 (obtained via Microsoft Xbox app) - There was massive screen flickering and slowdown from the boot screen all the way to arriving at orbit upon logging in. A simple restart of the game and the issue was resolved.
• Halo Infinite (obtained via Microsoft Xbox app) - The game no longer crashes, but rendering issues are plaguing the game. I posted a thread of Halo Infinite crashing with the 4502 WHQL drivers, and at the time I was running Windows 10 with the same specs mentioned in my attached SSU. While still using Windows 10, the current beta drivers fixed the crashing of Halo Infinite and the game ran like a dream with maximum settings. I have tried lower settings but the results persist. This only occurs on Windows 11. I have attached a video obtained by the Xbox Game Bar capture to show what I mean by the rendering issues.
• The Graphics Command Center - I would set my "vividness" under the Display tab to 65. The settings would stay until the PC was shut down or restarted. I would go back to the GCC and see "vividness" was still set to 65, but the colors were flat; as if they were back at the setting of 50. The "vividness" settings were still the same, yet the color vibrancy was gone. A click on either - or + and the colors would pop back in. Also, I have HDR enabled in Windows. I do not know if the GCC doesn't play well with beta drivers, or if this is a new issue altogether. I will continue to test whether GCC is conflicting with Windows HDR and post updated results.

This is all I have for now. If any more issues arise, I will continue to post updates in this thread.

UPDATE - The GCC vividness settings issue continues to persist in SDR mode. When my PC booted back up after a shutdown lasting for thirty minutes, I watched the color vibrancy fall flat on the lock screen. I have reverted back to HDR mode.

[Jean_Intel]

Hello L0G1C-B0M8,

Thank you for posting on the Intel️® communities. We appreciate all the information you have shared regarding the issues you have encountered with our latest Beta Driver. We would be more than glad to help you with you and troubleshoot your problems.

• About the Horizon Zero game. Thanks for informing us that performance has increased, but we understand that there is still work to do in some places, such as Meridian. We would like to inform you that we are currently investigating, and the driver developer team is working to improve performance in upcoming drivers. However, we are unable to commit to an estimated time or updates regarding this matter.
• For the Destiny 2 problem, we would like to confirm if you have faced the problem again or if it has only occurred one more time.
• Currently, Intel is working on a solution for some graphical corruption issues on the Halo Infinite game. Unfortunately, we can't commit to an ETA regarding this problem.
• For the IGCC problem, we would like to confirm if you have any other graphics control center in your system. Sometimes the Intel® Graphics Command Center changes are returned to normal due to another application pre-installed on the system. For example, the Dell PremierColor or Samsung Setting application creates conflicts with the Intel® Graphics Command Center.

Also, since you reported multiple issues and there are differences between each other, we would like to recommend you open a thread per issue. This would help us maintain the threads organized and avoid confusion caused by troubleshooting multiple problems at once.

Best regards, 

Jean O. 

Intel Customer Support Technician

[L0G1C-B0M8]

Greetings Jean,

I appreciate your response. I want to say thank you to you and your team for due diligence to improve the Arc graphics cards. I understand you cannot give an exact timeframe until you're sure, but as they say - "Rome wasn't built in a day". But to answer your questions about these issues:

• Not much more to say about Horizon or Halo Infinite but thank you for your team's efforts to continue improving the driver performance.
• For Destiny 2, no further issues have popped up since the initial start. Destiny 2 is good to go.
• As for IGCC, I am not running any other control panels whatsoever. My system is clear of everything except for IGCC. To be certain, I uninstalled the beta drivers and used Display Driver Uninstaller. I then installed the 4502 WHQL drivers. With the official drivers, the IGCC worked just fine every time. So I am certain it's the current beta drivers, which I have reinstalled.

Noted on one thread per issue. I admit since it was more of a report concerning the beta drivers, I felt it would be more beneficial to bring them altogether. Maybe there might be a thread dedicated to beta driver feedback down the road. Who knows.

Once again, thank you for the response and informing me on what's being done. Feel free to lock this thread if you wish.

[Jean_Intel · Accepted solution]

Hello L0G1C-B0M8,

Thank you for the information and the feedback you provided.

Based on your comment about locking the thread, we assume that you would prefer to close it. Therefore, we will proceed with closing the thread. If you require further assistance, please post a new question as this thread will no longer be monitored.

Best regards,

Jean O.

Intel Customer Support Technician