For those of you interested in ways to set this up:
My personal setup uses two different sets of hotkeys, this is within the modal transforms, there are now additional operators (introduced in 2.91 & 2.92). I use shift to constrain to mouse axis movement and tab for planes, for consistency across softwares. These work just like middle mouse button. Unfortunately, precision transform (default keymap = shift) cannot be mapped to different buttons due to a bug (T85383).
Anyway, under “Transform modal map” in the hotkeys (there are redundant F5/6/7 keys for compliance with Max’ hotkeys):
Set a key (that does not invoke another function on its own) in conjuction with another key/ mouse action (e.g. right/ middle clicking) that way you could also opt to change modes.
I will try to create video, the idea is not really complicated, but can be confusing in text.
(I’m going to have to cover all the tools though, so it becomes a complicated video to make “simple” ;D )
@Kiellog
Hi,
just found that your “Context Extrude” is automatically choose axis without MMB clicking
Is it intendant change? Can it be as earlier, default blender edge extrude with MMB to choose direction?
Good news / Bad news:
Good:
-There are some cool new features in the next update (EXR sync viewport and render)
I finally got around to fixing the “clean” installation process. No more error spam when installing (you still have to restart, probably)
Bad:
I realized why the enums for various tools were not saved(when re-installing) - this only works if you export your keyconfig, and then re-import it. This will force the enums to be set, otherwise they go to default.
This is not ideal.
I have reworked the Transform Tool Toggle modes into unique operators, which eliminates the problem. And you have to clean out your old hotkeys and set the new ones.(note: just as a test, not in .410)
To avoid this being an issue in the future, I would have to do this to ALL the operators relying on Enum options for shortcuts (when re-installing) if you ARE importing keyconfigs, you will have remove that file from your user-preset folder to avoid clashing. Which you probably are using, and dont want to do. You will probably have to remove old hotkeys in prefs, set the new ones, and export keyconfig and re-import. You don’t want to do that whole procedure unless migrating to a different blender release.
So…fun times ahead! hey, it’s only…half of the tools. Well, the export-reimport trick should work…
EDIT: Hmm, I dont think it is managable, there would be -many times- as many operators. like hundreds.
Export-Import is prob the way to go.
EDIT2:
This will be the recommended procedure for installation:
Clean install - the usual zip install
Update - Just overwrite the add-on folder manually.
Migration (or if you must uninstall/remove the add-on for whatever reason: export/import keyconfigs)
OK, no major changes to the entire kit. Just the update instructions
Please read!
v1.410 is up! (I should do a video on BG sync, at some point)
EDIT: now v1.411, minor update. (panel reads v1.411b)
EDIT2: now up to .413 with minor updates
EDIT3: …and .414
Just discovered RenderVisible script. Both this one and BG Sync are really nice features!
Regarding rendering. In Modo when we press the render button it automatically selects next render slot. Kjell, is it possible to create similar in Blender? Now we have to manually change a render slot. And if we forget to do so F12 overwrites the existed one.
Got it working, was pretty trivial after I spent an hour debugging…a typo.
reg slot count: the script will handle any amount of slots available. @Antony
you can add extra slots and save in your startupfile for default. Dont forget to set slot 1 as active tho!
It looks like Frame All or Selected doesn’t work at UV and Shader Editors(probably with some other like Compositor, Timeline/Graph etc.)
Kjell, is it possible to improve the tool?
yes, adding to the to-do list
edit: Investigated, it will become a new operator, needs more general context. not super hard but will take some time, maybe not in the next release Hmm. i might release it anyway, v0.1 will only support viewport tho.
(also, Noticed there was a bug/error in frame all in object mode…whoops(fix in next)