Intel ARC A750 problem with Blender node connection visibility.

[Mathisdu]

While using Blender, I have noticed that the node connections do not show up while being connected. Below is a simple example:

It can be seen that both the shader nodes and the compositor nodes are connected to each other and are in effect but the connection of the nodes are not visible. I have tried this on different blender projects and it does not seem to be a file specific issue. Below are some necessary information:

>Blender version 4.3.2 installed through Steam

>Intel ARC A750 with the latest drivers 32.0.101.6647

>Steps to reproduce:

-Install Blender 4.3.2 through Steam

-Open any nodetree and try to connect various nodes

-You will see that the nodes get connected but it is not visible

I have also tried to reproduce the issue with a different computer that has a Radeon RX6600 using drivers 25.3.1 but there has been no issues so I decided to report here. A driver that didn't have this issue was 32.0.101.6325_101.6252 as far as I can remember.

[VonM_Intel]

Hi, Mathisdu.

Thank you for posting in our Community and bringing this to our attention and for providing detailed information about the issue. I understand that the node connections in Blender 4.3.2 are not visually displaying when using the Intel ARC A750 with driver version 32.0.101.6647. Since you mentioned that this issue did not occur with driver version 32.0.101.6325_101.6252 and that it does not appear on a system with a Radeon RX6600, this may be a driver-specific issue. Are you using any custom Blender settings or modifications, or is it a default installation? Does the problem persist in all projects, or only in specific node setups (e.g., complex shader graphs vs. simple ones)? If possible, could you share a short video or screenshots demonstrating the missing node connections? These questions will help narrow down the cause and determine if it's a driver issue, Blender-specific bug, or system-related problem.

Have a nice day!

Best regards,

Von M.

Intel Customer Support Technician

[Mathisdu]

Hello again! Below is a video that I hope shows the issue. To make sure that basic tweaks, such as the options in the preferences tab and add-ons, I loaded the factory settings to make sure that the problem wasn't caused by my settings and the issue still persists. The Blender installation by itself is a clean installation that I installed from Steam.

The problem persists in all projects and the complexity of the nodes do not matter, the problem affects all of them. The video below shows a simple example of it, I used both drivers mentioned before for a comparison. I hope this helps in fixing the issue.

[VonM_Intel]

Hello, Mathisdu.

Thank you for sharing the video and providing detailed information about the issue. I appreciate the effort you’ve taken to troubleshoot, including resetting to factory settings and performing a clean installation via Steam.

Since the problem persists across all projects and with different drivers, I will review the provided video carefully to analyze the behavior. I’ll need to conduct additional research on this issue and will post an update in this thread once I have more information about this matter.

Best regards,

Von M.

Intel Customer Support Technician

[VonM_Intel · Accepted solution]

Hello, Mathisdu.

Thank you for your patience. Based on my investigation, Blender version 4.4 was released yesterday. Please download and test this version to check if the issue persists. 

Best regards,

Von M.

Intel Customer Support Technician

[Mathisdu]

Hello again! After checking the new version, the issue seems to be completely fixed. I tried replicating it but there has been no issues whatsoever. Its also stated in the official Blender Bug Fixes page. Thanks!

[VonM_Intel]

Hello, Mathisdu.

Thank you for the update! I’m glad to hear that the issue has been completely resolved in the new version and that it's confirmed on the official Blender Bug Fixes page. Thank you for taking the time to share this, and hopefully, it may help other community members experiencing similar behavior. Since the thread is now solved, I will proceed to close it. Please keep in mind that this thread will no longer be monitored by Intel.

Best regards,

Von M.

Intel Customer Support Technician