Shader compilation freeze Blender on Intel Arc770 #111556

New Issue

Closed

opened 2023-08-26 14:35:57 +02:00 by Andrew · 27 comments

Andrew commented

2023-08-26 14:35:57 +02:00

System Information
Operating system: Windows 10
Graphics card: Intel Arc770 16Gb (Resizable Bar enabled)

Blender Version
3.6.0
Date: 2023-06-27 08:08
Hash: c7fc78b81e
Branch: blender-v3.6-release

Intel driver version
31.0.101.4665
Released 11.08.2023 (latest on moment of this post)

Short description of error
All modes of viewport on new scene (default, for example) works fine: solid, material preview, display render. But, if I open my scene, works only 1 and 3 option. Building a shaders freezes Blender. It's around 800+ materials on scene, and GeForce cards works fine with that. The video card works at full power, with enabled Resizable Bar function. Cycles render (oneAPI) also works fine, but i can't switch the viewport on material preview. Blender freezes when shaders start compile.

**System Information** Operating system: Windows 10 Graphics card: Intel Arc770 16Gb (Resizable Bar enabled) **Blender Version** 3.6.0 Date: 2023-06-27 08:08 Hash: c7fc78b81ecb Branch: blender-v3.6-release **Intel driver version** 31.0.101.4665 Released 11.08.2023 (latest on moment of this post) **Short description of error** All modes of viewport on new scene (default, for example) works fine: solid, material preview, display render. But, if I open my scene, works only 1 and 3 option. Building a shaders freezes Blender. It's around 800+ materials on scene, and GeForce cards works fine with that. The video card works at full power, with enabled Resizable Bar function. Cycles render (oneAPI) also works fine, but i can't switch the viewport on material preview. Blender freezes when shaders start compile.

Andrew added this to the 3.6 LTS milestone 2023-08-26 14:35:57 +02:00

Andrew added the

labels 2023-08-26 14:35:58 +02:00

Iliya Katushenock added the

EEVEE & Viewport

label 2023-08-27 00:13:40 +02:00

Iliya Katushenock removed this from the 3.6 LTS milestone 2023-08-27 00:13:42 +02:00

Alaska commented

2023-08-27 12:05:36 +02:00

Member

Can you please share the .blend file you're having issues with so we can investigate it?

Can you please share the .blend file you're having issues with so we can investigate it?

Alaska added

Needs Information from User

and removed

labels 2023-08-27 12:05:55 +02:00

Andrew commented

2023-08-29 18:03:29 +02:00

Author

Can you please share the .blend file you're having issues with so we can investigate it?

Only in private mode, because this is working file, not for public release.

> Can you please share the .blend file you're having issues with so we can investigate it? Only in private mode, because this is working file, not for public release.

Iliya Katushenock commented

2023-08-29 18:06:39 +02:00

Member

@Raid9000 We need some kind of simple blend. file just to reproduce the bug.

@Raid9000 We need some kind of simple blend. file just to reproduce the bug.

Andrew commented

2023-08-29 22:05:57 +02:00

Author

@Raid9000 We need some kind of simple blend. file just to reproduce the bug.

Okay, I just ask can I give a non-public link or not.

> @Raid9000 We need some kind of simple blend. file just to reproduce the bug. Okay, I just ask can I give a non-public link or not.

Alaska commented

2023-08-30 06:58:26 +02:00

Member

@Raid9000 , you can provide a private link to people if need be. However, it typically interfers with the triaging and bug fixing process.
It's preferred if you share the file publicly, or simplify the file to only what's necessary to reproduce the bug then share it publicly.

Here's an example of how you might simplify the file:

Freezes seem to occur during shader compilation. It's probably an issue with a shader. So...
- Remove every object from the scene then add a simple object with a material assigned to each one. Does the issue continue?
  - If yes, then it's a shader or set of shaders causing issues. So start removing objects and their matieral/shaders until you find the one, or multiple, that are causing issues.
  - If no, then it's either an issue with an object, or an object shader pair. So test groups of objects until you find the group that has issues. Then start removing objects one by one from that group until you find the object or object shader pair that's causing issues.
  - It should be noted it could be a more complex issue that only occurs if you have X materials with Y objects with Z number of vertices in your scene. In which case you won't be able to track the issue down to a single object or material.
