Blender 2.82 - Default key map - No Set Origin hotkey #71127

New Issue

Carlo Andreacchio · 2019-10-27T01:05:41+02:00

Carlo Andreacchio commented

2019-10-27 01:05:41 +02:00

System Information
Operating system: Ubuntu 19.04
Graphics card: GTX 1080

Blender Version
Broken: 2a3b5dc730
Worked: cac3e16cfb

Short description of error
There is no set origin hotkey for the blender 2.82 default keymap

Exact steps for others to reproduce the error

Open blender 2.82
set keymap to 2.7x
press control shift alt c
notice how you can set the origin
set keymap to default keymap
try the same key combination
notice how it doesnt set it
look in the preferences to see what it is and notice how it is not there.

**System Information** Operating system: Ubuntu 19.04 Graphics card: GTX 1080 **Blender Version** Broken: 2a3b5dc730 Worked: cac3e16cfb **Short description of error** There is no set origin hotkey for the blender 2.82 default keymap **Exact steps for others to reproduce the error** 1. Open blender 2.82 2. set keymap to 2.7x 3. press control shift alt c 4. notice how you can set the origin 5. set keymap to default keymap 6. try the same key combination 7. notice how it doesnt set it 8. look in the preferences to see what it is and notice how it is not there.

Carlo Andreacchio commented

2019-10-27 01:05:41 +02:00

Added subscriber: @candreacchio

Stanislav Blinov commented

2019-10-27 17:15:39 +01:00

Added subscriber: @Stan_Pancakes

Stanislav Blinov commented

2019-10-27 17:15:39 +01:00

Should it be there is the question though. Different keymap - different keys.

Carlo Andreacchio commented

2019-10-27 22:11:40 +01:00

Yes. It is imperative as a hotkey for fast efficient (hotkey dominated) workflows.

Carlo Andreacchio commented

2019-10-27 22:50:34 +01:00

I shoudl add, that this is for a archviz / hard surface modelling workflow. Not a animation based workflow.

Stanislav Blinov commented

2019-10-27 23:20:38 +01:00

That specific default hotkey was neither fast or efficient, but that's beside the point. This is not a bug: different keymaps exist to have different, uh, key mappings. That's their purpose. Choose one you like, and build on it by assigning your own hotkeys. Furthermore, with the 2.81+ origin transforms, you may well find that those operators lost quite a bit of their use. But if you don't, assigning your own is the way to go.

Carlo Andreacchio commented

2019-10-27 23:43:17 +01:00

Just breaking down your response into multiple responses:

That specific default hotkey was neither fast or efficient

It was pretty efficient in that we could set specific points to be the at the 3d Cursor, that we have specifically placed at a certain point. Using transform origins, does not allow us to snap the origins to a speciifc point in space. (shift s - snap to cursor). Our normal workflow is having the lefthand on the keyboard and the right hand ont he mouse. ctrl alt shift c is a lefthand only keyboard command which allows the flow of modelling not to be effected. I am not attached to this specific key command, more the underlying command.

This is not a bug: different keymaps exist to have different, uh, key mappings.

I agree, it is not a bug, but it something that is needed for a complete key mapping. There are a few of these that are still outstanding from the 2.8 changes, and I am trying to help the developers realise what is needed for all workflows.

Choose one you like, and build on it by assigning your own hotkeys.

I know I can make my own hotkeys, but it should be part of the standard, ... I dont mind what it is, but it should be one. When we hire new artists, they usually spend a few days prepping with blender before starting with us. They inevidenably use the default hotkeys. Making sure that the default hotkeys is up to industry standards is what I am trying to do.

