search

PhysicalAddons / physical-starlight-and-atmosphere

issue tracker
16 stars 2 forks source link

Consistent crash on 1.4.x (right after pressing F12) #43

Closed hokutonanto closed 2 years ago

hokutonanto commented 3 years ago

OS Windows 10 x64 Blender 2.93.1 official release

When I try to render this scene, Blender crashes, though the view port preview works fine. Log and scene attached.

room-WFSP.crash.txt

B3D scene https://we.tl/t-PcbYJmS8xQ

threesixtyat commented 3 years ago

hey @karlisup, my blender 3.0.0 28-06-2021 is also crashing with 1.4.1 on macOS 11.4

exact same issue as @hokutonanto, so i assume it is not related to blender or OS

thanks ;-)

Log:

`UNSUPPORTED (log once): POSSIBLE ISSUE: unit 0 GLD_TEXTURE_INDEX_2D_ARRAY is unloadable and bound to sampler type (Float) - using zero texture because texture unloadable Traceback (most recent call last): File "/Users/NAME/Library/Application Support/Blender/3.0/scripts/addons/physical-starlight-atmosphere/properties.py", line 1165, in align_defaults_with_preset bpy.ops.script.execute_preset( File "/Applications/Blender.app/Contents/Resources/3.0/scripts/modules/bpy/ops.py", line 126, in call _BPyOpsSubModOp._view_layer_update(context) File "/Applications/Blender.app/Contents/Resources/3.0/scripts/modules/bpy/ops.py", line 90, in _view_layer_update view_layer.update() RuntimeError: Error: Dependency graph update requested during evaluation

Blender(1086,0x170933000) malloc: error for object 0x133381e00: pointer being freed was not allocated Blender(1086,0x170933000) malloc: set a breakpoint in malloc_error_break to debug Blender(1086,0x171d6f000) malloc: error for object 0x129ff8000: pointer being freed was not allocated Blender(1086,0x171d6f000) malloc: set a breakpoint in malloc_error_break to debug Blender(1086,0x171963000) malloc: error for object 0x1398a0000: pointer being freed was not allocated Blender(1086,0x171963000) malloc: set a breakpoint in malloc_error_break to debug Blender(1086,0x171557000) malloc: error for object 0x161070000: pointer being freed was not allocated Blender(1086,0x171557000) malloc: set a breakpoint in malloc_error_break to debug zsh: abort /Applications/Blender.app/Contents/MacOS/Blender`

hokutonanto commented 3 years ago

OS Windows 10 x64 Blender 2.93.1 official release

When I try to render this scene, Blender crashes, though the view port preview works fine. Log and scene attached.

room-WFSP.crash.txt

B3D scene https://we.tl/t-PcbYJmS8xQ

Please, let me know if you got the scene, the link is about to expire.

Flameseeker006 commented 3 years ago

Having the same problem. 1.3.1 works without any issues. 1.4.1 consistently crashes right after pressing F12 to render. Happens with both Cycles and Eevee. Viewport rendering works fine.

I've noticed that when I create a new scene and activate the addon, rendering works without issues. When I save that scene and reopen it, the problem occurs and Blender immediately crashes after trying to render it. I've managed to replicate this many times.

I'll attach logs from two different scenes.

Jama beginner tut.crash.txt whyismyrendercrashing.crash.txt

bischofftep commented 3 years ago

Experiencing the same issue: doesn't seem to be tied to any particular setting of clouds/no clouds, stars/no stars, etc.

Blender 2.93.2 LTS, Windows 10, two RTX 2080 Ti cards, rendering in OPTIX mode.

karlisup commented 3 years ago

Hi everyone, Thank you for your patience! Could you, please try the new beta version (v1.4.2) and report if this issue persists? We had issues reproducing it. We relied on complete refactoring of shader node setup to fix it, but from the reports it seems that it has not been fixed.

Please, let me know if you got the scene, the link is about to expire.

I am sorry @hokutonanto, I didn't make in time, but crash and error logs gathered here gives a good insight of what could be the reason. Hypothesis is that it is related somehow with presets and preset execution. The problem now is that we cannot yet test if we fix the issue or not as we cannot reproduce it.

It would help a bunch if you could try this and report the results:

  1. you open blender 2.9x
  2. on clean scene > enable PSA addon v1.4.2
  3. Hit F12

  4. Does it crash?

If not:

  1. save this in blendfile
  2. reopen this project
  3. Hit F12

  4. Does it crash?

bischofftep commented 3 years ago

Successful render in both cases. Plus clouds work in Cycles. :-)

Flameseeker006 commented 3 years ago

Succesful render indeed! And also yes the clouds working in Cycles..nice!

karlisup commented 3 years ago

I leave the ticket open just to see if there are no more reports regarding this issue. Thank you @bischofftep and @Flameseeker006 for reporting the results. Much appreciated!

evie404 commented 3 years ago

Hi, I just bought this plugin and have been getting extremely frequent crashes whenever I render with atmosphere on. I've even tried resorting to CPU rendering just to make sure it's not a driver issue. The crash only happens during render. Rendered preview in viewport works perfectly fine.

This is the debug log from Blender. I couldn't get a crash log for some reasons :/

I0918 12:48:27.079037 16940 blender_python.cpp:195] Debug flags initialized to:
CPU flags:
  AVX2       : True
  AVX        : True
  SSE4.1     : True
  SSE3       : True
  SSE2       : True
  BVH layout : EMBREE
  Split      : False
CUDA flags:
  Adaptive Compile : False
OptiX flags:
  CUDA streams : 1
OpenCL flags:
  Device type    : ALL
  Debug          : False
  Memory limit   : 0
