K2 Projector from LoRA:
FVM_K2_ProjectorFromLoRA extracts twelve projector values directly from a projector LoRA file, giving you the file’s own values instead of an approximation from a preset table. It supports both a direct projector-difference tensor and a rank-1 projector adapter format. This is useful when you want to reproduce the effect of a compatible projector LoRA while keeping a separate LoRA loader out of the rest of your graph. The node prepares projector settings for downstream use; it does not modify a model by itself.
K2 Projector from LoRA Input Parameters:
lora_name
Select the LoRA file from the available LoRA list. The node resolves the selected file and reads its projector delta, so choose a compatible projector LoRA rather than assuming any ordinary LoRA will work. There is no fixed default stated in the source, and the available options depend on the files installed in your LoRA folders. The node description identifies both direct projector-difference files and rank-1 projector adapters as supported formats.
multiplier
Sets a signed scale for the twelve extracted values, similar to adjusting the strength of this projector delta. The default is 1.0, which uses the extracted values at their original scale; the allowed range is -8.0 to 8.0, in steps of 0.05. A value of 0 makes the effective values zero, while a negative value reverses their sign. The node retains the unscaled values separately in its projector payload, so this setting changes the effective values rather than the values read from the file.
identity_protection
Sets the identity-protection value passed to the projector payload. Its tooltip describes this setting as keeping identity prompt tokens on the unmodified baseline layer mix. The default is 1.0, and the allowed range is 0.0 to 1.0, in steps of 0.05. The node stores this value for downstream use; the provided source does not show how a later node applies it to an image or model.
enabled
Sets whether the projector payload is marked as enabled. The available options are True and False, with True as the default. The tooltip says that turning it off passes the model through untouched, but this node itself does not receive or return a model: it still reads the LoRA, calculates the values, and returns both outputs. The enabled flag tells downstream components whether to apply the projector effect.
K2 Projector from LoRA Output Parameters:
projector
A K2_PROJECTOR payload for a compatible downstream node. It contains the selected LoRA’s name, twelve unscaled values extracted from the file, twelve effective values after applying multiplier, the identity_protection setting, an enabled flag, and a source marker identifying the LoRA. This is the output to connect when another node needs the complete projector configuration, including settings that are not represented in the text output.
values
A STRING containing the twelve effective projector values as a JSON array, rounded to four decimal places. These are the scaled values, not the original values extracted from the file. For example, a zero multiplier produces an array of zero-valued effective entries. The string is returned even when enabled is False, so it is useful for inspecting the calculation but does not, on its own, indicate that the effect is active.
K2 Projector from LoRA Usage Tips:
- Start with a known projector LoRA and leave
multiplierat1.0to use its extracted delta at the original scale. Check thevaluesoutput when you want to see the resulting twelve numbers. - Adjust
multiplierin small increments of0.05when tuning the effect. Use0to test a zero-strength delta without changing the selected file; remember that negative values reverse the delta’s sign. - Keep
identity_protectionat its default of1.0when you want the identity-protection setting described by the node’s tooltip. Change it only when the downstream projector workflow calls for a different setting. - Set
enabledtoFalseto mark the projector configuration as inactive for downstream use. This does not skip file loading, so keep a valid LoRA selected even while the node is disabled.
K2 Projector from LoRA Common Errors and Solutions:
Selected LoRA file cannot be found
- Explanation: The node resolves
lora_namewithget_full_path_or_raise, so execution can fail if the selected filename no longer points to an available LoRA. The exact error wording comes from the file-path helper and is not shown in the provided source. - Solution: Confirm that the file is still in a configured LoRA folder, refresh the available LoRA list, and select the file again.
LoRA does not contain a supported projector delta
- Explanation: The node expects projector data in one of the two formats described by its source: a direct projector-difference tensor or rank-1 projector adapter tensors. An unrelated LoRA may not provide the data needed to produce twelve values. The extraction helper’s exact error message is not included in the provided context.
- Solution: Select a LoRA known to contain a compatible projector delta. Do not assume that a LoRA intended for general model or style loading is a projector LoRA.
LoRA file cannot be read or parsed
- Explanation: Reading and interpreting the selected file happens inside the extraction helper, whose implementation and error messages are not provided. A damaged file or an unsupported file structure may prevent extraction.
- Solution: Verify that the file opens in the workflow it was supplied for, replace an incomplete download, or try a known-compatible projector LoRA to isolate the problem.
The projector appears inactive when enabled is False
- Explanation: The node marks the returned projector payload as disabled, even though it continues to calculate and display effective values. Seeing numbers in
valuesdoes not mean the projector effect is enabled. - Solution: Set
enabledtoTrueand ensure theprojectoroutput is connected to a compatible downstream node.
The result is weaker, stronger, or reversed than expected
- Explanation:
multiplierscales the extracted delta;0produces zero effective values, values above or below1.0change its scale, and negative values reverse its sign. These are configuration results, not necessarily file errors. - Solution: Reset
multiplierto1.0to check the file’s original scale, then adjust it gradually while inspectingvalues.