Once you've simplified the file, upload it here.

For reference, the triaging and bug fixing process typically goes like this:

A user makes a bug report with the relevant information to reproduce the bug.
A member from the triaging team (typically volunteers, sometimes developers) will test to see if the bug exists and marks the report with various tags to let relevant people know this needs investigating.
A developer comes along and fixes the issue, or figures out exactly why it's happening (E.G. A driver bug that the Blender developers can't fix).

I am a volunteer, and I'm helping out with the triaging team. I have an Intel Arc A750. If you give me the file, I can investigate it, confirm whether or not the issue happens on other Intel Arc GPUs, and potentially simplify the file to help a developer that wants to work on fixing it. And if the file can be highly simplified, I will share the simplified file here.

But since I'm not an experienced developer and do not have much knowledge in the EEVEE shader compilation code, I can not fix the issue. So after doing my tests, confirming whether or not he issue occurs, a developer with a Intel Arc GPU will come along and investigate the issue and then proceed to fix it or identify the exact cause.

It's up to you on how you want to handle this.

Try simplifying the file yourself so it can be shared publicly?
Share the file privately with me so I can confirm whether or not the issue occurs on my Intel Arc A750 and I could potentially simplify it? If I can't simply it, then you may need to share the file with other people?
Wait until a developer with and Intel Arc GPU comes along and share it privately with them?

