- Posts: 456
- Joined: Thu Sep 16, 2021 7:05 am
- Real Name: Cody Predum
This feels very similar to the other issue I posted about, but I'm starting a new thread because some of the behavior is noticeably different. In this case, my comped image is sometimes showing up as cut off in the viewer, but it seems random as to when. In the case of my earlier issue, it seemed to be caused by changing slider values in the inspector. Here though, I am not changing anything at all, but just by cycling through different nodes being displayed in the viewers, I can get either the correct or incorrect image from the same node without making any changes whatsoever. For example, sometimes the image is incorrect as displayed in the planar tracker, but after looking at the output from a different node and then looking at the planar tracker again, it shows up correctly. Or it doesn't. I am also seeing the same behavior on the next two downstream merge nodes.
It's kind of like that old riddle: "There's a planar tracker and merge node. One of them always tells the truth, and the other always lies. However, sometimes the planar tracker tells you what its output is, but sometimes it tells you what it thinks the merge node's output will be. The merge node does the same regarding the signal it gets from the planar tracker, or what it thinks the signal was that the tracker received. What upstream signal do you send to them so that you can figure out which one is lying?"
Ok, jokes aside, here's a screen recording:
Since this felt similar to the other issue I was seeing, I tried the work-around that we found for that bug (adding a disabled dissolve node after the planar tracker). So far that seems to treat the symptoms, but I still figured it would be worth reporting.
It's kind of like that old riddle: "There's a planar tracker and merge node. One of them always tells the truth, and the other always lies. However, sometimes the planar tracker tells you what its output is, but sometimes it tells you what it thinks the merge node's output will be. The merge node does the same regarding the signal it gets from the planar tracker, or what it thinks the signal was that the tracker received. What upstream signal do you send to them so that you can figure out which one is lying?"
Ok, jokes aside, here's a screen recording:
Since this felt similar to the other issue I was seeing, I tried the work-around that we found for that bug (adding a disabled dissolve node after the planar tracker). So far that seems to treat the symptoms, but I still figured it would be worth reporting.