🔀 Bawk LoRA Switch:
BawkLoraSwitch lets you choose one of up to four LoRA sets for the next part of your workflow. It passes along the selected set and provides readable text describing its triggers and LoRAs, making it easier to compare alternatives without rebuilding your connections. The node does not apply LoRAs to a model itself; it selects which set to pass downstream.
🔀 Bawk LoRA Switch Input Parameters:
active
Choose which connected LoRA set to pass through. The available choices are A, B, C, and D, and the default is A. Selecting a slot determines all three results: the stack, its trigger text, and its LoRA summary. There is no numeric minimum or maximum.
set_a
An optional LORA_STACK for choice A. Connect the set you want passed downstream when active is A. When another choice is active, this input does not contribute to the results. There is no numeric range or specified default; you can leave it unconnected.
set_b
An optional LORA_STACK for choice B. Its contents are used only when active is B, so you can keep a second LoRA configuration connected for comparison. There is no numeric range or specified default; you can leave it unconnected.
set_c
An optional LORA_STACK for choice C. Its contents are used only when active is C, providing another configuration you can select without changing connections. There is no numeric range or specified default; you can leave it unconnected.
set_d
An optional LORA_STACK for choice D. Its contents are used only when active is D, providing a fourth selectable configuration. There is no numeric range or specified default; you can leave it unconnected.
🔀 Bawk LoRA Switch Output Parameters:
lora_stack
The selected LORA_STACK to connect to a downstream node that accepts that type. The node normalizes the selected value into a stack with LoRA and trigger lists; it does not apply those LoRAs to a model. If the selected input is unconnected, the node requests an empty stack.
lora_triggers
A STRING containing the selected stack’s triggers joined with commas and spaces. You can use it where downstream prompt-building nodes accept trigger text. If the selected stack has no triggers, this output is an empty string.
lora_info
A STRING summarizing the selected stack’s LoRAs as name@strength, separated by commas. For example, a LoRA named portrait_style at strength 0.8 appears as portrait_style@0.8. This is a readable summary, not a replacement for the lora_stack connection; it is empty when the selected stack has no LoRAs.
🔀 Bawk LoRA Switch Usage Tips:
- Connect each alternative to a different set input, then change
activeto compare them while keeping downstream connections in place. - Keep
activeon a connected slot when you expect a LoRA set. Selecting an unconnected slot passes an empty stack instead. - Connect
lora_stackto a downstream node that acceptsLORA_STACK. Connectlora_triggersseparately if your prompt workflow needs the selected set’s trigger text. - Check
lora_infoto confirm which LoRAs and strengths the selected stack reports. A blank summary can also mean the selected stack contains no LoRAs.
🔀 Bawk LoRA Switch Common Errors and Solutions:
Selected LoRA set is missing
- Explanation: If
activepoints to an unconnected set input, the node requests an empty stack. This may look as though your LoRAs have stopped taking effect downstream. - Solution: Connect a
LORA_STACKto the selected slot, or changeactiveto a slot that is already connected.
Trigger text is blank
- Explanation:
lora_triggersis empty when the selected stack contains no triggers. The trigger output is separate from the LoRA summary. - Solution: Confirm that
activeselects the intended set and that the upstream stack includes the trigger text you expect.
LoRA summary is blank
- Explanation:
lora_infohas nothing to list when the selected stack contains no LoRAs. The selected slot may also be unconnected. - Solution: Check the selected input and inspect the upstream stack for LoRA entries.
LoRAs do not affect the generated image
- Explanation: This node selects and passes a stack; its source does not show it loading or applying LoRAs to a model. A disconnected or unsuitable downstream path can therefore leave the image unchanged.
- Solution: Confirm that
lora_stackreaches a compatible downstream node that applies the selected stack, and verify that the intended slot is active.
Invalid or incompatible LORA_STACK connection
- Explanation: The set inputs are declared as
LORA_STACK. A connection supplying another type may be rejected by the workflow, while malformed stack contents may prevent the node from producing its text summaries. The supplied source does not establish a specific error-message string for these cases. - Solution: Connect a node that produces
LORA_STACKand check that its LoRA entries contain names and strengths in the expected form.
