It seems that the the “start” function of the execute DAT doesn’t works.
I read on the wiki it should be exectuted at the start fot he patch, but it doesnt’t.
Please see the attached patch, I expected that the count will increase by 1 after 30 seconds of the “start” of the patch.
Can you please help me?
Thank you:
PS: Touchdesginer 2025.30060 (but also on old 2023 versions) and Windows 10
startExecure.2.toe (4.8 KB)
Hi @Simplo,
I think that is caused because of order of execution. Probably the instruction is sent in TD before it can be interpreted. I’m not sure if there’s a systematic solution for this from Derivative, but I often get around this issue by delaying the initial instruction by a single frame, or a second to be sure. You can try changing the code in your execute script to:
run("op('button1').click()", delayFrames=60)
Hope that helps.
Best,
Darien
Your workaround seems to work!!! Than youm grat idea!
Now I’m just wondering what’s the use of the original START 
1 Like
Yah, after looking into this more, it’s definitely a problem of all the execute callback DATs inside button not being initialized before the start script is fired.
We’re looking into this further, but as mentioned above, safest bet is to delay the click. Just 1 frame should do it in this case.
Thanks for the example,
Rob.
Thank you Rob!
Experimental builds 2025.31354 will now execute the onStarts after initializing other callback scripts (panel, parm, etc) on startup.
This should fix your example, provided you change the button type to momentary, and/or toggle the button state so the next click action increments the count.
Cheers.
Thank you so much!!!