2.8 not starting #59853

Closed
opened 2018-12-25 23:21:46 +01:00 by paperbenni · 17 comments

Blender 2.8 doesn't start. I'm on windows 32 bit, Lenovo IdeaPad miix 300, one of these old 2 in 1 tablets.
With Intel graphics, Intel atom and 2gb ram, it could be that it doesn't meet the requirements. It supports up to OpenGL 4.0 so it shouldn't be a problem.
2.79 and the 2.79 daily builds work fine ("fine")
Either the requirement of OpenGL 3.3 ist false or it's a bug. I've tried yesterday's and today's daily 2.8 build bot build, both show up a terminal without contents for a couple seconds and then close, no error message whatsoever. 2.79 has been proven surprisingly useful on such a weak tablet and it'd be cool to get 2.8 on there since it should technically be supported anyway.

Blender 2.8 doesn't start. I'm on windows 32 bit, Lenovo IdeaPad miix 300, one of these old 2 in 1 tablets. With Intel graphics, Intel atom and 2gb ram, it could be that it doesn't meet the requirements. It supports up to OpenGL 4.0 so it shouldn't be a problem. 2.79 and the 2.79 daily builds work fine ("fine") Either the requirement of OpenGL 3.3 ist false or it's a bug. I've tried yesterday's and today's daily 2.8 build bot build, both show up a terminal without contents for a couple seconds and then close, no error message whatsoever. 2.79 has been proven surprisingly useful on such a weak tablet and it'd be cool to get 2.8 on there since it should technically be supported anyway.
Author

Added subscriber: @paperbenni

Added subscriber: @paperbenni

Added subscriber: @StephenSwaney

Added subscriber: @StephenSwaney

Generic advice:
Run blender from a terminal window so you can see any error messages.
Use updated graphics driver - preferably from your card's manufacturer.

Please mention what version of Windows and your specific graphics card.

Generic advice: Run blender from a terminal window so you can see any error messages. Use updated graphics driver - preferably from your card's manufacturer. Please mention what version of Windows and your specific graphics card.
Author

I did run it from terminal. No output there, just a blank line and then it quits.
blender.exe --help and --version works, so at least it's not completely broken.
I'm on windows 10 home 1803 32 bit
The graphics is intel integrated.
Here is the output of dxdiag, maybe that can help. There's something about blender crashes in there too.
DxDiag.txt

I did run it from terminal. No output there, just a blank line and then it quits. blender.exe --help and --version works, so at least it's not completely broken. I'm on windows 10 home 1803 32 bit The graphics is intel integrated. Here is the output of dxdiag, maybe that can help. There's something about blender crashes in there too. [DxDiag.txt](https://archive.blender.org/developer/F6077677/DxDiag.txt)

Added subscriber: @ChristopherAnderssarian

Added subscriber: @ChristopherAnderssarian

There should be an output from the terminal...

Open Command prompt:

Drag and drop blender.exe and add

--debug

to the end hit enter.

It should look something like this (not the exact filepath):

"C:\Program Files\Blender Foundation\Blender2.8testing\blender.exe" --debug

If that doesn't work then here's a general (paste) list of things to check/do:

Please:

  • Give us your exact Blender, OS and GPU (including drivers) versions, as requested in the template!
  • Ensure both your OS and drivers are fully up-to-date (and use official GPU drivers, not those provided by windows or tablet/laptop maker or open source ones in linux distributions).
    ** If your GPU driver is already to latest version, try down-grading to a few previous versions (sometimes newest versions introduce bugs…).
  • For Windows 7, at least service pack 1 is mandatory, please ensure it is installed on your machine.
  • Try to disable any running antivirus.
  • Try to disable any custom input device (de-install their drivers even), like some graphic tablets, some 3D mice, etc.
  • Try the latest build from our buildbot.
  • Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
  • Try to tweak your GPU driver settings (e.g. try different values between 'performance' and 'quality' if you have such slider, etc.).
  • Launch Blender from the command line with -d option and attach as text file here any error printed out in the console (do not paste it directly in comment).
  • Launch Blender from the command line with --debug-cycles option and attach as text file here any error printed out in the console (do not paste it directly in comment).
  • Launch Blender from the command line with --debug-gpu option and attach as text file here any error printed out in the console (do not paste it directly in comment).