I0918 12:48:27.847040 16940 device_opencl.cpp:48] CLEW initialization succeeded.
I0918 12:48:27.933547 16940 device_cuda.cpp:41] CUEW initialization succeeded
I0918 12:48:27.933547 16940 device_cuda.cpp:43] Found precompiled kernels
ERROR (bke.fcurve): C:\Users\blender\git\blender-v293\blender.git\source\blender\blenkernel\intern\fcurve_driver.c:138 dtar_get_prop_val: Driver Evaluation Error: cannot resolve target for SCScene.001 -> node_tree.nodes["Transform"].inputs[4].default_value
ERROR (bke.fcurve): C:\Users\blender\git\blender-v293\blender.git\source\blender\blenkernel\intern\fcurve_driver.c:138 dtar_get_prop_val: Driver Evaluation Error: cannot resolve target for SCScene.001 -> node_tree.nodes["Transform"].inputs[2].default_value
ERROR (bke.fcurve): C:\Users\blender\git\blender-v293\blender.git\source\blender\blenkernel\intern\fcurve_driver.c:138 dtar_get_prop_val: Driver Evaluation Error: cannot resolve target for SCScene.001 -> node_tree.nodes["Transform"].inputs[1].default_value
ERROR (bke.fcurve): C:\Users\blender\git\blender-v293\blender.git\source\blender\blenkernel\intern\fcurve_driver.c:138 dtar_get_prop_val: Driver Evaluation Error: cannot resolve target for SCScene.001 -> node_tree.nodes["Transform"].inputs[3].default_value
I0918 12:48:32.658418 16940 device_cuda.cpp:177] Device has compute preemption or is not used for display.
I0918 12:48:32.658418 16940 device_cuda.cpp:180] Added device "NVIDIA GeForce RTX 2080 Ti" with id "CUDA_NVIDIA GeForce RTX 2080 Ti_0000:0b:00".
Memoryblock MORE THAN 1 MEMORYBLOCK CORRUPT: error in header
Memoryblock MORE THAN 1 MEMORYBLOCK CORRUPT: error in header
Memoryblock dupli_alloc: double free
Memoryblock dupli_alloc: double free
Memoryblock dupli_alloc: double free
Memoryblock MORE THAN 1 MEMORYBLOCK CORRUPT: error in header

lmk if I should open a new issue

ontogenic commented 2 years ago

I'm also seeing this pattern of problem - in blender 2.9.3, with PSA 1.4.2 - render preview works but if I try to render it crashes. What information can I share to help get this fixed?

