- User Since
- Mar 24 2014, 1:16 AM (285 w, 6 d)
Jun 16 2019
Jun 8 2019
Apr 28 2019
I can confirm this in a recent build of commit 9e3246ce6e9767148e4394dc7acbec04a7d69163.
Apr 24 2019
You're right. It is only "Toggle Fullscreen Area" missing.
I don't know what I was looking at, yesterday. But I have to double-check such things in the future.
Apr 23 2019
OK, figured it out. No Blender-related issue, sorry.
It was a bloody MIDI-Synthesizer (was loaded by the web browser for no good reason) that used Ctrl-Alt-Space as "panic" button. Case closed.
I checked it on another Win10 machine and the shortcut worked there (partially).
I have to check it later on the other Win7 machine, whether the locale or another application is interfering.
Apr 22 2019
I tested it with the stated version (build date: 2019-04-17), as well as with a self-compiled version from master branch (last commit 22.4.2019 @ 15:10 / 7d6a9b551759cf3f1cca0c6d8ecb1459d02dcc28).
Apr 13 2019
Feb 4 2016
Jan 29 2016
While --enable-new-depsgraph seems to avoid the crash, it seems to erase the driver on the object instead (tested on the posted file). Maybe topic for a new ticket?
@Sergey Sharybin (sergey) Could a workaround be to catch at least the error (the code is in C++ ?) with try/catch and an error message as console ouptput to avoid the hard crash of Blender?
Jan 28 2016
I am not exactly a Blender developer. But I would like to ask you for them whether you could provide some more information about this incident. Otherwise, the bug will be closed by an admin very quickly as „invalid“.
Please try the following:
Apr 17 2015
Apr 5 2014
Weight paint seems to be the reason of the crash.
If the weight value of all vertices is 0.0 no crash occurrs.
Please see attached files where weight paint is cleared.