hfVisualizer Remote Control Node
node
hfVisualizer --remote [--target <id>] node <id> <x,y,z> [--nset <name>]
- Creates or updates one node in preprocessing mode.
<id>must be a positive integer.<x,y,z>must be three finite numeric values.- If
<id>does not exist, the command creates a new node. - If
<id>already exists, the command updates that node coordinate. --nsetis optional and is supported only when creating a new node.- This is the canonical IPC/CLI form for
Node Tablecreate and coordinate-edit operations.
Example:
hfVisualizer --remote node 101 0,0,0
hfVisualizer --remote node 101 10,20,30
node-copy
hfVisualizer --remote [--target <id>] node-copy <translate-copy|translate-move|rotate-copy|rotate-move> [--source <text>] --direction-axis <text> [--distance-angle <text>] [--start-id <id>] [--nset <name>] [--merge-node <on|off>]
- Applies the same operation as the GUI
Copy Nodewidget. --sourceuses nset-expression syntax:- integer ids or id patterns such as
1,2,3,1:3,1:9:2 - existing nset names
__selected__for the current UI node selection-tokento remove ids, nsets, or__selected__from the source set- If
--sourceis omitted, the default is__selected__. --direction-axisuses the same numeric repeat syntax as the GUI:- translate:
dx,dy,dz - rotate:
x1,y1,z1,x2,y2,z2 --distance-angleuses the same repeat syntax as the GUI, such as1,2,2@1.5or20,30,2@15.translate-copyandrotate-copyrequire--start-id.translate-movedoes not use--distance-angle.--nsetis optional and matches the GUI behavior by inserting source/result nodes into that nset.--merge-nodedefaults toon.
Example:
hfVisualizer --remote node-copy translate-copy --source "__selected__" --direction-axis 1,0,0 --distance-angle 100,2@50 --start-id 1001 --nset COPIED --merge-node on
hfVisualizer --remote node-copy rotate-move --source "TOP_NODES,-__selected__" --direction-axis 0,0,0,0,0,1 --distance-angle 15
node-delete
hfVisualizer --remote [--target <id>] node-delete <ids|__selected__>
- Deletes nodes by id pattern or current node selection in preprocessing mode.
- Uses the same safe delete behavior as the GUI.
<ids>accepts integer id patterns such as1,2,3,1:5,1:9:2.__selected__resolves to the current node selection.- This is the canonical IPC/CLI form for
Node Tablerow deletion. - Validation rules:
- preprocessing mode only
- every requested id must already exist before deletion starts
__selected__requires a non-empty current node selection- Partial delete behavior:
- safe delete may leave some requested nodes undeleted
- when that happens, the command returns
DELETE_PARTIALwithrequestedIds,deletedIds,remainingIds, counts, and the canonicalscriptTail - the applied tail is still recorded in Remote Control History because the model has changed
Example:
hfVisualizer --remote node-delete 101:105
hfVisualizer --remote node-delete __selected__