Python backtrace (collapsed) # Blender 2.93.0, Commit date: 2021-06-02 11:21, Hash 84da05a8b806 Read library: 'D:\RasterStudio\Assets\Self\Hardware\LNER A3\lner_a3_version_2.blend', '//..\lner_a3_version_2.blend', parent '' # Info Read library: 'D:\RasterStudio\Assets\Self\People\MatthewHurst\matthewhurst.blend', '//..\..\..\People\MatthewHurst\matthewhurst.blend', parent '' # Info Read library: 'D:\Crail\Hardware\N2\n2.blend', '//..\..\..\..\..\..\Crail\Hardware\N2\n2.blend', parent '' # Info Read library: 'D:\RasterStudio\Assets\Self\Hardware\LNER A3\Locomotives\Sir Frederick Banbury.blend', '//Sir Frederick Banbury.blend', parent '' # Info Read library: 'D:\RasterStudio\Assets\Self\Hardware\Permanent Way\track.blend', '//..\..\Permanent Way\track.blend', parent '' # Info Read library: 'D:\RasterStudio\Assets\Self\Hardware\General\Metal\metal.blend', '//..\General\Metal\metal.blend', parent 'D:\Crail\Hardware\N2\n2.blend' # Info Read library: 'D:\RasterStudio\Assets\Self\Hardware\General\Dirt\procedural dirt.blend', '//..\General\Dirt\procedural dirt.blend', parent 'D:\RasterStudio\Assets\Self\Hardware\General\Metal\metal.blend' # Info Read library: 'D:\RasterStudio\Assets\Self\Hardware\General\Locomotive Parts\locomotive parts.blend', '//..\..\..\RasterStudio\Assets\Self\Hardware\General\Locomotive Parts\locomotive parts.blend', parent 'D:\Crail\Hardware\N2\n2.blend' # Info Read library: 'D:\RasterStudio\Assets\Self\Hardware\General\Metal\rust.blend', '//..\General\Metal\rust.blend', parent 'D:\RasterStudio\Assets\Self\Hardware\Permanent Way\track.blend' # Info Read library: 'D:\RasterStudio\Assets\Self\Hardware\General\Wood\wood.blend', '//..\General\Wood\wood.blend', parent 'D:\RasterStudio\Assets\Self\Hardware\Permanent Way\track.blend' # Info Read library: 'D:\RasterStudio\Assets\Self\Hardware\General\Material Helpers\Edge Helpers.blend', '//..\Material Helpers\Edge Helpers.blend', parent 'D:\RasterStudio\Assets\Self\Hardware\General\Dirt\procedural dirt.blend' # Info Read library: 'D:\RasterStudio\Assets\Self\Hardware\General\Dirt\bottom up dirt.blend', '//bottom up dirt.blend', parent 'D:\RasterStudio\Assets\Self\Hardware\General\Dirt\procedural dirt.blend' # Info Read library: 'D:\RasterStudio\Assets\Self\Hardware\General\Material Helpers\Color Helpers.blend', '//..\General\Material Helpers\Color Helpers.blend', parent 'D:\RasterStudio\Assets\Self\Hardware\LNER A3\lner_a3_version_2.blend' # Info Read library: 'D:\RasterStudio\Assets\Self\Hardware\LNER A3\lamp.blend', '//lamp.blend', parent 'D:\RasterStudio\Assets\Self\Hardware\LNER A3\lner_a3_version_2.blend' # Info bpy.context.scene.general_settings.enabled = False # Property bpy.context.scene.general_settings.enabled = True # Property # backtrace Exception Record: ExceptionCode : EXCEPTION_ACCESS_VIOLATION Exception Address : 0x00007FF6469443A5 Exception Module : blender.exe Exception Flags : 0x00000000 Exception Parameters : 0x2 Parameters[0] : 0x0000000000000000 Parameters[1] : 0x00000000000000B8 Stack trace: blender.exe :0x00007FF6469443A0 BKE_paint_brush blender.exe :0x00007FF646C219D0 OVERLAY_edit_uv_init blender.exe :0x00007FF646BEAE20 OVERLAY_engine_init blender.exe :0x00007FF646BB1020 drw_engines_init blender.exe :0x00007FF646BAD110 DRW_draw_render_loop_2d_ex blender.exe :0x00007FF64730A330 image_main_region_draw blender.exe :0x00007FF646F39000 ED_region_do_draw blender.exe :0x00007FF646AF2AF0 wm_draw_window_offscreen blender.exe :0x00007FF646AF2940 wm_draw_window blender.exe :0x00007FF646AF2440 wm_draw_update blender.exe :0x00007FF646ACE6A0 WM_main blender.exe :0x00007FF646791C90 main blender.exe :0x00007FF64B572788 __scrt_common_main_seh KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Threads: Thread : 00003a38 ntdll.dll :0x00007FF9E58CCDE0 NtWaitForSingleObject KERNELBASE.dll :0x00007FF9E33E1A00 WaitForSingleObjectEx blender.exe :0x00007FF64AB718E0 IlmThread_2_5::Semaphore::wait blender.exe :0x00007FF64AB710B0 IlmThread_2_5::ThreadPool::numThreads blender.exe :0x00007FF64AB71D50 std::_LaunchPad::operator() blender.exe :0x00007FF64988EED0 std::_LaunchPad >,std::default blender.exe :0x00007FF6496AB090 std::_Pad::_Call_func ucrtbase.dll :0x00007FF9E31D1B20 configthreadlocale KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 00001044 ntdll.dll :0x00007FF9E58D0750 ZwWaitForAlertByThreadId ntdll.dll :0x00007FF9E5893EF0 RtlSleepConditionVariableSRW KERNELBASE.dll :0x00007FF9E342CEC0 SleepConditionVariableSRW MSVCP140.dll :0x00007FF9D4832410 std::_Winerror_message MSVCP140.dll :0x00007FF9D48327A0 Cnd_wait blender.exe :0x00007FF64988E850 ::operator() blender.exe :0x00007FF64988EED0 std::_LaunchPad >,std::default blender.exe :0x00007FF6496AB090 std::_Pad::_Call_func ucrtbase.dll :0x00007FF9E31D1B20 configthreadlocale KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 00001d00 ntdll.dll :0x00007FF9E58D0750 ZwWaitForAlertByThreadId ntdll.dll :0x00007FF9E5893EF0 RtlSleepConditionVariableSRW KERNELBASE.dll :0x00007FF9E342CEC0 SleepConditionVariableSRW MSVCP140.dll :0x00007FF9D4832410 std::_Winerror_message MSVCP140.dll :0x00007FF9D48327A0 Cnd_wait blender.exe :0x00007FF64988E850 ::operator() blender.exe :0x00007FF64988EED0 std::_LaunchPad >,std::default blender.exe :0x00007FF6496AB090 std::_Pad::_Call_func ucrtbase.dll :0x00007FF9E31D1B20 configthreadlocale KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 0000136c ntdll.dll :0x00007FF9E58D0750 ZwWaitForAlertByThreadId ntdll.dll :0x00007FF9E5893EF0 RtlSleepConditionVariableSRW KERNELBASE.dll :0x00007FF9E342CEC0 SleepConditionVariableSRW MSVCP140.dll :0x00007FF9D4832410 std::_Winerror_message MSVCP140.dll :0x00007FF9D48327A0 Cnd_wait blender.exe :0x00007FF64988E850 ::operator() blender.exe :0x00007FF64988EED0 std::_LaunchPad >,std::default blender.exe :0x00007FF6496AB090 std::_Pad::_Call_func ucrtbase.dll :0x00007FF9E31D1B20 configthreadlocale KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 00004c04 ntdll.dll :0x00007FF9E58D0750 ZwWaitForAlertByThreadId ntdll.dll :0x00007FF9E5893EF0 RtlSleepConditionVariableSRW KERNELBASE.dll :0x00007FF9E342CEC0 SleepConditionVariableSRW MSVCP140.dll :0x00007FF9D4832410 std::_Winerror_message MSVCP140.dll :0x00007FF9D48327A0 Cnd_wait blender.exe :0x00007FF64988E850 ::operator() blender.exe :0x00007FF64988EED0 std::_LaunchPad >,std::default blender.exe :0x00007FF6496AB090 std::_Pad::_Call_func ucrtbase.dll :0x00007FF9E31D1B20 configthreadlocale KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 00003194 ntdll.dll :0x00007FF9E58D0750 ZwWaitForAlertByThreadId ntdll.dll :0x00007FF9E5893EF0 RtlSleepConditionVariableSRW KERNELBASE.dll :0x00007FF9E342CEC0 SleepConditionVariableSRW MSVCP140.dll :0x00007FF9D4832410 std::_Winerror_message MSVCP140.dll :0x00007FF9D48327A0 Cnd_wait blender.exe :0x00007FF64988E850 ::operator() blender.exe :0x00007FF64988EED0 std::_LaunchPad >,std::default blender.exe :0x00007FF6496AB090 std::_Pad::_Call_func ucrtbase.dll :0x00007FF9E31D1B20 configthreadlocale KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 00004830 ntdll.dll :0x00007FF9E58D0750 ZwWaitForAlertByThreadId ntdll.dll :0x00007FF9E5893EF0 RtlSleepConditionVariableSRW KERNELBASE.dll :0x00007FF9E342CEC0 SleepConditionVariableSRW MSVCP140.dll :0x00007FF9D4832410 std::_Winerror_message MSVCP140.dll :0x00007FF9D48327A0 Cnd_wait blender.exe :0x00007FF64988E850 ::operator() blender.exe :0x00007FF64988EED0 std::_LaunchPad >,std::default blender.exe :0x00007FF6496AB090 std::_Pad::_Call_func ucrtbase.dll :0x00007FF9E31D1B20 configthreadlocale KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 00003e68 ntdll.dll :0x00007FF9E58D0750 ZwWaitForAlertByThreadId ntdll.dll :0x00007FF9E5893EF0 RtlSleepConditionVariableSRW KERNELBASE.dll :0x00007FF9E342CEC0 SleepConditionVariableSRW MSVCP140.dll :0x00007FF9D4832410 std::_Winerror_message MSVCP140.dll :0x00007FF9D48327A0 Cnd_wait blender.exe :0x00007FF64988E850 ::operator() blender.exe :0x00007FF64988EED0 std::_LaunchPad >,std::default blender.exe :0x00007FF6496AB090 std::_Pad::_Call_func ucrtbase.dll :0x00007FF9E31D1B20 configthreadlocale KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 000017ac ntdll.dll :0x00007FF9E58D0750 ZwWaitForAlertByThreadId ntdll.dll :0x00007FF9E5893EF0 RtlSleepConditionVariableSRW KERNELBASE.dll :0x00007FF9E342CEC0 SleepConditionVariableSRW MSVCP140.dll :0x00007FF9D4832410 std::_Winerror_message MSVCP140.dll :0x00007FF9D48327A0 Cnd_wait blender.exe :0x00007FF64988E850 ::operator() blender.exe :0x00007FF64988EED0 std::_LaunchPad >,std::default blender.exe :0x00007FF6496AB090 std::_Pad::_Call_func ucrtbase.dll :0x00007FF9E31D1B20 configthreadlocale KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 00005120 ntdll.dll :0x00007FF9E58D0750 ZwWaitForAlertByThreadId ntdll.dll :0x00007FF9E5893EF0 RtlSleepConditionVariableSRW KERNELBASE.dll :0x00007FF9E342CEC0 SleepConditionVariableSRW MSVCP140.dll :0x00007FF9D4832410 std::_Winerror_message MSVCP140.dll :0x00007FF9D48327A0 Cnd_wait blender.exe :0x00007FF64988E850 ::operator() blender.exe :0x00007FF64988EED0 std::_LaunchPad >,std::default blender.exe :0x00007FF6496AB090 std::_Pad::_Call_func ucrtbase.dll :0x00007FF9E31D1B20 configthreadlocale KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 00002f7c ntdll.dll :0x00007FF9E58D0750 ZwWaitForAlertByThreadId ntdll.dll :0x00007FF9E5893EF0 RtlSleepConditionVariableSRW KERNELBASE.dll :0x00007FF9E342CEC0 SleepConditionVariableSRW MSVCP140.dll :0x00007FF9D4832410 std::_Winerror_message MSVCP140.dll :0x00007FF9D48327A0 Cnd_wait blender.exe :0x00007FF64988E850 ::operator() blender.exe :0x00007FF64988EED0 std::_LaunchPad >,std::default blender.exe :0x00007FF6496AB090 std::_Pad::_Call_func ucrtbase.dll :0x00007FF9E31D1B20 configthreadlocale KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 00003484 ntdll.dll :0x00007FF9E58D07B0 ZwWaitForWorkViaWorkerFactory ntdll.dll :0x00007FF9E5882680 TpReleaseCleanupGroupMembers KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 00002f18 ntdll.dll :0x00007FF9E58CD8B0 ZwWaitForMultipleObjects KERNELBASE.dll :0x00007FF9E340CA80 WaitForMultipleObjectsEx combase.dll :0x00007FF9E3FB9D50 RoGetServerActivatableClasses combase.dll :0x00007FF9E3FB9D50 RoGetServerActivatableClasses combase.dll :0x00007FF9E3FB9D50 RoGetServerActivatableClasses combase.dll :0x00007FF9E3FB9D50 RoGetServerActivatableClasses KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 00001a34 ntdll.dll :0x00007FF9E58CD8B0 ZwWaitForMultipleObjects KERNELBASE.dll :0x00007FF9E340CA80 WaitForMultipleObjectsEx CRYPT32.dll :0x00007FF9E2F6BB50 CertFreeCTLContext KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 00002704 ntdll.dll :0x00007FF9E58CCDE0 NtWaitForSingleObject KERNELBASE.dll :0x00007FF9E33E1A00 WaitForSingleObjectEx nvwgf2umx.dll :0x00007FF9638D5EA0 OpenAdapter12 nvwgf2umx.dll :0x00007FF9638D5EA0 OpenAdapter12 KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 00001330 ntdll.dll :0x00007FF9E58CCDE0 NtWaitForSingleObject KERNELBASE.dll :0x00007FF9E33E1A00 WaitForSingleObjectEx nvwgf2umx.dll :0x00007FF9638D5EA0 OpenAdapter12 nvwgf2umx.dll :0x00007FF9638D5EA0 OpenAdapter12 KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 00004060 ntdll.dll :0x00007FF9E58CCDE0 NtWaitForSingleObject KERNELBASE.dll :0x00007FF9E33E1A00 WaitForSingleObjectEx nvwgf2umx.dll :0x00007FF9638D5EA0 OpenAdapter12 nvwgf2umx.dll :0x00007FF9638D5EA0 OpenAdapter12 KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 00001e50 ntdll.dll :0x00007FF9E58CCDE0 NtWaitForSingleObject KERNELBASE.dll :0x00007FF9E33E1A00 WaitForSingleObjectEx nvwgf2umx.dll :0x00007FF9638D5EA0 OpenAdapter12 nvwgf2umx.dll :0x00007FF9638D5EA0 OpenAdapter12 KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 00001e58 ntdll.dll :0x00007FF9E58CCDE0 NtWaitForSingleObject KERNELBASE.dll :0x00007FF9E33E1A00 WaitForSingleObjectEx nvwgf2umx.dll :0x00007FF9638D5EA0 OpenAdapter12 nvwgf2umx.dll :0x00007FF9638D5EA0 OpenAdapter12 KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 00002d5c ntdll.dll :0x00007FF9E58CCDE0 NtWaitForSingleObject KERNELBASE.dll :0x00007FF9E33E1A00 WaitForSingleObjectEx nvwgf2umx.dll :0x00007FF9638D5EA0 OpenAdapter12 nvwgf2umx.dll :0x00007FF9638D5EA0 OpenAdapter12 KERNEL32.DLL :0x00007FF9E4A47020 BaseThreadInitThunk ntdll.dll :0x00007FF9E5882630 RtlUserThreadStart Thread : 000009b8 blender.exe :0x00007FF6467C3850 ntreeHasTree blender.exe :0x00007FF64732C100 ED_node_tag_update_nodetree Loaded Modules : 0x00007FF646660000 2.9.3.0 blender.exe C:\Program Files\Blender Foundation\Blender 2.93\blender.pdb 0x00007FF9E5830000 10.0.19041.1288 ntdll.dll 0x00007FF9E4A30000 10.0.19041.1202 KERNEL32.DLL 0x00007FF9E33C0000 10.0.19041.1202 KERNELBASE.dll 0x00007FF9E4280000 10.0.19041.1202 USER32.dll 0x00007FF9E30B0000 10.0.19041.1288 win32u.dll 0x00007FF9E3880000 10.0.19041.1202 GDI32.dll 0x00007FF9DBA00000 2020.2.0.0 tbb.dll 0x00007FF9E36E0000 10.0.19041.1110 gdi32full.dll 0x00007FF9E30E0000 10.0.19041.789 msvcp_win.dll 0x00007FF9E31B0000 10.0.19041.789 ucrtbase.dll 0x00007FF9E4B90000 10.0.19041.1266 SHELL32.dll 0x00007FF9E3690000 10.0.19041.1151 CFGMGR32.dll 0x00007FF9DB8F0000 14.28.29910.0 VCRUNTIME140.dll 0x00007FF9D4820000 14.28.29910.0 MSVCP140.dll 0x00007FF9E4520000 10.0.19041.546 WS2_32.dll 0x00007FF9BBCA0000 8.0.1.0 openvdb.dll 0x00007FF9E3DC0000 10.0.19041.1288 RPCRT4.dll 0x00007FF9B8AC0000 10.0.19041.1081 OPENGL32.dll 0x00007FF97EC90000 3.9.2150.1013 python39.dll 0x00007FF9E52D0000 7.0.19041.546 msvcrt.dll 0x00007FF9E3D10000 10.0.19041.1052 ADVAPI32.dll 0x00007FF9E3EF0000 10.0.19041.1288 combase.dll 0x00007FF9E56C0000 10.0.19041.1202 ole32.dll 0x00007FF9E4AF0000 10.0.19041.906 sechost.dll 0x00007FF9E4510000 10.0.19041.546 PSAPI.DLL 0x00007FF9E5660000 10.0.19041.1023 SHLWAPI.dll 0x00007FF97E450000 58.29.100.0 avformat-58.dll 0x00007FF9DB7A0000 58.8.100.0 avdevice-58.dll 0x00007FF9E3C40000 10.0.19041.985 OLEAUT32.dll 0x00007FF9E4250000 10.0.19041.546 IMM32.dll 0x00007FF968AB0000 58.54.100.0 avcodec-58.dll 0x00007FF9BC8E0000 56.31.100.0 avutil-56.dll 0x00007FF9E3180000 10.0.19041.1023 bcrypt.dll 0x0000000070440000 1.0.28.0 libsndfile-1.dll 0x00007FF9BF9E0000 5.5.100.0 swscale-5.dll 0x00007FF9BB510000 1.20.1.0 OpenAL32.dll 0x000000006ACC0000 libgmp-10.dll 0x00007FF97F310000 2.0.12.0 SDL2.dll 0x00007FF9DC910000 2020.2.0.0 tbbmalloc_proxy.dll 0x00007FF9E4590000 10.0.19041.1237 SETUPAPI.dll 0x00007FF9DBC10000 14.28.29910.0 VCRUNTIME140_1.dll 0x00007FF9CEC20000 6.10.19041.1110 COMCTL32.dll 0x00007FF9DB770000 10.0.19041.1 AVIFIL32.dll 0x00007FF9DCAD0000 10.0.19041.546 VERSION.dll 0x00007FF9BC740000 10.0.19041.1081 GLU32.dll 0x00007FF9DC6F0000 10.0.19041.867 dbghelp.dll 0x00007FF9CAE40000 10.0.19041.546 Secur32.dll 0x0000000070680000 libfftw3-3.dll 0x00007FF9D79D0000 10.0.19041.1 AVICAP32.dll 0x00007FF9D1910000 3.5.100.0 swresample-3.dll 0x00007FF9D8090000 10.0.19041.546 WINMM.dll 0x00007FF9D18D0000 2020.2.0.0 tbbmalloc.dll 0x00007FF9C9180000 10.0.19041.1 MSVFW32.dll 0x00007FF97DAD0000 10.0.19041.1 MSACM32.dll 0x00007FF9D7640000 10.0.19041.1 winmmbase.dll 0x00007FF9E2E40000 10.0.19041.1266 SSPICLI.DLL 0x00007FF9E5370000 10.0.19041.1266 shcore.dll 0x00007FF9E0E10000 10.0.19041.546 kernel.appcore.dll 0x00007FF9E1010000 10.0.19041.1266 windows.storage.dll 0x00007FF9E27F0000 10.0.19041.662 Wldp.dll 0x00007FF9E0930000 10.0.19041.1266 uxtheme.dll 0x00007FF9E37F0000 10.0.19041.1202 bcryptPrimitives.dll 0x00007FF9B3F30000 2.6.7.0 AudioDevProps2.dll 0x00007FF9E2E90000 10.0.19041.844 profapi.dll 0x00007FF9E3B00000 2001.12.10941.16384 clbcatq.dll 0x00007FF9DC1E0000 10.0.19041.1023 MMDevApi.dll 0x00007FF9E2C80000 10.0.19041.1151 DEVOBJ.dll 0x00007FF9DCC70000 10.0.19041.1023 AUDIOSES.DLL 0x00007FF9E2DC0000 10.0.19041.546 powrprof.dll 0x00007FF9E2DA0000 UMPDC.dll 0x00007FF9E3920000 10.0.19041.1202 MSCTF.dll 0x00007FF9B4E10000 10.0.19041.1151 dataexchange.dll 0x00007FF9DF420000 10.0.19041.1266 dcomp.dll 0x00007FF9DE880000 10.0.19041.1202 d3d11.dll 0x00007FF9E1800000 10.0.19041.1266 dxgi.dll 0x00007FF9DDA90000 10.0.19041.964 twinapi.appcore.dll 0x00007FF9DAA80000 10.0.19041.1288 AppXDeploymentClient.dll 0x00007FF966270000 27.21.14.5148 nvoglv64.dll 0x00007FF9E04A0000 10.0.19041.546 WTSAPI32.dll 0x00007FF9E3360000 10.0.19041.1266 WINTRUST.dll 0x00007FF9E2F50000 10.0.19041.1202 CRYPT32.dll 0x00007FF9E2AC0000 10.0.19041.546 MSASN1.dll 0x00007FF9E1C00000 10.0.19041.546 ntmarta.dll 0x00007FF9C6410000 10.0.19041.546 dxcore.dll 0x00007FF9E0C30000 10.0.19041.746 dwmapi.dll 0x00007FF9E2870000 10.0.19041.546 WINSTA.dll 0x00007FF9BD120000 27.21.14.5148 nvldumdx.dll 0x00007FF9DC1A0000 10.0.19041.906 cryptnet.dll 0x00007FF9E2760000 10.0.19041.546 cryptbase.dll 0x00007FF9E4A10000 10.0.19041.546 imagehlp.dll 0x00007FF9E2830000 10.0.19041.546 CRYPTSP.dll 0x00007FF9E1F70000 10.0.19041.1052 rsaenh.dll 0x00007FF963890000 27.21.14.5148 nvwgf2umx.dll 0x00007FF9D9DF0000 27.21.14.5148 nvapi64.dll 0x00007FF9C4950000 27.20.100.8681 igd10iumd64.dll 0x00007FF9E29A0000 10.0.19041.662 ncrypt.dll 0x00007FF9E2960000 10.0.19041.546 NTASN1.dll 0x00007FF9C4710000 27.20.100.8681 igdgmm64.dll 0x00007FF9C1780000 27.20.100.8681 igc64.dll 0x00007FF9C9340000 10.0.19041.1266 textinputframework.dll 0x00007FF9DFBB0000 10.0.19041.746 CoreMessaging.dll 0x00007FF9DF0C0000 10.0.19041.546 CoreUIComponents.dll 0x00007FF9DDF10000 10.0.19041.1202 wintypes.dll 0x00007FF97E200000 1.0.5.10 Wintab32.dll 0x00007FF9D7A80000 10.0.19041.546 MPR.dll 0x00007FF977660000 6.3.42.2 Wacom_Tablet.dll 0x00007FF9B39B0000 10.0.19041.1023 explorerframe.dll 0x00007FF9DFCC0000 7.0.19041.1023 propsys.dll 0x00007FF9DBB90000 3.9.2150.1013 python3.DLL 0x00007FF9DB990000 3.9.2150.1013 _uuid.pyd 0x00007FF9D1D30000 3.9.2150.1013 _hashlib.pyd 0x00007FF978F90000 1.1.1.9 libcrypto-1_1.dll 0x00007FF9D18B0000 3.9.2150.1013 _socket.pyd 0x00007FF9E22E0000 10.0.19041.546 IPHLPAPI.DLL 0x00007FF9DB880000 3.9.2150.1013 select.pyd 0x00007FF9C9150000 3.9.2150.1013 _ssl.pyd 0x00007FF9B6F20000 1.1.1.9 libssl-1_1.dll 0x00007FF9C6470000 3.9.2150.1013 _bz2.pyd 0x00007FF9C46E0000 3.9.2150.1013 _lzma.pyd 0x00007FF97D470000 3.9.2150.1013 unicodedata.pyd 0x00007FF9E25D0000 10.0.19041.546 mswsock.dll 0x00007FF9E2320000 10.0.19041.1266 DNSAPI.dll 0x00007FF9E3C30000 10.0.19041.610 NSI.dll 0x00007FF9DAB80000 10.0.19041.546 rasadhlp.dll 0x00007FF9DA890000 10.0.19041.1266 fwpuclnt.dll 0x00007FF9C46B0000 14.28.29910.0 VCOMP140.DLL
karlisup commented 2 years ago

