@Brecht Van Lommel (brecht) who to assign this to?
Tue, Dec 4
Mon, Dec 3
FYI - this is tested fixed on intel driver version 22.214.171.12499, 10/11/2018
Sun, Dec 2
Sat, Dec 1
Rebased on latest blender2.8.
If it says reading preferences, it might be crashing due to some old preferences or startup file that was saved. They are in this folder:
Confirmed, Build 2.80 Beta, 0f5b53ba4dc, 2018-11-30 22:29 works as expected. Thanks
This is fixed in the very latest build.
Fri, Nov 30
Installing Wintab_x64_126.96.36.199 driver solved the issue for me as well on Surface Laptop just now. Thanks @Daniel Lara (Pepeland) (pepeland)
Thu, Nov 29
Yes, I use Blender in surface book 2 with same issue and after instaling Wintab_x64_188.8.131.52 driver the pressure works (yay!) but Blender have some
problems manage this kind of pen devices, like this one https://developer.blender.org/T55589 the problem is that pen event is not received for the first movements of the pen and only after a while.
this task appear closed but still happening.
@Daniel Lara (Pepeland) (pepeland) iirc, you are using a surface tablet with Blender? are you aware of anything special about that topic?
I can reproduce the bug on 27cccaeccd2 with --threads 1 option.
Could reproduce here with only one basis shape key.
Just a shot in the dark:
Does this also happen when blender is called from the commandline with the --threads 1 option?
Wed, Nov 28
Related to this is T58075, which crashes under the same conditions (only one shape key, or one or more nonzero shape keys) when switching from edit mode to vertex paint mode.
I was able to confirm this on windows 10 x64 2018-11-28 hash 4c6e7ef11f3
Mon, Nov 26
Sun, Nov 25
Which is one of the reasons i picked sentry unlike other solutions in this space, it's opensource and you can run it on your own servers.
I hope that Blender Foundation eventually does not rely on Sentry.Io or any other 3rd party entity when it comes this functionalty. This is all how it starts, first you want to know aboutt he crashes, then you want to know what was leading to the crash, then how the user interacts with Blender, then you want everyone to have an account with Blender to use it etc etc. Not saying there are such intentions but feature creeps happen all the time.
Thu, Nov 22
Hm, OK seems there was indeed a reason for something I removed (blush -- see rB0f4064c66ff8).
[running vertex connect with a single vertex was not on the radar...]
Will correct shortly.
I'm still seeing this on the latest version, try selecting this vertex before running Vertex Connect
More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.
Cannot reproduce crash here either, on Linux debian64…
Wed, Nov 21
Tue, Nov 20
Same with me, tested all the options available. Nothing worked
Mon, Nov 19
Blender 2.79b was opening on Monitor 4 every time, after doing the workaround:
Fri, Nov 16
Someone here on windows that can debug this?
Thu, Nov 15
Seems to be something wrong with Vega 64 (and newest divers?), there are other (more specific issues reported, see e.g. T57832)
Nov 2 2018
That may well be, but i'm not gonna change a legal text on my own without explicit instructions to do so.
It is actually correct to be GPL3, from https://www.blender.org/about/license/
I can change it into whatever, but i'm gonna need some guidance from @Ton Roosendaal (ton) what he wants