There is already an industry standard keymap preset available in preferences.
It is useful for the cases when Blender is not used as the main program in pipeline, and workflow assumes lots of switching between different applications.
This tread is about pushing industry standard approach to Blender defaults.
We all know there is an existing industry compatible keymap preset (I would not call it Industry Standard). What I’m talking about is to develop more about it.
For me or many of other users, it doesn’t matter having IC keymap and Blender default keymap co-exist, just like people mentioned above, those use Blender default don’t really care if there is a IC keymap development or not; same for the IC keymap users/ future users, they don’t really care about the Blender default or not.
With that being said, people who prefer stay with Blender default, then stay with the default, just don’t either bother or judge on the IC keymap development. That’s the whole point of it.
Do you know how Blender IC layout was created?
Multiple keymaps was compared.
https://developer.blender.org/T54963
Is it that old so XSI is still available?
Everyone knows there is an IC keymap existed, and the keymap is not welly mapped.
Have you even check how many commands didn’t even got assigned a keys and some important commands were missing though?
Yes I know, but since it is suitable for basic usage when Blender is used as a secondary program, it does not matter much.
IC was never supposed to be powerful, the goal was to design an average keymap, which will be useful for using with the most of industry standards software, and it is assumed that you will complete it accordingly to the software requirements you use with Blender. It is quite logical, since there is a lot if software with different requirements.
Blender defaults, which was originally designed to represent a powerful keymap solution, lost some nice assignments during redesign, and was basically corrupted at the concept level, since some key features of Blender was not even taken into account.
It is not logical, since shrinks the scope of the entire application.
So,
when I, one of the user of Blender, or other people asked for that,
means there is a demand that want the IC keymap improve.
Like what I said,
if you don’t even care you can just leave it alone, don’t even to judge or comment or anything since it’s not affecting you anyway.
Let the people who want it make it happened.
when you said basic usage, secondary application,
what about the people is seek for complete replacement as an primary, advance usage?
I don’t agree on what you said never to be powerful,
so why the Blender default can be powerful but IC can not though?
Same application same functionality same tools same feature,
what’s the point it can’t be?
About the corruption of the binding keys, honestly, in both Blender default or IC keymap, not necessarily every tools or commands need to be keys assigned.
A lot of them pie menu and floating menu can tackle most of these problems already.
Because the original Blender approach is incompatible with IC.
The last time IC was pushed to Blender approach, Blender lost several functional features and got inconsistencies, which is not acceptable.
Anyway, this particular tread is about pushing IC to Blender approach, not about IC enhancement, so you just writing the wrong tread.
Try this one.
Well yeah,
I’m not one of those yelling to replace the entire default keymap with IC keymap,
I think when come to keymapping, it should leave more freedom and harmony to let the users choose what ever they want to use,
therefore, I think co-exist is the best solution on there own track.
I already using it for a long while,
I even make a side by side comparison google sheet with all the function and hotkeys see what’s missing in IC then create a temporary one
You can’t buy it, but a lot of people still use ‘old’ versions because Softimage (XSI) is one of best ‘tools’ there is.
Yes, Vitaliy Bulgarov is one of the most famous XSI user.
Yup. XSI is like Blender + Maya + Houdini in one.
PS. IMHO: XSI’s workflow / approach would be great for Blender. It’s easy, intuitive and logical. You want to unwrap a model? Select a model and apply unwrap. You want subdivide a model? Select a model and press Subdivide. You want to split an edge? Select a model, press ‘Split Edge Tool’ then click where you want to split the edge(s). You want to change ‘common’ parameters of multiple objects, materials, etc.? No problem. You want to change default parameters of all operators? No problem. You want to create a custom button? No problem. Macros? Yes. Custom Menu? Yes. You want to create a custom script and assign it to a custom button on a custom shelve without leaving XSI? Yes, you can do it either.
I think you’ve got the idea.
This sounds like expandability.
XSI has it all. Flexibility, user and artist friendliness, expendability and more important - easy, intuitive and logical workflow and approach to modeling and other things. All of the necessary tools available to you at once. And because you can create custom shelves with custom buttons, you don’t have to remember 2500 keyboard shortcuts like in Blender and all of the modes where those shortcuts used. You just push one button in any ‘mode’ and active the tool you need.
You don’t have to remember shortcuts to learn Blender.
You have to remember shortcuts to outperform competitors on the market.
You have to remember shortcuts to learn Blender. The whole Blender’s pipeline was build around that. At least that’s what some developers has told me.
And no, you don’t have to remember shortcuts to outperform competitors on the market.
How do you know?
Did you tried to challenge Blender approach?
The goal of learning shortcuts is to reach two-handed aproach instead of single-handed one, which is easier to learn, but way slower to use.
It has been already proven for a couple of decades.
So when you learn Blender, you learn the fastest approach right from the begining - that is the point of learning Blender.
Every software has bevel and extrude, in modern graphics era it is important how fast you perform them during deadlines.
It is a certain step in every professional modeller’s evolution - when you stop using GUI in order to bypass GUI speed limitation level and reach physical body speed limitation level.
Perhaps you are exaggerating a bit about the number of keyboard shortcuts one should learn? You can access the features through the menus, pie menus or panels. Also with a couple of keyboard shortcuts you remember you can open important menus where you will find most of the features you will need (In Edit mode for example: Ctrl+V, Ctrl+E, Ctrl+F, W, 1,2,3). In addition, all of them are accessible from the Search feature. And you can personalize them with Quick Favorites.
Perhaps it is true that Blender workflow is based on shortcuts, and it is the reason why many choose Blender. But I don’t think it’s true that you have to learn 2500 shortcuts in order to learn how to use Blender.
The real problem with Blender would be if it didn’t have a good workflow at all. But Blender has it and it is the one based on keyboard shortcuts.
Who would not want Blender to have the many good things that it has, but also to have the best of all the other apps. But realistically, there are no resources to make this possible. There are decisions to be made and in this regard Blender has chosen workflow based shortcuts as its fastest and best method.
