Latest v17 beta: nodes linking to self

Hello,

I have some issues with the nodes linking to themselves when detaching from a different node. Result is the program crashing. Is this happening to anyone else?

Also, since the last update to v17 the system has become very unstable, and will freeze regularly, with a high chance of shutting down altogether. The good side is i don't lose much, if any work; the bad, it happens often enough to slow any progression, and usually dose not request info for sending a report.

Have these bugs/issues been reported, and any potential fixes. Is it an issue with the biological to computer interface?

Thanks,
John

Nodes on which page?

And, what does it mean that a node links to itself?

Nodes on which page?

And, what does it mean that a node links to itself?

Nodes in Fusion. Output for a node is linking to it's own inputs, either background, foreground, and so on.

Thought I responded, but nothing has posted, so...


Jim, Fusion node out put are linking to their inputs(Background, Foreground, and others).

For all to read:

The nodes in fusion are connecting their output to their own background, foreground, or other connections.

OK, I haven't seen that myself, but my Fusion work in 17 has been fairly minimal.

I'm thinking that's definitely not supposed to happen.

Thanks, Jim,

Now to figure out why my replies are not posting.

(You're posting by logging into the forums with a browser?)

(You're posting by logging into the forums with a browser?)

Yes

Well, seem to be coming through fine now.

For all to read:

The nodes in fusion are connecting their output to their own background, foreground, or other connections.

Could you post a screenshot? (The nice thing about these forums is that they upload your screenshot to their own storage and you don't have to post them to another place and only link to them as on many other forums.)

You literally have lines running from the output on a node to its own input? I'm not even sure how that would look, since they'd take a straight line. Or are you instead disconnecting a node but leaving it in place so that the pipe from the previous node to the next node runs underneath your disconnected node and only appear to be connecting input to output? (I've definitely had my fair share of times when I ended up with a node sitting on a pipe but not connected to it and I was totally puzzled as to why the controls were having no effect.)

Hey Jim,

I'll post a screenshot tomorrow. Sorry for the slow communication on my end!

Thanks!
John

Sorry for the delay, here is an image of a linked node.

Sorry, I see an error icon instead of the image.

Sorry, I see an error icon instead of the image.

Odd. Not sure why, but I can open it is a second window. Let me know if that works, and I'll try to reupload as well.

Thanks!

Here's what I see. Just the word "Image", but no actual image.

No Image.png (18.05 KiB) Viewed 998 times

Screenshot_20210112-173451.png (194.88 KiB) Viewed 997 times

That's messed up.

I see it now. And that truly does look like the link's output linked to its mask input. Weird! (I also had never thought you could display clips in Fusion. Just learned something.)

You've definitely found a bug, since it's not possible to manually make that kind of connection. I could almost imagine this happening if you copy/pasted or otherwise loaded the script associated with these nodes, but it sounds like it's happening spontaneously.

It happens when I disconnect the node, and I can manually link the node to itself.

Again I apologize for the slow responses, I just finished with a play production and should have better response time for a bit.

Thanks,
John