exitsimulation
Hi I just bought this plug-in! I am missing a bit of guidance and documentation to be honest.

Is it possible to toggle (hide) the network overlay other than by holding space? Like just moving around freely in the viewport without the overlay, how would I do this with supercharge enabled?

Thanks!

animatrix_

exitsimulation
Hi I just bought this plug-in! I am missing a bit of guidance and documentation to be honest.

Is it possible to toggle (hide) the network overlay other than by holding space? Like just moving around freely in the viewport without the overlay, how would I do this with supercharge enabled?

Thanks!

To toggle the overlay network editor, the default hotkey is ` (backtick). Space is configured for the volatile toggle to temporarily hide the overlay network editor.

exitsimulation

animatrix_

exitsimulation
Hi I just bought this plug-in! I am missing a bit of guidance and documentation to be honest.

Is it possible to toggle (hide) the network overlay other than by holding space? Like just moving around freely in the viewport without the overlay, how would I do this with supercharge enabled?

Thanks!

To toggle the overlay network editor, the default hotkey is ` (backtick). Space is configured for the volatile toggle to temporarily hide the overlay network editor.

Okay, thanks! How would I go about disabling the spawning of resample node in SOP context, since it's interfering with default visibility / render hotkey? Do I need to change it in hotkeys.csv or in the .keymap2?
Edit: removing it from the .csv worked!

Also where would I change the backtick toggle since it's not really compatible with my keyboard layout?

Thanks for your help!

Xr_Blood
Hello! I've been using this plugin for a while, and I really enjoy the convenience it brings.

Recently, I encountered an issue while developing my own tool. In Houdini's main panel, the Network Editor by default allows creating an externaldragdrop.py file to support external drag-and-drop events. However, it seems that the Supercharged Network Editor doesn't support this functionality.

Xr_Blood
Here’s a small suggestion from me: Starting from version 20.5, nodegraphhook supports returning a hotkeySymbol to determine whether a specific shortcut key is currently pressed. This can be directly used to block existing shortcuts and replace them with custom ones. So, is it possible to write the current shortcuts for the Supercharged shelf tools into the hook, using JSON or another format, so users can set them themselves? It feels like this approach would be more intuitive and convenient to use.

Xr_Blood

Image Not Found

Can the shortcut keys for shelftool also be modified in the hotkeys.csv file?

sh:shelftoolname

animatrix_

Xr_Blood

Image Not Found

Can the shortcut keys for shelftool also be modified in the hotkeys.csv file?

Those can be modified using the standard hotkey editor but the upcoming version allows you to do the same using the hotkeys.csv like so:

sh:shelftoolname

which can call any existing shelf tool.

Xr_Blood

animatrix_

Xr_Blood

Image Not Found

Can the shortcut keys for shelftool also be modified in the hotkeys.csv file?

Those can be modified using the standard hotkey editor but the upcoming version allows you to do the same using the hotkeys.csv like so:

sh:shelftoolname

which can call any existing shelf tool.

Thank you for your response; the functionality is very powerful. I would greatly appreciate it if you could let me know once the issue with the drag-and-drop feature for external events is resolved.

tpetrick 特佩特里克
Houdini has a script hook for external drag/drop, but currently only file path data is supported.

To use the script hook add a Python script named externaldragdrop.py to the Houdini script path, for example ~/houdini16.5/scripts/externaldragdrop.py. The script should define a function called dropAccept which takes a single parameter. Every time a drop event occurs on the main Houdini application it will call the dropAccept function with a list of file path(s) that were dropped onto Houdini. The function can return True to block the drop event from continuing on to Houdini, or False to indicate that Houdini should handle the drop event itself.

An example drop handler script that ignores .hip file drops and creates Font SOPs with the contents of the incoming files:

import hou
import os

def dropAccept(file_list):
    if len(file_list) == 1 and os.path.splitext(file_list[0])[1] == ".hip":
        return False

    for filename in file_list:
        with open(filename) as f:
            contents = f.read()

        obj = hou.node("/obj")
        geo = obj.createNode("geo", "geo1", False, False)
        font = geo.createNode("font")
        font.parm("text").set(contents[:20])

    return True

If the data in the drag/drop event contains arbitary text or binary data instead of file paths the script hook won't be invoked. This is something that would need to be fixed on our end - I can look into fixing that if necessary.

Xr_Blood

tpetrick 特佩特里克
Houdini has a script hook for external drag/drop, but currently only file path data is supported.

To use the script hook add a Python script named externaldragdrop.py to the Houdini script path, for example ~/houdini16.5/scripts/externaldragdrop.py. The script should define a function called dropAccept which takes a single parameter. Every time a drop event occurs on the main Houdini application it will call the dropAccept function with a list of file path(s) that were dropped onto Houdini. The function can return True to block the drop event from continuing on to Houdini, or False to indicate that Houdini should handle the drop event itself.

An example drop handler script that ignores .hip file drops and creates Font SOPs with the contents of the incoming files:

import hou
import os

def dropAccept(file_list):
    if len(file_list) == 1 and os.path.splitext(file_list[0])[1] == ".hip":
        return False

    for filename in file_list:
        with open(filename) as f:
            contents = f.read()

        obj = hou.node("/obj")
        geo = obj.createNode("geo", "geo1", False, False)
        font = geo.createNode("font")
        font.parm("text").set(contents[:20])

    return True

If the data in the drag/drop event contains arbitary text or binary data instead of file paths the script hook won't be invoked. This is something that would need to be fixed on our end - I can look into fixing that if necessary.

I saw a post on the forum where SideFX staff member tpetrick wrote.

animatrix_

Xr_Blood

tpetrick 特佩特里克
Houdini has a script hook for external drag/drop, but currently only file path data is supported.

To use the script hook add a Python script named externaldragdrop.py to the Houdini script path, for example ~/houdini16.5/scripts/externaldragdrop.py. The script should define a function called dropAccept which takes a single parameter. Every time a drop event occurs on the main Houdini application it will call the dropAccept function with a list of file path(s) that were dropped onto Houdini. The function can return True to block the drop event from continuing on to Houdini, or False to indicate that Houdini should handle the drop event itself.

An example drop handler script that ignores .hip file drops and creates Font SOPs with the contents of the incoming files:

import hou
import os

def dropAccept(file_list):
    if len(file_list) == 1 and os.path.splitext(file_list[0])[1] == ".hip":
        return False

    for filename in file_list:
        with open(filename) as f:
            contents = f.read()

        obj = hou.node("/obj")
        geo = obj.createNode("geo", "geo1", False, False)
        font = geo.createNode("font")
        font.parm("text").set(contents[:20])

    return True

If the data in the drag/drop event contains arbitary text or binary data instead of file paths the script hook won't be invoked. This is something that would need to be fixed on our end - I can look into fixing that if necessary.

I saw a post on the forum where SideFX staff member tpetrick wrote.

Ok using that script, I get the drag and drop but it only seems to work on the 3d viewport. You manage to get it working using the regular network editor? I think this might require more to get it working for any network editor.