hello first time posting.
so i have an issue of stuff not cooking(i think) outside of a container
but inside the container always works fine.
if outside the container the 1st time always seems to work while the ones thereafter don’t.
the values go from -1 to 0 then immediately to 1 and back to 0.
it should smoothly go from -1 to 0 then 0 to 1 smoothly.
i have 2 triggers both going into math nodes.
one range mapped to -1 to 0 the other 0 to 1.
both of these go into a switch
when the trigger going from -1 to 0 is 0 a chop execute with code changes the switch’s index to 1
which is the 2nd trigger which then gets called to go from 0 to 1.
from the switch i go into a null to force cooking.
then i have some logic nodes to check when both have gone off with AND bools.
the null has been an exported chop or expression on multiply nodes translate Y parameters from -1 to 1.
here’s a video of it working multiple times inside a container then not working when outside of it.
any help would be appreciated. hopefully i explained the issue correctly. TOUCH ISSUE
Hey,
I have also encountered this issue.
I’d love to tell you how I solved it, but I have no idea. I’m not even sure that it won’t come back!
However, keep in mind that TD is a pull-to-cook, not push-to-cook system.
Make sure there are nodes requesting the data that want to cook. Cook - Derivative explains it.
Also, try changing exports to expressions. This might have been a thing that helped me, but I was changing quite a lot at once to fix the issue of nodes not cooking
I’m not sure I can help further.
I’m new to TD, and have encountered exactly what you’ve described. If I’m in the troublesome Base Comp everything runs smoothly, if I’m not in the Base Comp then some unknown nodes stop cooking.
I haven’t figured out a way to diagnose it, because whenever I look at it, it starts working.
I started playing around with Null CHOPs to auto or selective cook, I changed exports to expression references etc.
Unfortunately, by the time I noticed these issues, my project grew and I was unable to isolate the issue to properly submit a bug report.
Can you isolate your issue in a way that you can share it? Ie as a .toe or .tox? As well as the steps needed to see the issue.
I’d like to try it on my servers, and see if I can reproduce it.
If it’s reproduceable, then maybe we can submit a bug report. Or maybe ask for clarification of documentation.
Like I said: I’m pretty new to TD, I’ve encountered this, I played around for a while, and I have no idea how I fixed it (or even if I have fixed it).
But I absolutely want to get to the bottom of it!
Can you share the file? that would make understanding the issue easier.
TouchDesigner usually cooks things on a need basis - simply said: if the calculated value is somehow needed to display something, it will be calculated. A much more in depth explanation can be found here: https://docs.derivative.ca/Cook
Having said that - being able to look at you file will make it easier to see if perhaps something is going wrong.
issue is inside of PREGAME container
game starts in IDLE
controls are:
player 1 can join with 1 or 2
player 2 can join with 3 or 4
R to reset
so for example.
p2 joins first by pressing 4
then p1 joins by pressing 2
there you should see the issue off it cooking inside the container and not outside.
if it moves on to GAME container i just press R and reset to IDLE.
let me know if i need to explain anything.
hopefully you guys can catch something i’m completely missing.
i appreciate the help.
sorry - need some more pointers - which parameters should I be watching? I press 4, wait a bit and the press 2… watching the parameters triggervalue2 and triggervalue1…
yeah the trigger value parameters on the PREGAME custom parameters
those use the rename nodes
while the multiply4 & 5 inside the pregame container use the null after the rename nodes.
i did that to see if i was getting different values from rename to null, but they’re pretty much the same.
visually you can watch LEDCROPPER1
right now i have them as exports but ive had them as expressions as well.
if you watch the video in my original post maybe you can see what i’m doing.
ah - i see it - yes - the issue being the triggers that go into the switch - only the trigger is being calculated that currently is selected by the switch. As an easy workaround instead of changing the logic, you can put a Null CHOP after the par1 CHOP and set it to Cook Type: Always.
But in these cases I would actually try to rethink the logic: instead of using a Switch CHOP, use a Math CHOP and add the 2 CHOPs together (Combine CHOPs: Add), this way both triggers are always being considered and you save a logic plus CHOPExecute.
thank you very much for the help snaut.
yeah adding the 2 chops makes more sense.
i can’t change it right now but will the moment i get a chance.
just started last week with touch, once again thank you for the help.