@Raid9000 , you can provide a private link to people if need be. However, it typically interfers with the triaging and bug fixing process. It's preferred if you share the file publicly, or simplify the file to only what's necessary to reproduce the bug then share it publicly. Here's an example of how you might simplify the file: - Freezes seem to occur during shader compilation. It's probably an issue with a shader. So... - Remove every object from the scene then add a simple object with a material assigned to each one. Does the issue continue? - If yes, then it's a shader or set of shaders causing issues. So start removing objects and their matieral/shaders until you find the one, or multiple, that are causing issues. - If no, then it's either an issue with an object, or an object shader pair. So test groups of objects until you find the group that has issues. Then start removing objects one by one from that group until you find the object or object shader pair that's causing issues. - It should be noted it could be a more complex issue that only occurs if you have X materials with Y objects with Z number of vertices in your scene. In which case you won't be able to track the issue down to a single object or material. - Once you've simplified the file, upload it here. --- For reference, the triaging and bug fixing process typically goes like this: 1. A user makes a bug report with the relevant information to reproduce the bug. 2. A member from the triaging team (typically volunteers, sometimes developers) will test to see if the bug exists and marks the report with various tags to let relevant people know this needs investigating. 3. A developer comes along and fixes the issue, or figures out exactly why it's happening (E.G. A driver bug that the Blender developers can't fix). I am a volunteer, and I'm helping out with the triaging team. I have an Intel Arc A750. If you give me the file, I can investigate it, confirm whether or not the issue happens on other Intel Arc GPUs, and potentially simplify the file to help a developer that wants to work on fixing it. And if the file can be highly simplified, I will share the simplified file here. But since I'm not an experienced developer and do not have much knowledge in the EEVEE shader compilation code, I can not fix the issue. So after doing my tests, confirming whether or not he issue occurs, a developer with a Intel Arc GPU will come along and investigate the issue and then proceed to fix it or identify the exact cause. --- It's up to you on how you want to handle this. - Try simplifying the file yourself so it can be shared publicly? - Share the file privately with me so I can confirm whether or not the issue occurs on my Intel Arc A750 and I could potentially simplify it? If I can't simply it, then you may need to share the file with other people? - Wait until a developer with and Intel Arc GPU comes along and share it privately with them?

Andrew commented

2023-08-31 18:46:34 +02:00

Author

@Raid9000 , you can provide a private link to people if need be. However, it typically interfers with the triaging and bug fixing process.

Try simplifying the file yourself so it can be shared publicly?

Not shure that simplifying is an option. This it an experimental line of videocards, so problems was expected. Scene itself is also experimental, I was try Blender as a level editor. So following conclusion about:

Share the file privately with me so I can confirm whether or not the issue occurs on my Intel Arc A750 and I could potentially simplify it? If I can't simply it, then you may need to share the file with other people?

This option definently. Just because I have any clue what's can go wrong: if I delete whole meshes - no problems with shaders to see. It's can about scale of scene, or just in "broken" shader that was imported with objects.

Where I can send link?

> @Raid9000 , you can provide a private link to people if need be. However, it typically interfers with the triaging and bug fixing process. > - Try simplifying the file yourself so it can be shared publicly? Not shure that simplifying is an option. This it an experimental line of videocards, so problems was expected. Scene itself is also experimental, I was try Blender as a level editor. So following conclusion about: > - Share the file privately with me so I can confirm whether or not the issue occurs on my Intel Arc A750 and I could potentially simplify it? If I can't simply it, then you may need to share the file with other people? This option definently. Just because I have any clue what's can go wrong: if I delete whole meshes - no problems with shaders to see. It's can about scale of scene, or just in "broken" shader that was imported with objects. Where I can send link?

Andrew commented

2023-08-31 19:00:22 +02:00

Author

Upd:

I just switched off and on back a visibility of collections in some sequence, so shaders built now (problem technically solved by itself). Strange.

Blender versions 3.6.2 e53e55951e
Windows 10 - update 19045.2965
Intel Software Component - 1.41.2021.121
Intel Arc driver - 31.0.101.4665

Also bug from this topic.

Upd: I just switched off and on back a visibility of collections in some sequence, so shaders built now (problem technically solved by itself). Strange. Blender versions 3.6.2 e53e55951e Windows 10 - update 19045.2965 Intel Software Component - 1.41.2021.121 Intel Arc driver - 31.0.101.4665 Also bug from [this](https://projects.blender.org/blender/blender/issues/111671) topic.

577 KiB

Alaska commented

2023-09-01 00:09:59 +02:00

Member

I just switched off and on back a visibility of collections in some sequence, so shaders built now (problem technically solved by itself). Strange.

So is the issue resolved? Or is this just a temporary work around?

Where I can send link?

You can send me a link over here (After logging in with your Blender ID, there should be a message button on the upper right portion of the page): https://devtalk.blender.org/u/alaska/summary

Sometimes new/inactive users are unable to send private messages to people. If that's the case for you, you can share your devtalk profile page here and I'll send you a message.

The other option is with Blender chat. You should be able to find me under the same name (Alaska) in the link below. https://blender.chat/channel/render-cycles-module

Just click on my name and a little "bubble" will pop up with an option to direct message me.

> I just switched off and on back a visibility of collections in some sequence, so shaders built now (problem technically solved by itself). Strange. So is the issue resolved? Or is this just a temporary work around? > Where I can send link? You can send me a link over here (After logging in with your Blender ID, there should be a message button on the upper right portion of the page): https://devtalk.blender.org/u/alaska/summary Sometimes new/inactive users are unable to send private messages to people. If that's the case for you, you can share your devtalk profile page here and I'll send you a message. --- The other option is with Blender chat. You should be able to find me under the same name (Alaska) in the link below. https://blender.chat/channel/render-cycles-module Just click on my name and a little "bubble" will pop up with an option to direct message me.

Andrew commented

2023-09-01 18:03:41 +02:00

Author

You can send me a link over here (After logging in with your Blender ID, there should be a message button on the upper right portion of the page):

I recieve PM from bot, but can't create one.

The other option is with Blender chat. You should be able to find me under the same name (Alaska) in the link below. https://blender.chat/channel/render-cycles-module

Just click on my name and a little "bubble" will pop up with an option to direct message me.

Chat falls into endless load.

>You can send me a link over here (After logging in with your Blender ID, there should be a message button on the upper right portion of the page): I recieve PM from bot, but can't create one. > The other option is with Blender chat. You should be able to find me under the same name (Alaska) in the link below. https://blender.chat/channel/render-cycles-module > > Just click on my name and a little "bubble" will pop up with an option to direct message me. > Chat falls into endless load.

Alaska commented

2023-09-02 01:45:43 +02:00

Member

You can send me a link over here (After logging in with your Blender ID, there should be a message button on the upper right portion of the page):

I recieve PM from bot, but can't create one.

Can you send me your profile on devtalk and I'll send you a private message and you should be able to respond to it.

> >You can send me a link over here (After logging in with your Blender ID, there should be a message button on the upper right portion of the page): > > I recieve PM from bot, but can't create one. Can you send me your profile on devtalk and I'll send you a private message and you should be able to respond to it.

Pratik Borhade commented

2023-10-23 08:58:54 +02:00

Member

Any updates here?

Any updates here?

Andrew referenced this issue

2023-11-28 18:32:02 +01:00

Blender 4.0 crashes on Intel Arc A770 #115396

Pratik Borhade commented

2023-12-29 07:30:21 +01:00

Member

@Raid9000 @Alaska ? Otherwise we can close the report.

@Raid9000 @Alaska ? Otherwise we can close the report.

Alaska commented

2023-12-30 00:29:25 +01:00

Member

Sorry, I haven't received any messages. So we'll need to wait for @Raid9000

Sorry, I haven't received any messages. So we'll need to wait for @Raid9000

Andrew commented

2023-12-30 07:27:10 +01:00

Author

Mostly crash can be solved if I uncheck "Load UI" when open file that crashes. Because default viewport shading is a "Solid", when I switch to "Material Preview" all shaders builds at scratch, and on this stage I not see crashes yet. So I can conclude, that problem In shader cash probably, In shaders that was built on NVIDIA and saves into file in the NVIDIA-specified form, that can't be readed by Arc.

Mostly crash can be solved if I uncheck "Load UI" when open file that crashes. Because default viewport shading is a "Solid", when I switch to "Material Preview" all shaders builds at scratch, and on this stage I not see crashes yet. So I can conclude, that problem In shader cash probably, In shaders that was built on NVIDIA and saves into file in the NVIDIA-specified form, that can't be readed by Arc.

Alaska commented

2023-12-30 10:47:35 +01:00

Member

Compiled shaders are saved to the shader cache file managed by the GPU driver. They are not saved to the .blend file.

So the .blend file working fine when "load UI" is unchecked suggests there's something wrong with your UI setup in the file, potentially the UI combined with some Intel Arc feature.s Are you willing to share the .blend file with us?

Previously you said you wanted to share the file privately. Please let me know how you would like to share the file privately if you would still like to keep it private. E.G. Send me a private link in blender chat. Or I can contact you privately on devtalk or blender chat and send you a link to upload your file or something like that.

Compiled shaders are saved to the shader cache file managed by the GPU driver. They are not saved to the .blend file. So the .blend file working fine when "load UI" is unchecked suggests there's something wrong with your UI setup in the file, potentially the UI combined with some Intel Arc feature.s Are you willing to share the .blend file with us? Previously you said you wanted to share the file privately. Please let me know how you would like to share the file privately if you would still like to keep it private. E.G. Send me a private link in blender chat. Or I can contact you privately on devtalk or blender chat and send you a link to upload your file or something like that.

Andrew commented

2023-12-30 23:04:38 +01:00

Author

Compiled shaders are saved to the shader cache file managed by the GPU driver. They are not saved to the .blend file.

So the .blend file working fine when "load UI" is unchecked suggests there's something wrong with your UI setup in the file, potentially the UI combined with some Intel Arc feature.s Are you willing to share the .blend file with us?

Previously you said you wanted to share the file privately. Please let me know how you would like to share the file privately if you would still like to keep it private. E.G. Send me a private link in blender chat. Or I can contact you privately on devtalk or blender chat and send you a link to upload your file or something like that.

I can give a link privately , but I need some instruction for access to Blender chat. Previously I was can't, because I'm stuck on endless page loading.

> Compiled shaders are saved to the shader cache file managed by the GPU driver. They are not saved to the .blend file. > > So the .blend file working fine when "load UI" is unchecked suggests there's something wrong with your UI setup in the file, potentially the UI combined with some Intel Arc feature.s Are you willing to share the .blend file with us? > > Previously you said you wanted to share the file privately. Please let me know how you would like to share the file privately if you would still like to keep it private. E.G. Send me a private link in blender chat. Or I can contact you privately on devtalk or blender chat and send you a link to upload your file or something like that. I can give a link privately , but I need some instruction for access to Blender chat. Previously I was can't, because I'm stuck on endless page loading.

Alaska commented

2023-12-31 00:38:00 +01:00

Member

If your file is less than 2GB in size, you can share it here. https://www.dropbox.com/request/y8rh6zO4OkJ1RHpoi4e7

If it's more than 2GB, then are you able to send me your devtalk profile page link? And I'l contact you there with an alternative way to share the file.

I'm not sure what's going on with Blender chat for you so I don't know how to fix it.

If your file is less than 2GB in size, you can share it here. https://www.dropbox.com/request/y8rh6zO4OkJ1RHpoi4e7 If it's more than 2GB, then are you able to send me your devtalk profile page link? And I'l contact you there with an alternative way to share the file. I'm not sure what's going on with Blender chat for you so I don't know how to fix it.

NicCrimson commented

2024-02-12 16:45:59 +01:00

I am having the same issue with Blender 4.0.2. On an A380.
Compiling shaders, especially complex ones take a long time and freezes Blender until it's unusable or crashes. (Every time my cursor dissapears is a freeze)

Video Demonstration

Node Setup

Blend File: vending_machine_test.blend

Is this a Blender related problem or an Intel one? So I know where to report to.

This might be unrelated. But Cycles rendering also broke:
https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/694 (Read until end)

I am having the same issue with Blender 4.0.2. On an A380. Compiling shaders, especially complex ones take a long time and freezes Blender until it's unusable or crashes. _(Every time my cursor dissapears is a freeze)_ <video src="/attachments/93375983-d597-4c86-bec0-60e052a6383a" title="2024-02-12 11-26-32.mkv" controls></video> _Video Demonstration_ ![image](/attachments/5bba102e-277c-4e93-98e6-a906859ad860) _Node Setup_ Blend File: [vending_machine_test.blend](/attachments/1327582a-121f-4557-816d-9e6b4b689911) Is this a Blender related problem or an Intel one? So I know where to report to. This might be unrelated. But Cycles rendering also broke: https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/694 (Read until end)

216 KiB

vending_machine_test.blend

11 MiB

2024-02-12 11-26-32.mkv

2.3 MiB

Alaska commented

2024-02-13 04:55:33 +01:00

Member

@NicCrimson. Using the vending machine file you attached, I got these results:

Ryzen 5 5600 + AMD RX 7800XT on Windows: 71 second shader compilation time from a clean shader cache
Ryzen 5 5600 + Intel Arc A750 on Windows: 72 second shader compilation time from a clean shader cache

I would test my RTX 4090 to see how NVIDIA compares. But it's a bit of a hassle to get things setup for this test with that specific hardware setup with my current computer layout.

Based on the results above, it seems the shader compilation time between AMD and Intel are close to identical and there's nothing obviously wrong here.

As for the Blender freezing during shader compilation, and shader compilation taking a long time, these are expected at the moment. Complex materials (like the ones you use) take a long time to compile. And the way Blender is setup at the moment means Blender will freeze while compiling the shaders. I do not believe there is a issue here.

As for the Cycles rendering breaking, please file one report per bug. However based on the link provided, it seems to be fixed already.

@NicCrimson. Using the vending machine file you attached, I got these results: Ryzen 5 5600 + AMD RX 7800XT on Windows: 71 second shader compilation time from a clean shader cache Ryzen 5 5600 + Intel Arc A750 on Windows: 72 second shader compilation time from a clean shader cache I would test my RTX 4090 to see how NVIDIA compares. But it's a bit of a hassle to get things setup for this test with that specific hardware setup with my current computer layout. Based on the results above, it seems the shader compilation time between AMD and Intel are close to identical and there's nothing obviously wrong here. As for the Blender freezing during shader compilation, and shader compilation taking a long time, these are expected at the moment. Complex materials (like the ones you use) take a long time to compile. And the way Blender is setup at the moment means Blender will freeze while compiling the shaders. I do not believe there is a issue here. --- As for the Cycles rendering breaking, please file one report per bug. However based on the link provided, it seems to be fixed already.

Alaska commented

2024-02-13 04:57:55 +01:00

Member

@Raid9000 are you able to share the .blend file you're having issues with. I have included a dropbox link for you to privately share your file (if it's below 2GB): https://www.dropbox.com/request/y8rh6zO4OkJ1RHpoi4e7

If the file is bigger than 2GB, feel free to upload the file to a different service. Copy the link to that, past it in a .txt file, and upload the .txt file to Dropbox.

@Raid9000 are you able to share the .blend file you're having issues with. I have included a dropbox link for you to privately share your file (if it's below 2GB): https://www.dropbox.com/request/y8rh6zO4OkJ1RHpoi4e7 If the file is bigger than 2GB, feel free to upload the file to a different service. Copy the link to that, past it in a .txt file, and upload the .txt file to Dropbox.

