Regression: Blender 3.5 crashes when selecting either Viewport Shading Material and Rendered #106278

System Information
Operating system: Windows 10 home : Laptop Lenovo G50-80
Graphics card: Intel(R) HD Graphics 5500 4.4.0 - Build 20.19.15.5171

Blender Version
Broken: 3.5
Worked: (3.4.1)

Short description of error

Exact steps for others to reproduce the error
Just installed Blender 3.5. Everything is factory default; no Addons were imported over from blender 3.4.1.

Went to check viewport shading previews. Every time I clicked on Viewport Materiel or Rendered, Blender 3.5 crashes. This happens in Eevee and Cycles. No Blend file is loaded.This is from the Splash Screen, New session factory default.

**System Information** Operating system: Windows 10 home : Laptop Lenovo G50-80 Graphics card: Intel(R) HD Graphics 5500 4.4.0 - Build 20.19.15.5171 **Blender Version** Broken: 3.5 Worked: (3.4.1) **Short description of error** **Exact steps for others to reproduce the error** Just installed Blender 3.5. Everything is factory default; no Addons were imported over from blender 3.4.1. Went to check viewport shading previews. Every time I clicked on Viewport Materiel or Rendered, Blender 3.5 crashes. This happens in Eevee and Cycles. No Blend file is loaded.This is from the Splash Screen, New session factory default.

Please open Blender's installation directory and double click on the blender_debug_gpu.cmd. This will start Blender in debug mode and create log files. Try to reproduce the
error again. Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them
to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt (or simply type %TEMP% into the path bar of the Windows Explorer).

Please open Blender's installation directory and double click on the `blender_debug_gpu.cmd`. This will start Blender in debug mode and create log files. Try to reproduce the error again. Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in `C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt` (or simply type `%TEMP%` into the path bar of the Windows Explorer).![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png)

@PratikPB2123. Thanks for letting me know how to create the crash files. I didn't see any when Blender 3.5 crashed....

The same thing happened in Blender 3.6 Alpha.

@PratikPB2123. Thanks for letting me know how to create the crash files. I didn't see any when Blender 3.5 crashed.... The same thing happened in Blender 3.6 Alpha.

blender_debug_output.txt

140 KiB

blender_system_info.txt

12 KiB

blender.crash.txt

15 KiB

Hi, old GPU/GPU drivers are causing the crash here.
Upgrading GPU drivers might fix the crash: https://docs.blender.org/manual/en/dev/troubleshooting/gpu/windows/intel.html

Hi, old GPU/GPU drivers are causing the crash here. Upgrading GPU drivers might fix the crash: https://docs.blender.org/manual/en/dev/troubleshooting/gpu/windows/intel.html

Hi, old GPU/GPU drivers are causing the crash here.
Upgrading GPU drivers might fix the crash: https://docs.blender.org/manual/en/dev/troubleshooting/gpu/windows/intel.html

I tried and it didn't work

> Hi, old GPU/GPU drivers are causing the crash here. > Upgrading GPU drivers might fix the crash: https://docs.blender.org/manual/en/dev/troubleshooting/gpu/windows/intel.html I tried and it didn't work

Start blender from blender_debug_gpu_glitchworkaround.cmd batch file. See if that helps.

Start blender from `blender_debug_gpu_glitchworkaround.cmd` batch file. See if that helps.

Thanks for trying to help. Your suggestion blender_debug_gpu_glitchworkaround.cmd. didn’t work, only produce crash log error files.

I know my Laptop is not brand new anymore, but my Intel Driver is supported according to Blender System requirements, and is up to date.

There was an issue some time back with one of the Blender Builds, causing a weird distortion on the Cube when entering Edit Mode. There were quite a few bug reports, because it only affected intel drivers. Somebody forgot to add a line in the code, causing that to happen.

Blender 3.4.1 works just fine, so something has changed again making Blender 3.5 crash, just by selecting Viewport Material or Rendered.

Thanks for trying to help. Your suggestion blender_debug_gpu_glitchworkaround.cmd. didn’t work, only produce crash log error files. I know my Laptop is not brand new anymore, but my Intel Driver is supported according to Blender System requirements, and is up to date. There was an issue some time back with one of the Blender Builds, causing a weird distortion on the Cube when entering Edit Mode. There were quite a few bug reports, because it only affected intel drivers. Somebody forgot to add a line in the code, causing that to happen. Blender 3.4.1 works just fine, so something has changed again making Blender 3.5 crash, just by selecting Viewport Material or Rendered.