Thank you @ontogenic for the feedback! Which graphics card are you using? Could you give your hardware specs, please?

ontogenic commented 2 years ago

I can give you more info a little later when back home. One thing I found is that this appears to happen in CPU rendering on cycles more than it does on GPU.

On Sat, Oct 16, 2021, 8:58 AM Karlis Upitis @.***> wrote:

Thank you @ontogenic https://github.com/ontogenic for the feedback! Which graphics card are you using? Could you give your hardware specs, please?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/PhysicalAddons/physical-starlight-and-atmosphere/issues/43#issuecomment-944940407, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOY6RMFEEQP6M7GYYXDOOF3UHGOKTANCNFSM47MZEE7Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

ontogenic commented 2 years ago

GPU: RTX 2060; most recent driver from Nvidia as of 10/16/2021; Intel UHD Graphics 630 CPU: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz 2.60 GHz

I see the crashes both on GPU and CPU mode. I've had to revert to 1.3 as the crashes are pretty consistent now. Let me know what I can do to help debug and resolve the issue.

karlisup commented 2 years ago

Rlguy has a promising blender crash troubleshooting guide. This is an excerpt from it:

  1. The first thing to check is to make sure that the Lock Interface option is enabled. This is a requirement for stable rendering: lock interface Some other things to try:
  2. Restarting your system - sometimes a driver issue can persist until a system restart.
  3. Updating graphics drivers.
  4. Changing render device settings in (Edit > Preferences > System), such as CUDA vs Optix or combinations of CPU/GPU rendering to narrow down what is causing the issue.
  5. Creating and testing a new .blend file to see if the issue can be reproduced with low detail and basic simulation.
  6. How large are the [..] geometry (triangles/vertices count) and how many whitewater particles are being rendered in a typical frame?
