[Resolved?] [2025.32820] project.cookRate get´s reset

Bugs
1

It seems like that something is resetting the cookRate on startup. When trying to set the projectCookrate using an executeDAT, even with delayed frames, something will reset it to the project-cookRate.
I think somewhere was an issue where a projects cookRate would reset to 60 and I assume that the fix for that borked the possibility to set it via executeDAT:

grafik
grafik1664×612 87.4 KB

As a workaround I can use a timerCHOP to delay the execution of the script.

grafik
grafik1563×1140 105 KB

2

Hi @plusplusone

Can you confirm in latest? I can’t seem to repro.

Best,
Michel

3

Indeed, in 33070 this behaviour seems to be resolved.
I did search for a mention in the release notes but could not find anything.

4

As a note, while this is fixed in TouchDesigner, this is not working with the Engine Implementation of Pixera. Not sure if this is something that the pixeraTeam has to take care of or if this is something inherint to TouchEngine.
It does work though when using the deferred method using the timerCHOP.

6

A couple of notes about TouchEngine:

  1. onStart() won’t be called for an Execute DAT because the .tox is loaded after TouchEngine has started
  2. TouchEngine expects the host to set a frame-rate programmatically which is applied after loading a .tox (and the host could apply it any time while running too)

Why are you setting a frame-rate? Can you achieve the same end by other means?

7
  1. I am calling onStart() in the onCreate() method so it will fire in both cases which does work.
  2. I assumed as much but for the moment the TuchEngine in Pixera is locked at 60 without a means from Pixera itself to adjust it. Using python to set the cookRate is the proposed solution from their site.