- User Since
- Sep 30 2015, 4:08 AM (124 w, 5 d)
Jan 3 2018
Single press is global as expected and usual with everything else. But I'd like to have the selected transform option be the one used for the double press. Some other operations respect it in this way, but for some stupid reason extrude doesn't. If I switch to select another face that I want to extrude on the custom transform, then I have to go back to the transforms menu and select the custom edge. It's tedious and creating an extra step that shouldn't be there. Again if I wanted the secondary constraint to be based on normal transform axes, I would have picked that from the menu. (So there shouldn't be any problem with fixing this flaw in the UI. It feels like an inconsistency.)
Yeah found that eventually after plugging away some more. Would be nice if there was a way to make being in local mode more obvious at times. (Looking at the one corner doesn't always come to mind. Like border color at the window, or even better - perhaps an "exit local" button that shows where the layers button usually is.) Seems individual objects can remain local if you switch out of them while editing. So this change in state can still hit a bit by surprise when going between different ones where you weren't in local space. Sorry about the freak-out though, although I'd guess I'm not the only one.
Dec 31 2017
Nov 12 2017
Can confirm as another user. Having the same exact problem with the latest Blender-Edge (via Thomas Sheix PPA) release on Linux Mint 17.3.
Sep 14 2017
I'm hoping it gets fixed in 2.79, because for whatever reason 2.8 is worse. Only gray screen there with the Intel chipset on the laptop, no bueno. :(
Sep 9 2017
Sep 2 2017
Aug 27 2017
Aug 25 2017
Seems to happen with the (still official?) version 2.78c. Oddly enough it didn't happen with the previous repository version of the 2.78 series. (I think that's where the old defaults were being pulled from.) Then it seems to be fixed in the 2.79-rc2-linux-glibc-x86-64 version, but is a problem with the 2.79.x PPA.
Aug 24 2017
Tried running it in debug mode...
Seems that the default scene was broken. Messed around a bit, and replaced it with the default scene from 2.78. No crash.
May 1 2017
Mar 17 2017
Apr 25 2016
I tried running "blender -softwaregl" from the terminal as you asked.
Apr 23 2016
Added system info as recorded by blender 2.76b under Mint 17.3 Rosa (Cinnamon) 64-bit.
Apr 21 2016
I'm hoping a video is acceptable for explaining and documenting the situation. I tried to include stuff which I'd think may be relevant. A quick run-through of other programs to show they display the alpha grid ok along with precedent for established expectations. (Not sure if they're using the same method, but that it's working. I don't think too much is broken or out of the ordinary with my setup.) Thus this problem seems to be in Blender. Yet within Blender itself, the transparency grid shows in the compositing node. The scene itself is a default scene, which hasn't been changed from the initial install.
Apr 17 2016
Dec 27 2015
Oct 2 2015
I suppose this may help. It was something quick I was messing with when having the particle-related crash and left at that stage. Reloading works, but may crash if changing around the particle settings.