karlisup commented 2 years ago

@ontogenic did you / could you try rendering animation beforehand Locking interface, just to confirm if this affects the outcome?

yoyopadser commented 2 years ago

Hi Everyone, I've been having the 1.4x, F12 crashing problem for quite a while, running blender on Linux, all 2.9 versions and after finding the "Lock Interface" suggestion by Karlisup above the problem has disappeared, ta very much for this comment Karlisup:)

terahurts commented 2 years ago

Hi,

I'm also having the F12 crashing problem. I've tried with "Lock Interface" turned on and off and it makes no apparent difference. I've also noticed that when loading a scene that uses the add-on, then turning viewport rending on, that the sun light colour temperature is no-longer adjusting for the elevation. Turning atmosphere off then on fixes the colour temp issues in the viewport but does not fix the crashing issue.

ontogenic commented 2 years ago

I noticed that 1.4.3beta was available for download. Sadly, this issue still happens. Really disappointing when working on a scene to find that it you can no longer continue due to this issue. The plugin is great when / if it works, but is far too buggy to rely on. I can't share my blend file with you, but anything I can do to get this resolved?

hnoerenberg commented 2 years ago

Even with the newest 1.4.4 the F12 bug is still existing. Constantly in Blender 3 (Win & Linux) - B 2.93 also has the problem.

