

To me the legacy option would work in two ways:ġ) Apply a new particular to a layer – it automatically is in the new mode, but somewhere at the top of its effects settings in an option to switch to legacy mode.Ģ) Open a project that has particular 2 in it – same migrate settings window opens, but an option to use legacy mode to retain expressions. So far my request is still an open active request to the developers but I don’t think its getting much traction. I’ve been having a discussion with Red Giant support for a few months now to try to get a legacy mode added when migrate settings from an older version. I link Particular position to nulls all the time – often its not a big deal to now relink them, but in some older projects with complex position expressions referencing many other vaules and sliders this can be difficult, especially since once migrated, the old expressions are gone and no way to even see what they were before. Upon clicking the “Migrate Settings” button when opening an old project in the new version, you get an error and all the old expressions are gone. The problem, however, is that they’ve NOT included any way to support old projects which had expressions driving the separate and fields. Probably a good move and I totally agree. In the latest version of Trapcode Suite v14 – they unified this in to a single field. Particular has always referenced the position of the emitter with two fields, one and a separate field for 3D – granted it is a bit clunky, but its been that way forever. To all Trapcode Particular fans out there….