Andrew commented

2024-02-14 17:56:30 +01:00

Author

@Raid9000 are you able to share the .blend file you're having issues with. I have included a dropbox link for you to privately share your file (if it's below 2GB): https://www.dropbox.com/request/y8rh6zO4OkJ1RHpoi4e7

If the file is bigger than 2GB, feel free to upload the file to a different service. Copy the link to that, past it in a .txt file, and upload the .txt file to Dropbox.

Sended.

> @Raid9000 are you able to share the .blend file you're having issues with. I have included a dropbox link for you to privately share your file (if it's below 2GB): https://www.dropbox.com/request/y8rh6zO4OkJ1RHpoi4e7 > > If the file is bigger than 2GB, feel free to upload the file to a different service. Copy the link to that, past it in a .txt file, and upload the .txt file to Dropbox. Sended.

Alaska commented

2024-02-15 03:57:23 +01:00

Member

@Raid9000 here are my observations with the file provided:

Ryzen 9 5950X + Nvidia RTX 4090: Shaders compile quickly.
Ryzen 5 5600 + AMD RX 7800 XT: Shaders compile quickly.
Ryzen 5 5600 + Intel Arc A750: Shaders compile quickly.
M1 Pro + M1 Pro GPU: Shaders compile quickly.

All of them had freezing issues during compilation. But nothing out of the ordinary for shader compilation.