blender.crash.txt

15 KiB

blender_debug_output.txt

163 KiB

blender_system_info.txt

12 KiB

Intel Driver.jpg

76 KiB

take look at mine

blender_debug_output.txt

298 KiB

blender_system_info.txt

12 KiB

It's happening for me on older versions of Blender too. It will either get killed or just hang, but with similar debug info. It seems to have something to do with CUEW and HIPEW initialization failing, but have no idea what that means. As it's not our drivers, perhaps it's OpenGL or another app that has been installed recently. I recently installed Bluestacks (Android emulator)—either of you done that?

blender_system_info.txt

14 KiB

blender_debug_output.txt

773 KiB

@Edmund-Wood . I haven't installed Bluestacks (Android emulator).

My OpenGL is 4.4

Blender 3.4.1 works perfectly. Something has changed in Blender 3.5 making the intel drivers we have installed not work properly.

@Edmund-Wood . I haven't installed Bluestacks (Android emulator). My OpenGL is 4.4 Blender 3.4.1 works perfectly. Something has changed in Blender 3.5 making the intel drivers we have installed not work properly.

@PratikPB2123 . I noticed a new feature in Blender 3.6 Alpha. The N-Panel has a scrolling feature, which is really good, beacuse you can see all the Addons Names.

I only checked Blender 3.6 Alpha to see if the Viewport Material, Rendered issue was still there, and it is.

If the new N-Panel feature is implemented in Blender 3.6 Alpha. Will that feature be in Blender 3.3LTS?

The reason I ask, because some of the Addons I have bought need Blender 3.4 to work. They can't run in the Blender 3.3LTS version.

The N-Panel needed a fix, and Blender 3.6 Alpha seems to have solved it. But it won't be in Blender 3.4 because it's not LTS. Is that how Blender LTS works? new features added?

Sorry to go off topic, but right now the N-Panel scrolling feature is really needed, as the Addons are all bunched up and squashed.

@PratikPB2123 . I noticed a new feature in Blender 3.6 Alpha. The N-Panel has a scrolling feature, which is really good, beacuse you can see all the Addons Names. I only checked Blender 3.6 Alpha to see if the Viewport Material, Rendered issue was still there, and it is. If the new N-Panel feature is implemented in Blender 3.6 Alpha. Will that feature be in Blender 3.3LTS? The reason I ask, because some of the Addons I have bought need Blender 3.4 to work. They can't run in the Blender 3.3LTS version. The N-Panel needed a fix, and Blender 3.6 Alpha seems to have solved it. But it won't be in Blender 3.4 because it's not LTS. Is that how Blender LTS works? new features added? Sorry to go off topic, but right now the N-Panel scrolling feature is really needed, as the Addons are all bunched up and squashed.

having facing and shareds issue too blender just crashes #106377

I don't have same hardware to verify/investigate the problem but it appears to be a valid crash report since multiple users are affected by this.
Perhaps the recent changes in shader code for metal support has introduced the issue.
Will raise the priority for now.
cc @fclem
cc @Jeroen-Bakker

Sorry to go off topic: If the new N-Panel feature is implemented in Blender 3.6 Alpha. Will that feature be in Blender 3.3LTS?

Depends on commit. Bigger changes and new features sometimes introduces newer issues so they are not backported to LTS. I'll check which commit has implemented the scrolling feature.

Lets halt the discussion here :)

I don't have same hardware to verify/investigate the problem but it appears to be a valid crash report since multiple users are affected by this. Perhaps the recent changes in shader code for metal support has introduced the issue. Will raise the priority for now. cc @fclem cc @Jeroen-Bakker - - - >Sorry to go off topic: If the new N-Panel feature is implemented in Blender 3.6 Alpha. Will that feature be in Blender 3.3LTS? Depends on commit. Bigger changes and new features sometimes introduces newer issues so they are not backported to LTS. I'll check which commit has implemented the scrolling feature. Lets halt the discussion here :)

I installed 3.3 and it works fine, the older ones no longer matter now and will uninstall.
Installed 3.5 on another computer and crashes the same upon opening material properties.