ontogenic commented 2 years ago

@karlisup any chance you could provide an update or ETA for a fix? While I love this add on, it is too disappointing to deal with this issue and so I'll probably need to look elsewhere for a solution if you can't resolve the problem.

karlisup commented 2 years ago

In Discord #help chat willr8 pointed out another workaround that could work out for you: image

Indeed @hnoerenberg, v1.4.4beta just fixed some minor issues with physical values and implemented the aces feature. We have found a version of PSA that doesn't crash by:

For the release, we are adding the support for an asset browser as a replacement for the presets. Also moving stored variables to World scope just breaks some other features that have to be prioritized. Doing our best with our resources to have this done.

SongCast commented 2 years ago

UPDATE: Success! The solution appears to be top menu bar > Render > Lock Interface. Working for me. :)

Same issue here. Physical Starlight And Atmosphere v1.4.4, Blender 3.0, Windows 11.

For some reason, Physical Starlight And Atmosphere seems to become corrupt in a Blender file with the result that when I attempt to render an animation (Ctrl+F12) or a single image (F12), Blender immediately crashes. Crash report attached.

What's weird is that leading up to the consistent crashes, Atmosphere becomes inconsistently unstable, sometimes crashing, sometimes not, without any obvious cause.

As an attempted solution, I uninstalled Atmosphere, including the data stored in \AppData\Roaming\Blender Foundation\Blender\3.0\scripts\presets\physical-addons\psa, then reinstalled it, but that made no difference.