I did want to confirm that I tested against a few versions of Blender:
3.6.0
3.6.8
4.0.2 (Crashes while opening the file on all platforms I tested - This is a different bug, and has already been fixed for future releases)
4.1.0 2024-02-12 20:16, hash: d45175c919f3

System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits (This is Windows 11)
Graphics card: Intel(R) Arc(TM) A750 Graphics Intel 4.6.0 - Build 31.0.101.5194

I did want to bring up some points.

The file you uploaded is missing it's textures. This might influence the test. Can you please re-upload the file with textures included? You can upload the file to the same link as before https://www.dropbox.com/request/y8rh6zO4OkJ1RHpoi4e7. Same rules applys. If it's less than 2GB, upload it there. If it's more than 2GB, upload it somewhere else, and share the link to the file in the dropbox.
- A easy way to include textures with your file is to select from the top of Blender File -> External Data -> Pack Resources then save the .blend file somewhere. Now all the textures will be included inside the .blend file you just saved.
I also just wanted to confirm how I am supposed to test this bug report.
- Is there a specific version of Blender I'm supposed to be testing? Or should I just continue testing 3.6.8 and 4.1 Beta?
- What are the steps to reproduce the issue. At the moment I've just been doing:
  - Open the file in Blender.
  - Change the viewport mode to Material Preview and waiting until all the shaders have compiled, then navigate around the viewport.