I installed 3.3 and it works fine, the older ones no longer matter now and will uninstall. Installed 3.5 on another computer and crashes the same upon opening material properties.

cant install version 3.3 from steam

I am currently building a system to try to replicate the issue. I have found a system, but doesn't have windows installed so it might take some time to get it reproducable.

bpy.context.space_data.context = 'MATERIAL'  # Property

# backtrace
Exception Record:

ExceptionCode         : EXCEPTION_ACCESS_VIOLATION
Exception Address     : 0x00007FF66EF7AAC3
Exception Module      : blender.exe
Exception Flags       : 0x00000000
Exception Parameters  : 0x2
	Parameters[0] : 0x0000000000000000
	Parameters[1] : 0x0000000000000008


Stack trace:
blender.exe         :0x00007FF66EF7AAB0  DRW_shgroup_uniform_float_copy
blender.exe         :0x00007FF66EF84810  EEVEE_lightprobes_cache_init
blender.exe         :0x00007FF66EF89FE0  EEVEE_render_cache_init
blender.exe         :0x00007FF66EF8C2A0  eevee_render_to_image
blender.exe         :0x00007FF66EF683B0  DRW_render_to_image
blender.exe         :0x00007FF66F9829E0  engine_render_view_layer
blender.exe         :0x00007FF66F984260  RE_engine_render
blender.exe         :0x00007FF66F98AA60  RE_PreviewRender
blender.exe         :0x00007FF6700D3070  shader_preview_render
blender.exe         :0x00007FF6700D32A0  shader_preview_startjob
blender.exe         :0x00007FF6700D1A40  icon_preview_startjob
blender.exe         :0x00007FF6700D1D00  icon_preview_startjob_all_sizes
blender.exe         :0x00007FF66EE63780  do_job_thread
blender.exe         :0x00007FF6745ED670  _ptw32_threadStart
ucrtbase.dll        :0x00007FF8CE081B20  configthreadlocale
KERNEL32.DLL        :0x00007FF8CE497600  BaseThreadInitThunk
ntdll.dll           :0x00007FF8D03E2680  RtlUserThreadStart

```# Blender 3.5.0, Commit date: 2023-03-29 02:56, Hash 1be25cfff18b bpy.context.space_data.context = 'MATERIAL' # Property # backtrace Exception Record: ExceptionCode : EXCEPTION_ACCESS_VIOLATION Exception Address : 0x00007FF66EF7AAC3 Exception Module : blender.exe Exception Flags : 0x00000000 Exception Parameters : 0x2 Parameters[0] : 0x0000000000000000 Parameters[1] : 0x0000000000000008 Stack trace: blender.exe :0x00007FF66EF7AAB0 DRW_shgroup_uniform_float_copy blender.exe :0x00007FF66EF84810 EEVEE_lightprobes_cache_init blender.exe :0x00007FF66EF89FE0 EEVEE_render_cache_init blender.exe :0x00007FF66EF8C2A0 eevee_render_to_image blender.exe :0x00007FF66EF683B0 DRW_render_to_image blender.exe :0x00007FF66F9829E0 engine_render_view_layer blender.exe :0x00007FF66F984260 RE_engine_render blender.exe :0x00007FF66F98AA60 RE_PreviewRender blender.exe :0x00007FF6700D3070 shader_preview_render blender.exe :0x00007FF6700D32A0 shader_preview_startjob blender.exe :0x00007FF6700D1A40 icon_preview_startjob blender.exe :0x00007FF6700D1D00 icon_preview_startjob_all_sizes blender.exe :0x00007FF66EE63780 do_job_thread blender.exe :0x00007FF6745ED670 _ptw32_threadStart ucrtbase.dll :0x00007FF8CE081B20 configthreadlocale KERNEL32.DLL :0x00007FF8CE497600 BaseThreadInitThunk ntdll.dll :0x00007FF8D03E2680 RtlUserThreadStart ```

Sorry for my late answer! ... For your information, I loaded the 3.4 version to see if I have the same issue. I can confirm that 3.4 version is running well on my computer

@John-Valley thanks for the information.

