You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m experiencing an issue with the ImpactWildcard Processor related to the use of multiple wildcards. Here’s an example to illustrate the problem:
example:
The camera angle is a {pov|side} shot, focusing on the {woman's|man's} actions, ...{ }...{ }...{ }...{ }...{ }...{ }...{ }...{ }...{ }
capturing every detail of the singing with {^1} of the action.
When I use the placeholder {^1}, it correctly picks the first referenced wildcard's value, such as pov or side. However, when I try to use {^9}, {^10}, or even {^1}, it outputs them directly as ^9, ^10, or ^1 instead of referencing the respective wildcard's value.
I've verified that my syntax is correct and that there are enough wildcards in the text, but still encounter this issue. It seems like there might be a limitation on the number of references supported by the processor.
Could you please provide guidance or a solution to address this issue? Any help would be greatly appreciated.
Thanks in advance!
The text was updated successfully, but these errors were encountered:
Hi~
I’m experiencing an issue with the ImpactWildcard Processor related to the use of multiple wildcards. Here’s an example to illustrate the problem:
example:
When I use the placeholder {^1}, it correctly picks the first referenced wildcard's value, such as pov or side. However, when I try to use {^9}, {^10}, or even {^1}, it outputs them directly as ^9, ^10, or ^1 instead of referencing the respective wildcard's value.
I've verified that my syntax is correct and that there are enough wildcards in the text, but still encounter this issue. It seems like there might be a limitation on the number of references supported by the processor.
Could you please provide guidance or a solution to address this issue? Any help would be greatly appreciated.
Thanks in advance!
The text was updated successfully, but these errors were encountered: