FIXED: me.rate not updating

After changing the fps, I have to force cook the math chop to update the me.rate expression, despite it is cooking each frame. Maybe due to optimization.

Cheers, David

(Lastest experimental.)
MeRate.toe (3.66 KB)

This was fixed in 22230, and I just confirmed it is working in the latest experimental 2018.22270, which came out on 20 April. Can you check that you are running that build?

I made a quick video to demonstrate.
If I close and reopen the file, the expression is corrected…
MeRate.mov (2.15 MB)

yes but which TD build are you running django?

The video shows, that it is 2018.22270 and it is not working for me.
I’m on Windows 10.

Another case of an expression not updating with 2018.22270 and Windows 10.
The destination expression in the Replicator and the actual path do not match, after moving the replicator to another Base.

I see the issue. me.time.rate is fixed but not me.rate. Will get right on it.

Ran into this problem as well, trying to run some things at 240fps with nodraw. Easy way to diagnose is to use a sharedmem chop out to another touch instance to monitor, the data will be still be time sliced at 60fps if you go into perform at 240fps, unless me.time.rate is replaced with 240 manually.

Will be fixed in 2018.22900.

Just a note that you should be using me.time.rate, rather than me.rate, which will give a recursion warning.

Build 2018.23080 with a fix for this is now available.

Download

New fix in 2018.23210. Hopefully didn’t miss anything this time!