Describe the bug
Unable to publish playblast with shot
To Reproduce
Publish a shot from blender with "preview" (playblast) option
Errors on preview creation
Expected behavior
Create preview
DCC
Please complete the following information:
- Dcc name(s): Blender
- Dcc Version(s) 4.3.2
Desktop (please complete the following information):
Additional context
OpenGL Render written to 'C:\Users\G513\TM4_default\tikDatabase\shots\test_shot\Layout\blender\publish\thumbnails\test_shot_Layout_test_layout_v001.jpg'
ERROR:tik_manager4:03/09/25 - 13:25 - ERROR : Preview generation failed: Region not found in area or screen
Traceback (most recent call last):
File "C:\Program Files\TikWorks\tik_manager4\objects\publisher.py", line 274, in publish
preview_abs_path = self._generate_preview(preview_context, message_callback)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Program Files\TikWorks\tik_manager4\objects\publisher.py", line 313, in _generate_preview
return preview_handler.generate(show_after=False)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Program Files\TikWorks\tik_manager4\objects\preview.py", line 200, in generate
abs_path = self.database_obj.dcc_handler.generate_preview(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Program Files\TikWorks\tik_manager4\dcc\blender\utils.py", line 73, in _keepfunc
raise e
File "C:\Program Files\TikWorks\tik_manager4\dcc\blender\utils.py", line 70, in _keepfunc
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "C:\Program Files\TikWorks\tik_manager4\dcc\blender\main.py", line 248, in generate_preview
with bpy.context.temp_override(**context):
TypeError: Region not found in area or screen
Seems to be a context issue again, like in #264
Describe the bug
Unable to publish playblast with shot
To Reproduce
Publish a shot from blender with "preview" (playblast) option
Errors on preview creation
Expected behavior
Create preview
DCC
Please complete the following information:
Desktop (please complete the following information):
Additional context
Seems to be a context issue again, like in #264