Ah, okay, my apologies. I misread that as the usual request of dragging and clicking the mouse to enable box selection.

In T56702#544572, @William Reynish (billreynish) wrote:

@Sebastian M Roy (sebastianmroy): Nice idea with the selection icons.

As for only dragging when you are over an object, that is not how Blender works, and probably isn't a very good idea for handling complex 3D scenes. You may be working in wireframe, you may have many tiny objects, or objects with holes, or thin, long objects. It would be very fiddly for most things if you had to drag on top of the thing you want to move. One of the nice things is that you can drag wherever you want

Maybe others can chime in here, but I've used Blender in left-click select mode with left-click drag enabling box select for years and I can't think of a single time this was an issue.

This is shaping up to be an excellent revamp of the default key map.

@Duarte Farrajota Ramos (duarteframos) You mean "This is shaping up to be an excellent industry standard key map", right? The default Blender standard key map is another task altogether.

@William Reynish (billreynish) I mean is this task open to discussions on how to improve the pie menu in general, or meant only to discuss the specific items you outlined in the Description above?

Is this task meant for improvements in general to the pie menu, or just these specific proposed changes?

Hi, @lucas veber (lucky3), thanks for the response.

I just wanted to say I like the first horizontal design a lot, especially with the strip of templates with quick visual representation of the different modes. It actually stirs in me the the desire to want to get into the program and work/explore, which is a huge plus.

In keeping with the "workflow" mentality, would it be possible to get a context-based deletion behavior by default when pressing "x"? Like the Smart Delete addon.

Just a quick question: Is there a plan to make the Favorites Bar optionally a floating panel?

I just saw the new update video from @venomgfx . Kudos on all the update efforts to have a coherent and useful default keymap. I may not agree with all the changes, but I think it's a worthwhile pursuit.

@Ludvik Koutny (rawalanche) It looks like context-sensitive menu is being developed as a whole anyways for 2.8 according to T55162.

It would be great once you select an object in the scene, the object get's always highlighted in the hierarchy of the outliner. So far you can only see a selected object that is in a collection or parented to another object if it's one of the first few icons in the list:

Just so options are considered.

I use quick layer changing a lot more often than mode change, so making the number change modes isn't ideal for me, and presume would be true for a lot of Blender users as well.

I agree. Context-sensitive right-click menus I think should be a given for industry standard keymap.

@William Reynish (billreynish) The Curve Extrusion tool looks very intuitive, and far superior to what Maya has.

@William Reynish (billreynish) In Maya, the spacebar, aside from toggling the quad view, it also shows a layout of menu items while held down:

Just want to say this is a really smart move. Also, the decision to integrate pie menu to be default in Blender in general is very welcome, too.

Not sure for the scope of this task, but I agree, Blender should allow for a more robust expression system.

YES, much needed. I actively avoid drivers because they're so cumbersome to setup. I'm really curious about what "Open Driver Editor" will open.

@William Reynish (billreynish) Actually, you're right, it's pretty much the same behavior. I think my main thing is when scaling individually extruded faces, it'd be more useful to have them scale on their individual origins by default temporarily.

@William Reynish (billreynish) For #3, Maybe this helps more: https://youtu.be/aKwE_tzV7l8?t=238. It looks like it's a mirrored operation, but it's not.

This is great! I have a few suggestions for extrusions that I think would be really helpful:

@William Reynish (billreynish) Appreciate you taking the time to respond. I hope my suggestions are not derailing the purpose of this task. I got excited at the notion of making the 3D Cursor more powerful, but I think the real goal here is to make it feel more refined and less disruptive, and not adding more features.

I love the idea of expanding the 3D Cursor to be more powerful.

Hi, @Sergey Sharybin (sergey). The forum discussion is just to contextualize my problem, but reading it is not necessary to replicate the problem in this report.

I can confirm that something has changed from 2.78 to 2.79. I have a custom keymap and have this exact same problem.

Thanks, @ronan ducluzeau (zeauro), I appreciate the feedback.

Thanks for the quick reply, @ronan ducluzeau (zeauro).

Running into this issue again. Could this be possibly be fixed with the new depsgraph or something?

Oh, forgot to respond to this. The exporting itself works just fine for me.

There should be as I've also confirmed this with a co-worker.

Ah, sorry, it was late, haha. Here's the file:

For when you get around to it:

In case it helps, just wanted to add on that thing that seems apparent to me in my tests is that exporting .fbx out of Blender bakes the animation as if basically all the options for Bake Action are checked.
Whereas, when importing the .blend into Unity straight, the baked animation is as if only the "Only Selected" option is checked (which, in this case, seems to be the desired setting).

Thanks for the suggestions, @Bastien Montagne (mont29). I tried changing the Simplify value to different values (including 0), as well as the Sampling Rate just in case, but nothing seems to help. =/

Right, but this doesn't look like one of them. Problem also replicated by co-worker. I'd appreciate it if somebody could look into this.

Ah, actually, it looks like baking within Blender works if only "Only Selected" option is on. (While testing, I somehow came to the conclusion that all the options needed to be checked.)

Yes, but neither exporting to .fbx to Unity nor baking the animation in Blender works corectly. Did it work for you in 2.78c?

Right, though I think it should be noted that, while this may not be a bug, this behavior is fixed by enabling the new depsgraph. Maybe that could be useful. Thanks, Sergey!

@ronan ducluzeau (zeauro) Thanks, that worked like a charm! I'm actually a little disappointed that I didn't think of that myself.

I'm still bumping up against this problem. Are there plans to remedy this limitation in 2.8? Even if it breaks older rigs, I'd be glad to have this limitation removed going forward.

I tried reimporting the .fbx to Blender, and as you said, it works fine. Then I tried importing it into Sketchfab and also Unreal Engine and the animations all work fine in those as well.

Oh, and just in case it's needed, before I change the items in the hierarchy, this is the structure as it imports into Unity by default from the .fbx exported out of Blender:

I tried it but it's still shifting. =/

Oopse, forgot to attach the file:

Hi, Ivan. I appreciate you taking the time to recreating the metarig.
Yes, I did originally make some modifications to the ORG-bones on my rig. I guess I wrongly assumed the z-axis should be facing up..

Oh, wow, nice, it worked! The snipet resolves the issue for me.

Thanks for looking into this. I could think of one thing that possibly could've affected the animation data.

Ah, okay, in retrospect, I realize I should've included the .blend file.

Ah, I apologize, really sorry for wasting your time!

I'm not sure if this would be covered in the scope of this task, but would it be possible to register drag direction as positive?

Well, that's embarrassing.. I thought I checked for that when doing the tests. Sorry for wasting your time, but thanks for checking it out!

Oopse, you're right. My apologies for lying. Just tested on 2.76 and 2.73.
I guess when I was testing this out last night, I accidentally did it for the armature instead of the bone in the other versions, haha.

I'll do you one better than a .blend. Show and tell: