raumafu
Hi,
will these updates come to your patreon as well?

Yes it will be available in a new post soon.

Hi, thank you for the quick update

I have some issue when trying to create nodes by using the multi-selection menu (for example in SOP, press H then C to create groupcombine node), the menu would show up but cant seem to create the node. Down below are error message from houdini console:



Traceback (most recent call last):

File "C:\Users/xxxx/Documents/houdini21.0/animatrix/hotkey system/python3.11libs\utility_hotkey_system.py", line 125, in keyPressEvent

if shortcut == (event.key() | event.modifiers()):

~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~

File "C:\PROGRA~2/Steam/STEAMA~1/common/HOUDIN~1/python311/lib/site-packages-forced\PySide6\support\deprecated.py", line 54, in func_or

return QtCore.QKeyCombination(self, other)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

TypeError: 'PySide6.QtCore.QKeyCombination.__init__' called with wrong argument types:

PySide6.QtCore.QKeyCombination.__init__(KeyboardModifier, int)

Supported signatures:

PySide6.QtCore.QKeyCombination.__init__(Union)

PySide6.QtCore.QKeyCombination.__init__(PySide6.QtCore.Qt.Key = Instance(Qt.Key_unknown))

PySide6.QtCore.QKeyCombination.__init__(PySide6.QtCore.Qt.KeyboardModifier, PySide6.QtCore.Qt.Key = Instance(Qt.Key_unknown))

PySide6.QtCore.QKeyCombination.__init__(PySide6.QtCore.Qt.Modifier, PySide6.QtCore.Qt.Key)

Cedric4826
Hi, thank you for the quick update

I have some issue when trying to create nodes by using the multi-selection menu (for example in SOP, press H then C to create groupcombine node), the menu would show up but cant seem to create the node. Down below are error message from houdini console:



Traceback (most recent call last):

File "C:\Users/xxxx/Documents/houdini21.0/animatrix/hotkey system/python3.11libs\utility_hotkey_system.py", line 125, in keyPressEvent

if shortcut == (event.key() | event.modifiers()):

~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~

File "C:\PROGRA~2/Steam/STEAMA~1/common/HOUDIN~1/python311/lib/site-packages-forced\PySide6\support\deprecated.py", line 54, in func_or

return QtCore.QKeyCombination(self, other)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

TypeError: 'PySide6.QtCore.QKeyCombination.__init__' called with wrong argument types:

PySide6.QtCore.QKeyCombination.__init__(KeyboardModifier, int)

Supported signatures:

PySide6.QtCore.QKeyCombination.__init__(Union)

PySide6.QtCore.QKeyCombination.__init__(PySide6.QtCore.Qt.Key = Instance(Qt.Key_unknown))

PySide6.QtCore.QKeyCombination.__init__(PySide6.QtCore.Qt.KeyboardModifier, PySide6.QtCore.Qt.Key = Instance(Qt.Key_unknown))

PySide6.QtCore.QKeyCombination.__init__(PySide6.QtCore.Qt.Modifier, PySide6.QtCore.Qt.Key)

Hi,

I fixed that bug now.

Great update! Everything works except fn:displaySelectNearestNode(uievent, context) option. I have bounded to my 1 key and remove every other hotkeys in the hotkey editor but it does not seem to work. The other options are working like 2 3 4 but not display one. How can i fix it?

raumafu
Great update! Everything works except fn:displaySelectNearestNode(uievent, context) option. I have bounded to my 1 key and remove every other hotkeys in the hotkey editor but it does not seem to work. The other options are working like 2 3 4 but not display one. How can i fix it?

You can use the selectDisplayNearestNodeInEditorEnhanced function in utility_generic.

@animatrix
In the utility_ui I use "toggle Headlight normal light" in 20.5 alot.
Do you know how it has to be changed to work with H21 Work Lights?


Cheers
CYTE

Hi,

This should work:


The other types are listed here:

hou.viewportWorkLight.Headlight:
Single over-the-shoulder distant light.

hou.viewportWorkLight.Domelight:
Environment light with optional texture map.

hou.viewportWorkLight.PhysicalSky:
Outdoor lighting with a distant and environment map based on the sun position and atmospheric conditions.

hou.viewportWorkLight.ThreePoint:
Three distant lights set up in a classic three point lighting arrangement.

Thanks, man,

You are the best!
I was hoping to toggle between these two.
WorkLight or Scene Light.
Is that possible, too?

CYTE
Thanks, man,

You are the best!
I was hoping to toggle between these two.
WorkLight or Scene Light.
Is that possible, too?

I think that's not possible because there is always some work light mode available. There is no off option. Even if the toolbar shows off, the work light still reports the current one used.