Looking forward to the next update. Thanks.

System Information Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23

Blender Version Broken: version: 3.0.1 Release Candidate, branch: K-CyclesX2, commit date: 2022-01-16 20:48, hash: rB75dde0af07ed Worked: (newest version of Blender that worked as expected)

physical_atmo_1-4-4_render_crash.txt

kinchd commented 2 years ago

I opened up another ticket before seeing this, sorry for the redundancy. Same issue

PS&A v1.4.4, both Blender 3.0.0 & 3.0.1, macOS Monterey 12.1

kinchd commented 2 years ago

update: "Lock Interface" fixed the issue. Thanks @karlisup !

ontogenic commented 2 years ago

Any chance the developers could publish a timeline for fixing this issue? I think there were some improvements in the latest version, but I have scenes now that are back to crashing. I'd prefer to have a committed timeline so I can consider alternatives (to crossing my fingers ;-) Given the price of this addon, I would expect more urgency around fixing such a critical flaw.

hnoerenberg commented 2 years ago

@ontogenic there are some bugs remaining and it does not feel like there would be some development be going on at that time. Yes it's a "beta" but since all values are changing the moment you hit enter right now there seems a lot going on in the scripts. There is also no update on possible solution to render on a farm without missing frames or wrong lighting in some frames. I still don't get it. I went over to use nishita and sun position again. at least it gives consistent results. a reply from the devs would be wonderful.

SongCast commented 2 years ago

@hnoerenberg Regarding render farms, while I have not used a render farm before, I do have a separate PC dedicated to rendering and I have experienced situations where a PSA Blender animation renders fine on my primary PC, but when I send it to my dedicated rendering PC the sun position changes or disappears entirely; I haven't been able to figure out why.

hnoerenberg commented 2 years ago

