I have a problem that on some machines perform mode on the second monitor doesn’t work. The content just freezes on that monitor, while everything in TouchDesigner is running. The same project with the same version of TouchDesigner worked on a different machine.
This is the issue that happened to me several times, so I’m pretty sure that many of you must have experienced it.
I found one post that mentioned similar problem. There the solution was disabling Nahimic services, but I don’t have those installed.
sorry you are running into this issue.
Can you provide a bit more information on your issue that could help us replicate it?
Especially we are interested in:
TouchDesigner build
hardware setup
are there differences in the hardware setup between the machines and output devices
can this be replicated with simple test networks or is this specific to certain projects
when you say everything in TouchDesigner is running, does this mean you are in perform mode or opened a Window COMP as a separate window?
Hello Markus,
Thank you for the quick response. I will give you the exact responses on Monday, I can’t check right now all the hardware, because two installations are now running on both machines and I don’t remember them all.
For now I can tell what I know:
we tried at the beginning a build 2023.sth and when the issue happened we installed the newest official which should be 2025.32460. No difference
I believe that it would behave the same if we wanted to use default beans newproject.toe. because it is very basic setup
we tried many option: classical perform option with F1, Opening perform window as a separate screen (then we saw that project was running), a window operator as well. It was still frozen
with the project running fine on one machine but not the other, my first approach would be making sure that all drivers are up to date. Also connecting a second monitor instead of the wall processor could be a good check to try to narrow down the issue.
If nothing changes, the next test would be switching out the video card, both trying the RTX 4090 in the machine that is successfully running the project currently as well as trying the RTX 3090 in the machine that is showing the issue.
This sounds very much like the issue is outside of TouchDesigner.
After days of research I think we found the pattern in those incidents. We discovered that my colleague, usually an experienced TD user, had this habit of turning off “window draw” in the perform parameters and possibly that’s what happened. I’m not betting everything on that theory because I tried it myself and it didn’t work even though I don’t have this habit.
But eventually it works for us
ha, that would do it - not something I would have thought about!
Do you know the reasoning behind why to turn the Draw Window parameter off? Just curious.
I can only guess. I did this once few years ago and my reasoning back then was that “draw window” did what parameter “borders” does. When people think about windows in computers, they usually associate it with a window with border with those “-,x” icons. That’s I think what happened.
So there was no rational reasoning.