What is the issue? Based on your report it seems to be: When switching to material preview, shaders will be compiled and Blender will freeze (forever?). Is this correct?
Have you tried updating to newer drivers? It has been a few months since you made the report and newer drivers may of fixed your issue.
It's possible you might have a configuration or add-on issue. Does loading Blender with factory settings help? The steps to do so are:
- Select from the top of Blender File -> Load Factory Settings
- Open your file in that Blender window.
- Test it.
What CPU do you have?

@Raid9000 here are my observations with the file provided: Ryzen 9 5950X + Nvidia RTX 4090: Shaders compile quickly. Ryzen 5 5600 + AMD RX 7800 XT: Shaders compile quickly. Ryzen 5 5600 + Intel Arc A750: Shaders compile quickly. M1 Pro + M1 Pro GPU: Shaders compile quickly. All of them had freezing issues during compilation. But nothing out of the ordinary for shader compilation. I did want to confirm that I tested against a few versions of Blender: 3.6.0 3.6.8 4.0.2 (Crashes while opening the file on all platforms I tested - This is a different bug, and has already been fixed for future releases) 4.1.0 2024-02-12 20:16, hash: `d45175c919f3` **System Information** Operating system: Windows-10-10.0.22631-SP0 64 Bits (This is Windows 11) Graphics card: Intel(R) Arc(TM) A750 Graphics Intel 4.6.0 - Build 31.0.101.5194 --- I did want to bring up some points. - The file you uploaded is missing it's textures. This might influence the test. Can you please re-upload the file with textures included? You can upload the file to the same link as before https://www.dropbox.com/request/y8rh6zO4OkJ1RHpoi4e7. Same rules applys. If it's less than 2GB, upload it there. If it's more than 2GB, upload it somewhere else, and share the link to the file in the dropbox. - A easy way to include textures with your file is to select from the top of Blender `File -> External Data -> Pack Resources` then save the .blend file somewhere. Now all the textures will be included inside the .blend file you just saved. - I also just wanted to confirm how I am supposed to test this bug report. - Is there a specific version of Blender I'm supposed to be testing? Or should I just continue testing 3.6.8 and 4.1 Beta? - What are the steps to reproduce the issue. At the moment I've just been doing: - Open the file in Blender. - Change the viewport mode to `Material Preview` and waiting until all the shaders have compiled, then navigate around the viewport. - What is the issue? Based on your report it seems to be: When switching to material preview, shaders will be compiled and Blender will freeze (forever?). Is this correct? - Have you tried updating to newer drivers? It has been a few months since you made the report and newer drivers may of fixed your issue. - It's possible you might have a configuration or add-on issue. Does loading Blender with factory settings help? The steps to do so are: - Select from the top of Blender `File -> Load Factory Settings` - Open your file in that Blender window. - Test it. - What CPU do you have?