Bought addon on gumroad. It seems to work, but it gives me claustrophobia like vim. There is no documentation, no videos on how anything work(some videos in this page is not available anymore) some hotkeys don't work(I use ODTOOLS, maybe that's the reason). Spent half an hour looking how to move the houdini from one monitor to another. Terrible experience, I'm sorry, but it's not fine for 100bucks addon. At least spend 20 minutes writing a readme with some explanation on how it works. I'm in the middle of the project, and now would have to waist even more time cleaning up the installation.
I'm not gonna demand my money back or write bad review, but come on

Hi,

Yes I heard some users had some hotkey conflicts with odtools. Videos were deleted by vimeo. I plan to make a new one as they were outdated also.

You can watch this video for some of the workflow (from 32:00 or so):



There is also some documentation inside HOUDINI_USER_PREF/animatrix/hotkey system/nodegraphhooks.py.

As for moving Houdini from one monitor to another, there is no such action built-in. But if you are in fullscreen mode, simple exit fullscreen, move the application and then toggle fullscreen again. I could probably make some action about it but Qt fullscreen has some issues on some systems i.e. when using Intel drivers, etc.

As for clean up, just remove the json files from the packages folder somewhere else, and nothing should load up on start up.

Ok, I spent some time with it, it's definitely a good product, but it's very aggressive on the user, changes so much and so drastically. And seems like it doesn't work correctly for me and I don't know if it's incorrect installation, or clashing with different addons, because there is no wide example of it working correctly. For example in network editor when I click shift+RMB I got empty radial menu end a console with "{}". F3 in scene view send me error "Cannot find the tool toggleViewportFlatSmoothShaded.", same goes for most of the F-keys, but not all of them, F5 for "display points" works, but in documentation part of the "\animatrix\hotkey system\python3.11libs\nodegraphhooks.py" it says the command for F5 is "Toggle Prim Numbers" and in "hotkeys.csv" the line for F5 is "op:attribcopy|fn:toMatrix3OrFloat(uievent)|op:sopvectorfield". So was the command changed after the documentation or is it not registered for me because wrong installation? What F5 does for anybody else who uses supercharged?
There are also a lot of errors with working on overlay network, for example sometimes it loads with tabs hidden, and sometimes with shown but collapsed. Reloading "DASH_SingleMonitor" gives error and can be fixed only with restarting Houdini. Here is an error.
Traceback (most recent call last):
File "C:\Users/3dlog/Documents/houdini21.0/animatrix/overlay network editor/python3.11libs\utility_overlay_network_editor.py", line 101, in updateUIElements
overlayNetworkEditorPassThrough = hasattr(hou.session, "overlayNE") and isPassThroughEnabled(hou.session.overlayNE)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users/3dlog/Documents/houdini21.0/animatrix/overlay network editor/python3.11libs\utility_overlay_network_editor.py", line 368, in isPassThroughEnabled
bool(window.windowFlags() & QtCore.Qt.WindowTransparentForInput) or
^^^^^^^^^^^^^^^^^^^^
RuntimeError: Internal C++ object (PySide6.QtWidgets.QWidget) already deleted.
I actually don't find overlay workflow very useful right now, I have big monitor and like working with different network views, is there a way to remove all the network overlay features and only keep hotkeys and network navigation? Selecting nodes that are closest to mouse is so good I got hooked in a minute and it's enough reason to not give up figuring out how to work with this beast of an addon.

Hi,

1. There is no Shift+RMB combo. I just tried it, it zooms as default. So it's possible other add-ons you are using might be causing this override.

Houdini itself is not really designed to have multiple add-ons that override the same mechanisms, i.e. AFAIK you can't have multiple packages each overriding nodegraphhooks.py. I am not familiar with DASH but @probiner would know more.

There is override for Alt+RMB on nodes for example.

2. F3 shows Toggle Point Numbers on my build. It's possible the last build updated is not the latest. I will push a new update to sync to latest.

3. F5 is correct. It's "Toggle Prim Numbers".

4. - "hotkeys.csv" the line for F5 is "op:attribcopy|fn:toMatrix3OrFloat(uievent)|op:sopvectorfield". So was the command changed after the documentation or is it not registered for me because wrong installation? What F5 does for anybody else who uses supercharged?

hotkeys.csv is only for the network editor. The other hotkeys you mentioned for function keys are listed under "=== Scene View Hotkeys ===". They are defined by the supercharged.shelf.

5. - There are also a lot of errors with working on overlay network, for example sometimes it loads with tabs hidden, and sometimes with shown but collapsed.

That should be based on the full screen state. In fullscreen everything is collapsed, i.e. stowbars.

6. For DASH_SingleMonitor I have to see what it is doing. Where did you download that? @probiner might know more why it happens because it happens when you use that action. Do you get the same error with other desktops? I have to try this.

7. To keep only context-sensitive rule-based hotkeys, you can rename or delete HOUDINI_USER_PREF/animatrix/overlay network editor/python3.11libs/pythonrc.py

That's the code that initialized the overlay network editor. There are some people who use the hotkey system alone, since they are independent systems.