Just breaking down your response into multiple responses: > That specific default hotkey was neither fast or efficient It was pretty efficient in that we could set specific points to be the at the 3d Cursor, that we have specifically placed at a certain point. Using transform origins, does not allow us to snap the origins to a speciifc point in space. (shift s - snap to cursor). Our normal workflow is having the lefthand on the keyboard and the right hand ont he mouse. ctrl alt shift c is a lefthand only keyboard command which allows the flow of modelling not to be effected. I am not attached to this specific key command, more the underlying command. > This is not a bug: different keymaps exist to have different, uh, key mappings. I agree, it is not a bug, but it something that is needed for a complete key mapping. There are a few of these that are still outstanding from the 2.8 changes, and I am trying to help the developers realise what is needed for all workflows. > Choose one you like, and build on it by assigning your own hotkeys. I know I can make my own hotkeys, but it should be part of the standard, ... I dont mind what it is, but it should be one. When we hire new artists, they usually spend a few days prepping with blender before starting with us. They inevidenably use the default hotkeys. Making sure that the default hotkeys is up to industry standards is what I am trying to do.

Stanislav Blinov commented

2019-10-28 02:45:03 +01:00

Just to point a couple of things out, though this discussion is probably better suited for rightclickselect than here:

With 2.80, you have "Set Origin" in the right click context menu. Speaking of hotkeys, that's right-click 3, 3 to snap origin to cursor. A finger from each hand, instead of 4 fingers from one. Three finger motions instead of five. Blazing fast.
Snapping origin to cursor, immensely useful up to, and including 2.80, becomes much less so. Because now instead of using the cursor as a middle man, first snapping it somewhere, and then setting origin, you can just snap the origin directly, using all the available snapping tools. This approach does come short in a few places where desired position is not related to any particular geometry and has to be preset, but these are hardly the norm. "Specifically placed at a certain point" usually means moving origin to some face or vertex though. Which you can now do directly. With long-existing multi-snapping, and the new additional edge snapping options. With aligning orientation when needed. Without having to do disrupt your work just to make a selection to snap the cursor somewhere.

In any case, how useful that hotkey is as a default is subjective, especially given the expanded alternatives in newer Blender versions. I'm not sure how one would derive any "industry standards" here. Old habits die hard, I know. I doubt anyone would lose sleep over having that hotkey in there by default, but my point remains that its usefulness is just not as great as it once was.

Just to point a couple of things out, though this discussion is probably better suited for rightclickselect than here: - With 2.80, you have "Set Origin" in the right click context menu. Speaking of hotkeys, that's right-click 3, 3 to snap origin to cursor. A finger from each hand, instead of 4 fingers from one. Three finger motions instead of five. Blazing fast. - Snapping origin to cursor, immensely useful up to, and including 2.80, becomes much less so. Because now instead of using the cursor as a middle man, first snapping it somewhere, and then setting origin, you can just snap the origin directly, using all the available snapping tools. This approach does come short in a few places where desired position is not related to any particular geometry and has to be preset, but these are hardly the norm. "Specifically placed at a certain point" usually means moving origin to some face or vertex though. Which you can now do directly. With long-existing multi-snapping, and the new additional edge snapping options. With aligning orientation when needed. Without having to do disrupt your work just to make a selection to snap the cursor somewhere. In any case, how useful that hotkey is as a **default** is subjective, especially given the expanded alternatives in newer Blender versions. I'm not sure how one would derive any "industry standards" here. Old habits die hard, I know. I doubt anyone would lose sleep over having that hotkey in there by default, but my point remains that its usefulness is just not as great as it once was.

Campbell Barton commented

2019-11-01 02:15:56 +01:00

Added subscriber: @ideasman42

Campbell Barton commented

2019-11-01 02:15:56 +01:00

Changed status from 'Open' to: 'Archived'

Campbell Barton closed this issue

2019-11-01 02:15:56 +01:00

Campbell Barton self-assigned this 2019-11-01 02:15:56 +01:00

Campbell Barton commented

2019-11-01 02:15:56 +01:00

This was removed intentionally #55666 (Minimal Keymap Proposal).

With right click select W,O or RMB,O can access this menu.

This was removed intentionally #55666 (Minimal Keymap Proposal). With right click select `W,O` or `RMB,O` can access this menu.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender 2.82 - Default key map - No Set Origin hotkey #71127