@SongCast this is exactly the issue. You have to disable the Sun Position Addon (what is totally ok). But generally there is python code executed before and after a frame and this seems to be working not all the time which leads to some frames that are losing information/sun/bounce. The same case if you start blender activate PSA and have a look at the viewport and all the settings, hit render - different images and values have been changed inside the panel (or have been party overwritten or are differently calculated). I can happily sit down with one of the devs and to some beta testing from my side but especially the distributed issues are a complete no-go in a production. TBH there is zero chance to render previs on one machine and manually selecting frames or frame ranges that have been rendered incorrectly is a) time consuming and b) killing deadlines.

karlisup commented 2 years ago

Hi @ontogenic @SongCast and @hnoerenberg, I do really apologize that it took so long to get back to you. I became a dad 6 days ago and it has been a rollercoaster. But that's no reason at all for cutting the communications. The short answer is that we are out of hands and we do try our best to increase our resources, but at the same time keep our tiny company afloat.

Crash fix We managed to produce a version that works. In our discord channel I got 5 people to test the new version out and it gave good results. The downside - it is not stable yet:

Sun position addon

I can happily sit down with one of the devs and to some beta testing from my side

Thank you @hnoerenberg! We do always appreciate help from contributors. We have identified this issue and it has to be tackled, but we have to do this after the major crash bug is addressed.

Render farm bug We need to implement pre / post frame change and look at the location and rotation of the sun in order to create keyframes. It's an extra complex because we allow rotating sun via azimuth/elevation parameters and sun object and Also, this issue will be addressed right after the crash bug is fixed. Here is a dedicated GitHub issue.

Communication I understand that promises don't help with hard deadlines. We'll do better in the future. Meantime, for the latest information and help, I do suggest going to our Discord channel where @adriansnetlis is doing his best to get back to everyone ASAP as unfortunately, information is scattered around too many platforms (GitHub, BlenderArtists, Discord, private 1 on 1s in BlenderMarket, Twitter).

Also in the future, could you keep discussions about other issues under corresponding threads, please? That would help a lot with the organization part. Thank you in advance!

Karlis

ontogenic commented 2 years ago

Hi Karlis - congrats on becoming a father!

swift502 commented 2 years ago

"Render > Lock interface" seems to do the trick for now. 👍

karlisup commented 2 years ago

Hi everyone, PSA version 1.5.0 has been released. Thank you all for your patience! It should fix all Blender crash-related issues. Would like if someone could confirm it before I close this issue.

ontogenic commented 2 years ago

Thanks Karlis. I'll take a look tonight and let you know.

Matt

On Thu, Mar 3, 2022, 3:15 PM Karlis Upitis @.***> wrote:

Hi everyone, PSA version 1.5.0 has been released. Thank you all for your patience! It should fix all Blender crash-related issues. Would like if someone could confirm it before I close this issue.

— Reply to this email directly, view it on GitHub https://github.com/PhysicalAddons/physical-starlight-and-atmosphere/issues/43#issuecomment-1058637865, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOY6RMA77KGJLEMAZHIEHRTU6FBZ7ANCNFSM47MZEE7Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: <PhysicalAddons/physical-starlight-and-atmosphere/issues/43/1058637865@ github.com>

ontogenic commented 2 years ago

I tested out 1.5 on a scene that previously was crashing - it worked.

https://blenderartists.org/t/steam-locomotive-london/1364221/6?u=ontogenic

I'll continue to test.

On Thu, Mar 3, 2022 at 3:15 PM Karlis Upitis @.***> wrote:

Hi everyone, PSA version 1.5.0 has been released. Thank you all for your patience! It should fix all Blender crash-related issues. Would like if someone could confirm it before I close this issue.

— Reply to this email directly, view it on GitHub https://github.com/PhysicalAddons/physical-starlight-and-atmosphere/issues/43#issuecomment-1058637865, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOY6RMA77KGJLEMAZHIEHRTU6FBZ7ANCNFSM47MZEE7Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: <PhysicalAddons/physical-starlight-and-atmosphere/issues/43/1058637865@ github.com>

ontogenic commented 2 years ago

Ok - so I've not experienced any crashes; so far so good. However, I'm now seeing another very frustrating bug - the world / background texture no longer gets updated. I can move the sun around using the plugin controls, but the state of the world is fixed. I've tried uninstalling and reinstalling, but no luck. I also note that the 'reset' button below the sun controls has no effect - I hit reset but all the values stay the same. Finally, I note that when I look at the world material in the node editor, there is one node group which is not connected to anything (called . PSA_sRGBtoAP1).

Still one of my favorite addons, but also the most frustrating! I'm leaving this comment here as these new bugs may have been introduced by the most recent update. Let me know if you want me to create a new issue.

ontogenic commented 2 years ago

I'm seeing now that if I move the sun and then hit reset the world material will catch up to the sun position. The expected behaviours are a) that the world material will stay in synch with the sun and b) that hitting reset will reset the sun information (both the sun light and the world material) to some default setting.

karlisup commented 2 years ago

Hi @ontogenic,

  • I've not experienced any crashes;

I am glad to hear that!

  • The world / background texture no longer gets updated. I can move the sun around using the plugin controls, but the state of the world is fixed. I've tried uninstalling and reinstalling, but no luck.
  • I also note that the 'reset' button below the sun controls has no effect - I hit reset but all the values stay the same.

Do you see any errors in the error console? A restart of The Blender instance should do the trick for both of the issues. If any error occurs, it prevents from rendering the preview. Regarding the restart - we'll consider adding a notice somewhere (in a README or somewhere in the user interface) like discussed in this issue.

  • I note that when I look at the world material in the node editor, there is one node group which is not connected to anything (called . PSA_sRGBtoAP1).

Yes indeed, there are 3 node groups that are not connected to others and one of them is called . PSA_sRGBtoAP1 and that's Ok. This particular node group will be connected to the output if use ACES color space has been enabled in the addon preferences.

  • Let me know if you want me to create a new issue.

Yes, if the issues still persist, please do so as this issue is dedicated to the Blender crash issue.

karlisup commented 2 years ago

After multiple reports, I can finally close this issue. Thank you everyone for taking part and helping to debug it! <3