1. Ok. I tested more, deleted all configs and started from scratch, something become more clear. Shift+RMBclick behaves this way in default houdini installation, with no addons present including Recharged.
2. After installing Recharged on top of clean houdini configs folder(didn't reinstall houdini, just renamed houdini21.0 directory in documents, and run the app, maybe there are some leftover configs elsewhere). The errors on most of the F-number keys are still there.
3. F5 is still toggles "Display points"
4. The other hotkeys you mentioned for function keys are listed under "=== Scene View Hotkeys ===". They are defined by the supercharged.shelf.
I don't understand what it means, there is no "scene view hotkeys" in shelf or "houdini21.0\animatrix\hotkey system\toolbar\supercharge.shelf" file. Don't know where else to look.
5. Tabs are useful sometimes, it'll be nice to have them and overlay viewport.
6. About DASH-singlemonitor desktop - my mistake, that desktop loaded by default, I thought it's a part of Supercharged.
7. That worked, thank you

2-3. I pushed a new update just now. Please try this build.

4. Sorry I mean if you look inside HOUDINI_USER_PREF/animatrix/hotkey system/nodegraphhooks.py, alot of hotkeys are listed there including "=== Scene View Hotkeys ===" so those should be the ones in the code.

5. That behaviour is defined inside HOUDINI_USER_PREF/animatrix/generic/python3.11libs/utility_ui.py


These lines have to be removed or commented out like this #comment.

It's possible this could be exposed as a setting in the pythonrc.py of hotkey system folder.

6. DASH is created by @probiner.

7. No worries.

1. Made experiments while working on a project and didn't notice right away that 456.py inside the addon overrides 456.bat, the only thing I got there is "autosave on", so I lost an hour of work because of that. If somebody else missing this you can change "animatrix/generic/scripts/456.py" to
Or maybe there is some better solution? Because every update of the recharge would demand fixing it and it's easy to miss.
2. After cleen install I still got a lot of errors. I tried to figure out on the example of "F3" key. It gives me error for "toggleViewportFlatSmoothShaded", can't find it. Google can't find it, search through houdini configs with installed recharged find it in one place only - animatrix/hotkey system/Houdini.keymap2. It's line 8942 "action":"h.pane.gview.tool:toggleViewportFlatSmoothShaded" assigning it to F3 key. So, I don't know what this is, maybe it's from another package or addon? Can't figure it out.

1. Yes unfortunately Houdini is not designed to have multiple 123 and 456 files. There is no way to aggregate them. I might have to change the approach to get rid of these files like using callbacks. I have to look into this.

2. That's strange, I see the same toggleViewportFlatSmoothShaded inside the file you mentioned twice but not in the hotkey editor. I have to investigate this but you can try removing it from the hotkey editor. It's supposed to be Shift+F3 like in my screenshot. Houdini's new hotkey system is WIP so I don't know if there is a bug there. I have to ask SideFX for more information.



Another thing you can check is if you have Houdini.keymap2.overrides inside your HOUDINI_USER_DIR. Because then that will override others AFAIK. In my case I see it, and it seems to remove the keys for the action you listed, so that likely overrides the F3 hotkey in the plugin.

In any case those shading actions need to be revised because it's missing the functions because they were overhauled. I have to look into it because I stopped using those.

Currently the function keys toggle point/prim numbers/normals, etc.

animatrix_
t. Houdini's new hotkey system is WIP so I don't know if there is a bug there. I have to ask SideFX for more information.

I'll look into it a bit more tomorrow, but seems unlikely that I'll get some overrides in HOUDINI_USER_DIR, since I deleted it, recreated with starting houdini, checked that it's clean(no personal configs were present), then installed recharged and got errors on hitting F3.
May I suggest just putting "autosave on" as default? Don't see any downsides from it, and see plenty downsides on forgetting to put it on after updating addon.
Also, may I suggest creating a radial menu for for viewport toggles like displaying markers/points/wires(since none of those keys are mouse position dependent). Maybe use F1-F5 as quickmarks since those are close to original shortcuts, so there are some muscle memory over those for most users but it's not overly desired ergonomic-real-estate-wise keys like 1-5.
Also, is there a way to assign-reassign creating nodes in network views? For example I use polyextrude and polybevel all the time, but seems like they aren't in any hotkeys. Maybe they are hidden in some menu like primitives menu on "P"? Is there a way to search for this? I'll probably figure out how to reassign keys myself if it's possible, but it'll make it a chore to fix every time I'll need to upgrade.
I feel like a nag, but I want to reiterate that addon is amazing, I'm going to use it, it's worth the money, all my problems are lies in the desire to figure out how it works.

All of these hotkeys can be customized. For example if you don't like the default hotkeys, you can remove them using the hotkey editor. But for the network editor hotkeys, you need to edit the hotkeys.csv yourself using a text editor.

The syntax is documented inside nodegraphhooks.py.

So you can assign hotkeys for polyextrude and polybevel there. When you upgrade, you wouldn't lose your hotkeys if you keep your hotkeys.csv and your own overrides files.