the AccentGrave (') is not accessible on a german-keyboard-layout to be used as a shortcut.. it's hidden behind Shift+# and in the place were the AccentGrave sits on an US-Layout, the german-layout has a degree sign (°)
Feb 14 2019
May 26 2018
I can reproduce this behavior but the Undo (Ctrl+Z) has nothing to do with it. The same happens when leaving Edit-Mode and entering it again after the insertion of the loop-cuts (to any flat surface). It's as if the Mirror-Modifier has an own option of "draw all edges" that's always turned on but only updates when the object updates as well. This is a bit confusing, but to workaround it for now just turn on the show_on_cage option of the Mirror-Modifier. Then you can see all the geometry on both sides.
this is probably to be expected ( Please correct me if I'm mistaken. ).
May 13 2018
@Philipp Oeser (lichtwerk) : Sorry - Yes, I just tested it with the 2.79b-official release where it works fine. And I didn't know I was allowed to just assign confirmed bugs to someone - I guess always to the relevant module owner, right? Thanks for pointing all this out!
@Erick Tukuniata (erickblender) : I'm sorry - I used the offical blender 2.79b to test this - I will keep in mind to always check with the latest master in the future. So yes with the current master build I can reproduce the bug as described. Sorry again! But with @Philipp Oeser (lichtwerk) the bug report is in good hands ;)
It doesn't crash for me - but if I switch to smoke+fire the scene freezes for a fraction of a second and in the console the following is printed:
I guess what you are referring to is that the changes/ color transformations of the color space/ exposure/ etc. in the properties editor - scene settings are not applied to the background image(s) set in the 3D-View.
I don't know if that is desired behavior, but I agree it seems like a bug. I guess the color transformation specified in the scene settings should apply to all areas of blender. I will thus confirm this as a bug for now, but invite others to clarify.
May 12 2018
I can reproduce this behavior here. Trying to set the group for all empties from within the object properties panel doesn't work via Alt-LMB. It works by pressing RMB+'copy to selected'-operator though. So even if this does not work via Alt-LMB, there is a really simple workaround, so that I guess it is not a bug of very high priority, but I let others decide this.
Hi @Cristian Delgadillo (pujols.cmt) ,
Please add more information as to what exactly it is that does not work for you.
build-hashes used that all worked fine within my Linux setup:
Hi @Erick Tukuniata (erickblender) ,
I can not reproduce this crash nor any artifacts with my setup (Fedora 28/ GeForce GT 740), even when I previously make the mesh non-manifold.
It works fine here for 2.79a, 2.79b and latest master build of the 2.79series.
So maybe it is something specific to your setup. You probably tested this already with blender's factory-settings loaded, right? Do you have the latest nvidia drivers installed?
May 10 2018
Sorry but that is not enough information you provided here.
It could be that your objects are on other layers. Or that your clipping plane cuts them off. But I'm almost sure this is not a bug.
Look in the outliner - if your objects are still in there then they are still in your file.
This side is specifically for bugs/development only, but you can always get more help at sites like: https://blender.stackexchange.com/
Hope you find a solution. For now I'm going to assume this is not a bug and close this task as invalid.
@andrew (karribu) : I'm glad you found a solution to work for you.
So I guess we can assume this is not a blender bug and close this task as invalid.
May 9 2018
I can reproduce this behavior using the operator in the Edge-Special menu. Although checking 'loop pairs'-option does yield a slightly different result than the other options, it can't really be considered the desired result.
If that is a feature you urgently need however, you can already use the add-on "loop-tools" that ships with blender. This produces the expected result.
I tested an intuos 3 in 2.79 texture painting. And it works fine for me (Fedora 28 with "wayland" disabled/ GeForce GT 740).
@Philipp Oeser (lichtwerk) : your work here is really aprecciated - thanks again for taking the time to fix this issue so soon!
May 8 2018
*wow* - getting back from work to find the bug I reported yesterday to be already fixed for 2.79. Thank you so much @Philipp Oeser (lichtwerk)! Regarding my other bug report: T54397 , do you think I should CC a 2.8-developers directly as the surface-deform modifier isn't ported over to 2.8 yet or would that be considered annoying/ unhelpful? I don't know the policy here and I don't want to clutter their chat with unimportant messages. Thanks again for your time and effort!
May 7 2018
Mar 22 2018
Just saw that "Shapekeys" of a target mesh have no effect in combination with the "Surface Deform"-modifier as well. This modifier really seems to overwrite any other transforms..
the attached file seems to be missing - sorry if I double-post it..