Looking into the code it might be related to the next part.

 if (grp == NULL) {
      Scene *scene = draw_ctx->scene;
      World *world = (scene->world) ? scene->world : EEVEE_world_default_get();

      const int options = VAR_WORLD_BACKGROUND | VAR_WORLD_PROBE;
      struct GPUMaterial *gpumat = EEVEE_material_get(vedata, scene, NULL, world, options);

      grp = DRW_shgroup_material_create(gpumat, psl->probe_background);
      DRW_shgroup_uniform_float_copy(grp, "backgroundAlpha", 1.0f);
    }

In case the world materials cannot be compiled the grp might still be invalid and isn't taken into account in this part.

Some questions to check when I have a system:

Why does the world material shader fail to compile.
This seems to be inside a icon/preview render which makes me wonder if
- default.blend has changed to display the material previews
- icon/previews are used in different places?
- logic has changed that triggers icon/previews
- Shader is failing
- ....

Many different questions to look into.

@John-Valley thanks for the information. Looking into the code it might be related to the next part. ``` if (grp == NULL) { Scene *scene = draw_ctx->scene; World *world = (scene->world) ? scene->world : EEVEE_world_default_get(); const int options = VAR_WORLD_BACKGROUND | VAR_WORLD_PROBE; struct GPUMaterial *gpumat = EEVEE_material_get(vedata, scene, NULL, world, options); grp = DRW_shgroup_material_create(gpumat, psl->probe_background); DRW_shgroup_uniform_float_copy(grp, "backgroundAlpha", 1.0f); } ``` In case the world materials cannot be compiled the grp might still be invalid and isn't taken into account in this part. Some questions to check when I have a system: - Why does the world material shader fail to compile. - This seems to be inside a icon/preview render which makes me wonder if - default.blend has changed to display the material previews - icon/previews are used in different places? - logic has changed that triggers icon/previews - Shader is failing - .... Many different questions to look into.

I am not able to reproduce the issue due to not having access to a system with a HD5500 series iGPU.

Looking at some reports https://projects.blender.org/attachments/4707422e-062f-44ee-91d2-75ceedf4e726 shows that unrolling macros isn't working on this platform. @fclem what do you think this could be?

I am not able to reproduce the issue due to not having access to a system with a HD5500 series iGPU. Looking at some reports https://projects.blender.org/attachments/4707422e-062f-44ee-91d2-75ceedf4e726 shows that unrolling macros isn't working on this platform. @fclem what do you think this could be?

Can someone download https://builder.blender.org/download/patch/PR106535/ install it and check if it runs correctly. When it doesn't please attach the debug_output from this version in order to see if we are on the right track.

NOTE: that this is Blender 3.6. After the issue is fixed it will be backported to 3.5.1

Can someone download https://builder.blender.org/download/patch/PR106535/ install it and check if it runs correctly. When it doesn't please attach the debug_output from this version in order to see if we are on the right track. NOTE: that this is Blender 3.6. After the issue is fixed it will be backported to 3.5.1

Can someone download https://builder.blender.org/download/patch/PR106535/ install it and check if it runs correctly. When it doesn't please attach the debug_output from this version in order to see if we are on the right track.

NOTE: that this is Blender 3.6. After the issue is fixed it will be backported to 3.5.1

@Jeroen-Bakker

I ran the Blender 3.6 Build in normal mode first, it crashed as before, so ran in blender_debug_gpu and blender_debug_gpu_glitchworkaround.

> Can someone download https://builder.blender.org/download/patch/PR106535/ install it and check if it runs correctly. When it doesn't please attach the debug_output from this version in order to see if we are on the right track. > > NOTE: that this is Blender 3.6. After the issue is fixed it will be backported to 3.5.1 @Jeroen-Bakker I ran the Blender 3.6 Build in normal mode first, it crashed as before, so ran in blender_debug_gpu and blender_debug_gpu_glitchworkaround.

blender_system_info.txt

13 KiB

blender_debug_output.txt

110 KiB

blender_system_info.txt

13 KiB

blender_debug_output.txt

74 KiB

Thanks, I will have another try!

There is a new build available at https://builder.blender.org/download/patch/PR106535/

Please try again and when failing attache the debug output. Thanks a lot!

There is a new build available at https://builder.blender.org/download/patch/PR106535/ Please try again and when failing attache the debug output. Thanks a lot!

There is a new build available at https://builder.blender.org/download/patch/PR106535/

