Need help with troubleshooting display jitter

General TouchDesigner Discussion
1

Hi,

I’m having a bit of a weird issue concerning base COMPS and display in 088 62160 and I was wondering if anyone ever had to troubleshoot something similar.

I’ve got a rendered scene that’s in a base COMP about three levels down in my network with only basic out CHOP + over CHOP compositing going on from one level to another. The scene runs as expected when I’m in the lowest level where the render is but as I go up there begins to be some serious jitteriness and flickering as though there was some z-space fighting.
The issue seems to disappears when I enter perform mode but so far it has caused 3 kernel power issues and made my computer shut down out of nowhere.

Could this be a hardware issue?

Any help troubleshooting is appreciated!
Thanks

youtu.be/xfP52vB2KV4

2

Are those white lines that look kind of like rain intended or are those rendering artifacts as well?

3

intended. they’re my stand in for rain ha

4

Ok jeez, I think I may have put my finger on it. I think it’s an error in how I’ve resampled or stretched the number of samples I have in my chop channels that causes some jitteriness in my instances :unamused: . It wasn’t so obvious because they appear to be smooth when looked at in the viewer but that would probably account for that sort of problem!

Here is another video for demonstrative purposes.

youtu.be/SgQ4Fnx-I6Y

Thanks for taking the time to read my thread Malcom!

5

Hmm, generally bluescreens and other OS level issues are hardware or OS problems. It’s very very hard for a bug in TD to cause a bluesceen.

6

Hey Owen,

I usually see this when I’m using something times sliced to drive instances. You can work around this with a stretch CHOP which essentially trims out one of your samples. There are sound downsides to this approach, but it should help with part of what you’re seeing here.

Unbypass the hog CHOP in this sample network to see the differences between shuffle1 and shuffle2. I know this doesn’t exactly mirror your set-up but I think it’s the same challenge.
base_timeslice_workaround.tox (718 Bytes)

7

Thanks Matthew. Turns out that my shuffle CHOP didn’t have ‘‘use first sample’’ selected. It didn’t occur to me that this would be an issue since I was sending it single-sample channels but it’s 100% what was causing the problem further down the line.