Andrew commented

2024-02-15 06:37:44 +01:00

Author

missing textures

Not relevant, because I tested separately, and also was same freezes. For now I don't see problems, at least for 3.6 Any new statistics will be available after migration on 4+ version.

CPU

Intel core i5 15400f

>missing textures Not relevant, because I tested separately, and also was same freezes. For now I don't see problems, at least for 3.6 Any new statistics will be available after migration on 4+ version. >CPU Intel core i5 15400f

Andrew commented

2024-02-15 06:47:17 +01:00

Author

missing textures
Not relevant, because I tested separately, and also was same freezes. For now I don't see problems, at least for 3.6 Any new statistics will be available after migration on 4+ version.

procrssor
Intel core i5 15400f

>missing textures Not relevant, because I tested separately, and also was same freezes. For now I don't see problems, at least for 3.6 Any new statistics will be available after migration on 4+ version. >procrssor Intel core i5 15400f

Andrew closed this issue

2024-02-15 06:47:20 +01:00

Blender Bot added

and removed

Needs Information from User

labels 2024-02-15 06:47:22 +01:00

Andrew reopened this issue

2024-02-15 06:47:38 +01:00

Blender Bot added

and removed

labels 2024-02-15 06:47:40 +01:00

Alaska commented

2024-02-15 07:25:37 +01:00

Member

For now I don't see problems, at least for 3.6

Does that mean the issue has gone away?

> For now I don't see problems, at least for 3.6 Does that mean the issue has gone away?

Andrew commented

2024-02-15 18:17:11 +01:00

Author

For now I don't see problems, at least for 3.6

Does that mean the issue has gone away?

Seems like so.

> > For now I don't see problems, at least for 3.6 > > Does that mean the issue has gone away? Seems like so.

Alaska commented

2024-02-15 21:56:11 +01:00

Member

I'll close this issue for now. If you encounter this issue again, feel free to create a new report.

I'll close this issue for now. If you encounter this issue again, feel free to create a new report.

Alaska closed this issue

2024-02-15 21:56:14 +01:00

Blender Bot added

and removed

labels 2024-02-15 21:57:34 +01:00

Sign in to join this conversation.

No Label

Animation & Rigging

Asset Browser Project (Legacy)

Automated Testing

Blender Asset Bundle

Dependency Graph

Development Management

EEVEE & Viewport

Images & Movies

Motion Tracking

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Render Pipeline

Sculpt, Paint & Texture

Video Sequencer

Virtual Reality

Blender 2.8 Project

Milestone 1: Basic, Local Asset Browser

Good First Issue

Animation & Rigging

Development Management

EEVEE & Viewport

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Sculpt, Paint & Texture

Needs Info from Developers

Needs Information from User

No Milestone

No project

No Assignees

5 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#111556

No description provided.