Please try again and when failing attache the debug output. Thanks a lot!

> There is a new build available at https://builder.blender.org/download/patch/PR106535/ > > Please try again and when failing attache the debug output. Thanks a lot!

blender_debug_output.txt

115 KiB

blender_debug_output.txt

76 KiB

blender_system_info.txt

13 KiB

Ok, seems there are no macro errors anymore, but somehow it is complaining about an illegal character. '`' To my knowledge we use this all the time. not sure why it is now failing. Anyhow will patch the shader for the next try!

I found a possible cause of the next issue. Can someone test again? New version is available at https://builder.blender.org/download/patch/PR106535/

I am signing off for today and will be back on Thursday to continue to work on this issue.

I found a possible cause of the next issue. Can someone test again? New version is available at https://builder.blender.org/download/patch/PR106535/ I am signing off for today and will be back on Thursday to continue to work on this issue.

I found a possible cause of the next issue. Can someone test again? New version is available at https://builder.blender.org/download/patch/PR106535/

I am signing off for today and will be back on Thursday to continue to work on this issue.

@Jeroen-Bakker. This version is working! I have clicked on Viewport Material and Rendered, and also the Material Properties Tab, No Crashes!

Can other users test and confirm!

> I found a possible cause of the next issue. Can someone test again? New version is available at https://builder.blender.org/download/patch/PR106535/ > > I am signing off for today and will be back on Thursday to continue to work on this issue. @Jeroen-Bakker. This version is working! I have clicked on Viewport Material and Rendered, and also the Material Properties Tab, No Crashes! > > > > > Can other users test and confirm!

also big thanks to all of you for reporting and testing! I will wait for some more feedback and if everything is fine commit it to 3.6 and 3.5

also big thanks to all of you for reporting and testing! I will wait for some more feedback and if everything is fine commit it to 3.6 and 3.5

@Jeroen-Bakker The first try was with No Addons imported over from Blender 3.4.1. Factory default.

The second try which I just done now, with Addons imported from Blender 3.4.1, and my personal settings. No crashes. I have quite a few Addons.

Just to add. Tested in Cycles as well, no crashes. Cycles feels quicker!

> also big thanks to all of you for reporting and testing! I will wait for some more feedback and if everything is fine commit it to 3.6 and 3.5 @Jeroen-Bakker The first try was with No Addons imported over from Blender 3.4.1. Factory default. The second try which I just done now, with Addons imported from Blender 3.4.1, and my personal settings. No crashes. I have quite a few Addons. Just to add. Tested in Cycles as well, no crashes. Cycles feels quicker!

Viewport Material.jpg

247 KiB

Viewport Rendred.jpg

224 KiB

Yep, it looks like you've fixed it. No problems here. Thank you.

Hey Jeroen,
I also had a similar issue like yours. You just need to download this patch build and it seems like it works.( It solved my problem )

here - https://builder.blender.org/download/patch/PR106535/

download this file and test it.

This is blender 3.6 Alpha build, its not the final release but it may solve your issue.

I tested it and it works. There is no issue using it.

Have a nice day!

Hey Jeroen, I also had a similar issue like yours. You just need to download this patch build and it seems like it works.( It solved my problem ) here - https://builder.blender.org/download/patch/PR106535/ download this file and test it. This is blender 3.6 Alpha build, its not the final release but it may solve your issue. I tested it and it works. There is no issue using it. Have a nice day!

LOL @Cherry-2 yes I am the developer of that patch :-)

Another positive. The patch works for me also. Thx.

Hey Jeroen,
I also had a similar issue like yours. You just need to download this patch build and it seems like it works.( It solved my problem )

here - https://builder.blender.org/download/patch/PR106535/

download this file and test it.

This is blender 3.6 Alpha build, its not the final release but it may solve your issue.

I tested it and it works. There is no issue using it.

Have a nice day!

3.6 fixes crash for me when picking viewport shading.

> Hey Jeroen, > I also had a similar issue like yours. You just need to download this patch build and it seems like it works.( It solved my problem ) > > here - https://builder.blender.org/download/patch/PR106535/ > > download this file and test it. > > This is blender 3.6 Alpha build, its not the final release but it may solve your issue. > > I tested it and it works. There is no issue using it. > > Have a nice day! 3.6 fixes crash for me when picking viewport shading.

