Thatās the point, Masterdynamic should NOT do a prerolling.
=> disconnect frost from tP, save, reset scene, reload, jump timeline to F250 => no prerolling
=> reconnect frost, save, reset, reopen scene, jump timeline to F250 => prerolling
=> return to F000, just reload cache, jump to F250 => no prerolling : this one it the normal behaviour of Masterdynamic
When Cache on Masterdynamic, this should jump directly to frame then load the particles from that frame.
Somehow with Frost 2.1 connected to tP, Masterdynamic react like a dynamicSet
This happen only with Frost 2.1, imagine this with 1000+frames and/or hundreds of thousands of particles how time consuming this is, and we canāt use a MXS code to hack this on farm because if we manipulate tP interface throw MXS, it will force slaves to grab one tP network-sim licence, then will release it only when the slave have finish the all job).