There should be an output from the terminal... Open Command prompt: Drag and drop blender.exe and add ``` --debug ``` to the end hit enter. It should look something like this (not the exact filepath): ``` "C:\Program Files\Blender Foundation\Blender2.8testing\blender.exe" --debug ``` ___ If that doesn't work then here's a general (paste) list of things to check/do: > Please: > * Give us your exact Blender, OS and GPU (including drivers) versions, as requested in the template! > * Ensure both your OS and drivers are fully up-to-date (and use official GPU drivers, not those provided by windows or tablet/laptop maker or open source ones in linux distributions). > ** If your GPU driver is already to latest version, try down-grading to a few previous versions (sometimes newest versions introduce bugs…). > * For Windows 7, at least service pack 1 is mandatory, please ensure it is installed on your machine. > * Try to disable any running antivirus. > * Try to disable any custom input device (de-install their drivers even), like some graphic tablets, some 3D mice, etc. > * Try the latest build from [our buildbot](https://builder.blender.org/download). > * Try to start Blender in factory settings (`--factory-startup` commandline option) (this will ensure whether this is a userpref or addon issue or not). > * Try to tweak your GPU driver settings (e.g. try different values between 'performance' and 'quality' if you have such slider, etc.). > * Launch Blender from the command line with `-d` option and **attach as text file** here any error printed out in the console (**do not** paste it directly in comment). > * Launch Blender from the command line with `--debug-cycles` option and **attach as text file** here any error printed out in the console (**do not** paste it directly in comment). > * Launch Blender from the command line with `--debug-gpu` option and **attach as text file** here any error printed out in the console (**do not** paste it directly in comment).
Author

It started with --debug enabled for some strange reason.

  • debug-gpu and so on did nothing.
    So I tried deleting the 2.8 prefs from the appdata. Didn't work.
    So I went all out and deleted the entire blenderfoundation folder including 2.79 prefs although the 2.8 prefs were already gone.
    And it started without issues. Could there be some permission issues? I thought every app could write to the appdata.
    But here's another issue: The viewport performance and responsiveness was about half of what 2.79 delivers. Is the new viewport just that much slower?! Here is the output of blender.exe -d
    log.txt
It started with --debug enabled for some strange reason. - debug-gpu and so on did nothing. So I tried deleting the 2.8 prefs from the appdata. Didn't work. So I went all out and deleted the entire blenderfoundation folder including 2.79 prefs although the 2.8 prefs were already gone. And it started without issues. Could there be some permission issues? I thought every app could write to the appdata. But here's another issue: The viewport performance and responsiveness was about half of what 2.79 delivers. Is the new viewport just that much slower?! Here is the output of blender.exe -d [log.txt](https://archive.blender.org/developer/F6079261/log.txt)

Added subscriber: @iss

Added subscriber: @iss

I had similar problem on windows 10 64bit, on both 64 and 32bit builds. After deleting userpref.blend file blender started, but it keep failing on exit and load file.

Here is output of start blender then immediately exit:

john@x MINGW64 ~/Desktop/blender-2.80.0-git.e4dbfe0a98c1-windows32
$ ./blender.exe -d --factory-startup
Switching to fully guarded memory allocator.
Blender 2.80 (sub 39)
Build: 26/12/2018 16:16 Windows Release
argv[0] = C:\Users\john\Desktop\blender-2.80.0-git.e4dbfe0a98c1-windows32\blender.exe
argv[1] = -d
argv[2] = --factory-startup
read file
  Version 280 sub 24 date unknown hash unknown
AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead
found bundled python: C:\Users\john\Desktop\blender-2.80.0-git.e4dbfe0a98c1-windows32\2.80\python
Saved session recovery to 'C:\Users\john\AppData\Local\Temp\quit.blend'
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x3F800000

In debugger I saw fail on free studiolights

Here is output of start blender, save file, open saved file.

john@x MINGW64 ~/Desktop/blender-2.80.0-git.e4dbfe0a98c1-windows32
$ ./blender.exe -d --factory-startup
Switching to fully guarded memory allocator.
Blender 2.80 (sub 39)
Build: 26/12/2018 16:16 Windows Release
argv[0] = C:\Users\john\Desktop\blender-2.80.0-git.e4dbfe0a98c1-windows32\blender.exe
argv[1] = -d
argv[2] = --factory-startup
read file
  Version 280 sub 24 date unknown hash unknown
AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead
found bundled python: C:\Users\john\Desktop\blender-2.80.0-git.e4dbfe0a98c1-windows32\2.80\python
Info: Total files 0 | Changed 0 | Failed 0
Read blend: C:\Users\john\Desktop\vid\xxx.blend
read file C:\Users\john\Desktop\vid\xxx.blend
  Version 280 sub 39 date 2018-12-26 22:09 hash e4dbfe0a98c1
Memoryblock reconstruct: end corrupt
I had similar problem on windows 10 64bit, on both 64 and 32bit builds. After deleting userpref.blend file blender started, but it keep failing on exit and load file. Here is output of start blender then immediately exit: ``` john@x MINGW64 ~/Desktop/blender-2.80.0-git.e4dbfe0a98c1-windows32 $ ./blender.exe -d --factory-startup Switching to fully guarded memory allocator. Blender 2.80 (sub 39) Build: 26/12/2018 16:16 Windows Release argv[0] = C:\Users\john\Desktop\blender-2.80.0-git.e4dbfe0a98c1-windows32\blender.exe argv[1] = -d argv[2] = --factory-startup read file Version 280 sub 24 date unknown hash unknown AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead found bundled python: C:\Users\john\Desktop\blender-2.80.0-git.e4dbfe0a98c1-windows32\2.80\python Saved session recovery to 'C:\Users\john\AppData\Local\Temp\quit.blend' Error : EXCEPTION_ACCESS_VIOLATION Address : 0x3F800000 ``` In debugger I saw fail on free studiolights Here is output of start blender, save file, open saved file. ``` john@x MINGW64 ~/Desktop/blender-2.80.0-git.e4dbfe0a98c1-windows32 $ ./blender.exe -d --factory-startup Switching to fully guarded memory allocator. Blender 2.80 (sub 39) Build: 26/12/2018 16:16 Windows Release argv[0] = C:\Users\john\Desktop\blender-2.80.0-git.e4dbfe0a98c1-windows32\blender.exe argv[1] = -d argv[2] = --factory-startup read file Version 280 sub 24 date unknown hash unknown AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead found bundled python: C:\Users\john\Desktop\blender-2.80.0-git.e4dbfe0a98c1-windows32\2.80\python Info: Total files 0 | Changed 0 | Failed 0 Read blend: C:\Users\john\Desktop\vid\xxx.blend read file C:\Users\john\Desktop\vid\xxx.blend Version 280 sub 39 date 2018-12-26 22:09 hash e4dbfe0a98c1 Memoryblock reconstruct: end corrupt ```

I can add stack trace...

for first case

 	3f800000()	Unknown
 	[Frames below may be incorrect and/or missing]	
>	blender.exe!studiolight_free(StudioLight * sl=0x0b67bee0) Line 143	C

 	blender.exe!BKE_studiolight_free() Line 1248	C
 	blender.exe!BKE_blender_free() Line 90	C
 	blender.exe!WM_exit_ext(bContext * C=0x007e07f8, const bool do_python=true) Line 520	C
 	blender.exe!WM_exit(bContext * C=0x007e07f8) Line 613	C
 	blender.exe!wm_exit_handler(bContext * C=0x007e07f8, const wmEvent * event=0x0d0ac780, void * userdata=0x00000000) Line 405	C
 	blender.exe!wm_handler_ui_call(bContext * C=0x007e07f8, wmEventHandler * handler=0x0d164e28, const wmEvent * event=0x0d0ac780, int always_pass=0) Line 573	C
 	blender.exe!wm_handlers_do_intern(bContext * C=0x007e07f8, wmEvent * event=0x0d0ac780, ListBase * handlers=0x0b7607c8) Line 2374	C
 	blender.exe!wm_handlers_do(bContext * C=0x007e07f8, wmEvent * event=0x0d0ac780, ListBase * handlers=0x0b7607c8) Line 2607	C
 	blender.exe!wm_event_do_handlers(bContext * C=0x007e07f8) Line 2997	C
 	blender.exe!WM_main(bContext * C=0x007e07f8) Line 427	C
 	blender.exe!main(int argc=3, const unsigned char * * UNUSED_argv_c=0x007ef018) Line 521	C
 	blender.exe!invoke_main() Line 78	C++
 	blender.exe!__scrt_common_main_seh() Line 283	C++
 	blender.exe!__scrt_common_main() Line 326	C++
 	blender.exe!mainCRTStartup() Line 17	C++

for second case

>	blender.exe!issue_debug_notification(const wchar_t * const message=0x07326fd4) Line 28	C++

 	blender.exe!__acrt_report_runtime_error(const wchar_t * message=0x07326fd4) Line 154	C++
 	blender.exe!abort() Line 51	C++
 	blender.exe!MemorY_ErroR(const unsigned char * block=0x085a6bac, const unsigned char * error=0x0859d658) Line 1079	C
 	blender.exe!MEM_guarded_freeN(void * vmemh=0x0b8bf360) Line 965	C
 	blender.exe!BKE_libblock_free_ex(Main * bmain=0x0b846380, void * idv=0x0b8bf360, const bool do_id_user=false, const bool do_ui_user=false) Line 943	C
 	blender.exe!BKE_main_free(Main * mainvar=0x0b846380) Line 76	C
 	blender.exe!BKE_blender_globals_clear() Line 149	C
 	blender.exe!setup_app_data(bContext * C=0x09241340, BlendFileData * bfd=0x2157e6b8, const unsigned char * filepath=0x0075f138, const bool is_startup=false, ReportList * reports=0x0ef48760) Line 239	C
 	blender.exe!BKE_blendfile_read(bContext * C=0x09241340, const unsigned char * filepath=0x0075f138, const BlendFileReadParams * params=0x0075f0d4, ReportList * reports=0x0ef48760) Line 404	C
 	blender.exe!WM_file_read(bContext * C=0x09241340, const unsigned char * filepath=0x0075f138, ReportList * reports=0x0ef48760) Line 601	C
 	blender.exe!wm_file_read_opwrap(bContext * C=0x09241340, const unsigned char * filepath=0x0075f138, ReportList * reports=0x0ef48760, const bool autoexec_init=true) Line 1864	C
 	blender.exe!wm_open_mainfile_exec(bContext * C=0x09241340, wmOperator * op=0x0ee9d630) Line 1924	C
 	blender.exe!wm_handler_fileselect_do(bContext * C=0x09241340, ListBase * handlers=0x0b846b50, wmEventHandler * handler=0x0e00bd20, int val=2) Line 2168	C
 	blender.exe!wm_handler_fileselect_call(bContext * C=0x09241340, ListBase * handlers=0x0b846b50, wmEventHandler * handler=0x0e00bd20, const wmEvent * event=0x0e584728) Line 2255	C
 	blender.exe!wm_handlers_do_intern(bContext * C=0x09241340, wmEvent * event=0x0e584728, ListBase * handlers=0x0b846b50) Line 2380	C
 	blender.exe!wm_handlers_do(bContext * C=0x09241340, wmEvent * event=0x0e584728, ListBase * handlers=0x0b846b50) Line 2607	C
 	blender.exe!wm_event_do_handlers(bContext * C=0x09241340) Line 2997	C
 	blender.exe!WM_main(bContext * C=0x09241340) Line 427	C
 	blender.exe!main(int argc=4, const unsigned char * * UNUSED_argv_c=0x092502e0) Line 521	C
 	blender.exe!invoke_main() Line 78	C++
 	blender.exe!__scrt_common_main_seh() Line 283	C++
 	blender.exe!__scrt_common_main() Line 326	C++
 	blender.exe!mainCRTStartup() Line 17	C++

on line

blender.exe!BKE_libblock_free_ex(Main * bmain=0x0b846380, void * idv=0x0b8bf360, const bool do_id_user=false, const bool do_ui_user=false) Line 943	C

id was

id->name = "MECube"
id->us = 1

all other fields were NULL

I can add stack trace... for first case ``` 3f800000() Unknown [Frames below may be incorrect and/or missing] > blender.exe!studiolight_free(StudioLight * sl=0x0b67bee0) Line 143 C blender.exe!BKE_studiolight_free() Line 1248 C blender.exe!BKE_blender_free() Line 90 C blender.exe!WM_exit_ext(bContext * C=0x007e07f8, const bool do_python=true) Line 520 C blender.exe!WM_exit(bContext * C=0x007e07f8) Line 613 C blender.exe!wm_exit_handler(bContext * C=0x007e07f8, const wmEvent * event=0x0d0ac780, void * userdata=0x00000000) Line 405 C blender.exe!wm_handler_ui_call(bContext * C=0x007e07f8, wmEventHandler * handler=0x0d164e28, const wmEvent * event=0x0d0ac780, int always_pass=0) Line 573 C blender.exe!wm_handlers_do_intern(bContext * C=0x007e07f8, wmEvent * event=0x0d0ac780, ListBase * handlers=0x0b7607c8) Line 2374 C blender.exe!wm_handlers_do(bContext * C=0x007e07f8, wmEvent * event=0x0d0ac780, ListBase * handlers=0x0b7607c8) Line 2607 C blender.exe!wm_event_do_handlers(bContext * C=0x007e07f8) Line 2997 C blender.exe!WM_main(bContext * C=0x007e07f8) Line 427 C blender.exe!main(int argc=3, const unsigned char * * UNUSED_argv_c=0x007ef018) Line 521 C blender.exe!invoke_main() Line 78 C++ blender.exe!__scrt_common_main_seh() Line 283 C++ blender.exe!__scrt_common_main() Line 326 C++ blender.exe!mainCRTStartup() Line 17 C++ ``` for second case ``` > blender.exe!issue_debug_notification(const wchar_t * const message=0x07326fd4) Line 28 C++ blender.exe!__acrt_report_runtime_error(const wchar_t * message=0x07326fd4) Line 154 C++ blender.exe!abort() Line 51 C++ blender.exe!MemorY_ErroR(const unsigned char * block=0x085a6bac, const unsigned char * error=0x0859d658) Line 1079 C blender.exe!MEM_guarded_freeN(void * vmemh=0x0b8bf360) Line 965 C blender.exe!BKE_libblock_free_ex(Main * bmain=0x0b846380, void * idv=0x0b8bf360, const bool do_id_user=false, const bool do_ui_user=false) Line 943 C blender.exe!BKE_main_free(Main * mainvar=0x0b846380) Line 76 C blender.exe!BKE_blender_globals_clear() Line 149 C blender.exe!setup_app_data(bContext * C=0x09241340, BlendFileData * bfd=0x2157e6b8, const unsigned char * filepath=0x0075f138, const bool is_startup=false, ReportList * reports=0x0ef48760) Line 239 C blender.exe!BKE_blendfile_read(bContext * C=0x09241340, const unsigned char * filepath=0x0075f138, const BlendFileReadParams * params=0x0075f0d4, ReportList * reports=0x0ef48760) Line 404 C blender.exe!WM_file_read(bContext * C=0x09241340, const unsigned char * filepath=0x0075f138, ReportList * reports=0x0ef48760) Line 601 C blender.exe!wm_file_read_opwrap(bContext * C=0x09241340, const unsigned char * filepath=0x0075f138, ReportList * reports=0x0ef48760, const bool autoexec_init=true) Line 1864 C blender.exe!wm_open_mainfile_exec(bContext * C=0x09241340, wmOperator * op=0x0ee9d630) Line 1924 C blender.exe!wm_handler_fileselect_do(bContext * C=0x09241340, ListBase * handlers=0x0b846b50, wmEventHandler * handler=0x0e00bd20, int val=2) Line 2168 C blender.exe!wm_handler_fileselect_call(bContext * C=0x09241340, ListBase * handlers=0x0b846b50, wmEventHandler * handler=0x0e00bd20, const wmEvent * event=0x0e584728) Line 2255 C blender.exe!wm_handlers_do_intern(bContext * C=0x09241340, wmEvent * event=0x0e584728, ListBase * handlers=0x0b846b50) Line 2380 C blender.exe!wm_handlers_do(bContext * C=0x09241340, wmEvent * event=0x0e584728, ListBase * handlers=0x0b846b50) Line 2607 C blender.exe!wm_event_do_handlers(bContext * C=0x09241340) Line 2997 C blender.exe!WM_main(bContext * C=0x09241340) Line 427 C blender.exe!main(int argc=4, const unsigned char * * UNUSED_argv_c=0x092502e0) Line 521 C blender.exe!invoke_main() Line 78 C++ blender.exe!__scrt_common_main_seh() Line 283 C++ blender.exe!__scrt_common_main() Line 326 C++ blender.exe!mainCRTStartup() Line 17 C++ ``` on line ``` blender.exe!BKE_libblock_free_ex(Main * bmain=0x0b846380, void * idv=0x0b8bf360, const bool do_id_user=false, const bool do_ui_user=false) Line 943 C ``` id was ``` id->name = "MECube" id->us = 1 ``` all other fields were NULL

Added subscriber: @brecht

Added subscriber: @brecht

@paperbenni, can you attach the output of Help > System Info in Blender 2.79?

It's not clear to me that this graphics card does fully support OpenGL 3.3. When it was released it only supported only 3.2, while OpenGL was already at 4.4 at the time. Maybe it got added later in the driver, but it's odd.

@iss, that seems like a different bug.

@paperbenni, can you attach the output of Help > System Info in Blender 2.79? It's not clear to me that this graphics card does fully support OpenGL 3.3. When it was released it only supported only 3.2, while OpenGL was already at 4.4 at the time. Maybe it got added later in the driver, but it's odd. @iss, that seems like a different bug.
Author

system-info.txt
There it is.
Opengl extensions viewer also shows opengl 4.0

[system-info.txt](https://archive.blender.org/developer/F6084956/system-info.txt) There it is. Opengl extensions viewer also shows opengl 4.0
Author

I really hope it is unable to use OpenGL for some reason, otherwise this is deeply concerning. Should I open another bug report or is 2.8 just half as fast as 2.79?!

I really hope it is unable to use OpenGL for some reason, otherwise this is deeply concerning. Should I open another bug report or is 2.8 just half as fast as 2.79?!

Blender 2.8 is optimized for modern GPUs, this system will likely soon be below our minimum requirements. 32 bit support will likely be dropped soon as well. So we're unlikely to invest time optimizing for this system, and would not handle poor performance on this system as a bug.

Blender 2.8 is optimized for modern GPUs, this system will likely soon be below our minimum requirements. 32 bit support will likely be dropped soon as well. So we're unlikely to invest time optimizing for this system, and would not handle poor performance on this system as a bug.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brecht Van Lommel self-assigned this 2019-01-04 18:14:40 +01:00

I missed that removing the old settings seems to solve the crash. So I'm not sure there is anything remaining here that we can fix.

I missed that removing the old settings seems to solve the crash. So I'm not sure there is anything remaining here that we can fix.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
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#59853
No description provided.