also big thanks to all of you for reporting and testing! I will wait for some more feedback and if everything is fine commit it to 3.6 and 3.5

thanks this vesrion is working well i have reported simillar issue #106412 and its working for me :)

> also big thanks to all of you for reporting and testing! I will wait for some more feedback and if everything is fine commit it to 3.6 and 3.5 thanks this vesrion is working well i have reported simillar issue #106412 and its working for me :)

There is a chance that we have to revert this change as more users are reporting that since this change MacOS/AMD has major regressions. We try to fix this, but if we are only able to support one or the other....

There is a chance that we have to revert this change as more users are reporting that since this change MacOS/AMD has major regressions. We try to fix this, but if we are only able to support one or the other....

@Jeroen-Bakker Do you mean the Blender 3.6 Alpha build you patched? And there's a possibility to go back as it was, in Blender 3.5

I thought it was for Windows users, using Intel Graphic drivers.

It’s a shame that there isn’t a check box in the System Preferences, to allow users to disable certain display features and use Blender 3.4 display settings.

> There is a chance that we have to revert this change as more users are reporting that since this change MacOS/AMD has major regressions. We try to fix this, but if we are only able to support one or the other.... @Jeroen-Bakker Do you mean the Blender 3.6 Alpha build you patched? And there's a possibility to go back as it was, in Blender 3.5 I thought it was for Windows users, using Intel Graphic drivers. It’s a shame that there isn’t a check box in the System Preferences, to allow users to disable certain display features and use Blender 3.4 display settings.

Changes that are being made are not for specific platforms. They are for all platforms. Due to platform differences (bugs in drivers) we try to find solutions that work for all platforms. So adding this change created a bigger regression on MacOS/AMD platform.

Adding a checkbox doesn't work as that might require two different versions of Eevee. Meaning two times the effort in support or adding new features. The fix of this patch is so low level that it can impact many things.

That checkbox would therefore be the same as installing Blender 3.4. I will have access to a system this morning and will try to find a solution that will work on both platforms. If I am not able to find it we might need to make a hard decision on platform support.

Would like your help on testing the eventual fix so we know for sure it works on your system as well.

When the builds are available can anyone check https://builder.blender.org/download/patch/PR106887/

Changes that are being made are not for specific platforms. They are for all platforms. Due to platform differences (bugs in drivers) we try to find solutions that work for all platforms. So adding this change created a bigger regression on MacOS/AMD platform. Adding a checkbox doesn't work as that might require two different versions of Eevee. Meaning two times the effort in support or adding new features. The fix of this patch is so low level that it can impact many things. That checkbox would therefore be the same as installing Blender 3.4. I will have access to a system this morning and will try to find a solution that will work on both platforms. If I am not able to find it we might need to make a hard decision on platform support. Would like your help on testing the eventual fix so we know for sure it works on your system as well. When the builds are available can anyone check https://builder.blender.org/download/patch/PR106887/

@Jeroen-Bakker

This build is working, not sure if it's altered yet. Just letting you know.

I was looking at the date and time. April 13, 10:42:25 106887 zip 294.81MB

@Jeroen-Bakker This build is working, not sure if it's altered yet. Just letting you know. I was looking at the date and time. April 13, 10:42:25 106887 zip 294.81MB

Thanks a lot. Seems we have found a winner.

Thanks a lot. Seems we have found a winner.

@Jeroen-Bakker

That's Great News! Glad I could help testing! :)

I tested again with my personals settings and Addons, and they're working as well.

Tried in Cycles, that's working too. Not sure what you Guys are doing, but Cycles feels faster than the last build I tried. My CPU doesn't like it LOL, but I know that from before, so not an issue. Nice Job on this Blender 3.6 Alpha Build.

> Thanks a lot. Seems we have found a winner. @Jeroen-Bakker That's Great News! Glad I could help testing! :) I tested again with my personals settings and Addons, and they're working as well. Tried in Cycles, that's working too. Not sure what you Guys are doing, but Cycles feels faster than the last build I tried. My CPU doesn't like it LOL, but I know that from before, so not an issue. Nice Job on this Blender 3.6 Alpha Build.

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Labels Milestones

Regression: Blender 3.5 crashes when selecting either Viewport Shading Material and Rendered #106278