This repository has been archived by the owner on Feb 21, 2025. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 8
A small bug #18
Comments
It is just like when I connect input's "FLOAT.a.88" to inp, it will be automatically updated to "FLOAT.inp.**". |
Hi @vivax3794 , when will you update? |
Sorry for the lack of updates lately, just started uni so lifes been busy. |
Great, you're finally back |
Hi , How are you doing at school recently? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When the output of input is connected to something else and then to default, an error "2" will be reported when loading with subgraph.
For example, it was like this at the beginning:


Then I added a default-node, connected the first input to inp, and an error "Error loading input/outputs for subgraph:2" would be reported when loading this.
Of course, it would be normal if the input was deleted and recreated and then connected to inp first. But if it was a very complex sub-node and the connection sequence was accidentally wrong, it would be very headache-inducing.
The text was updated successfully, but these errors were encountered: