If you are applying the time effects to a nested comp that contains Particular run a quick test by creating a new composition, adding particular with the default settings, pre-compose the particular layer and then add your time effects. If that works then check you settings in Particular and the other layers in the nested comp. If the simple test crashes then let us know. It works fine on my system. If you apply any time effects that can be applied to a layer that has particular or any other particle generator applied you will either have a lock up or crash. You MUST pre-compose time based effects like particle generators before applying time effects like Frame Hold or Time Remap. Most of the time AE will not even let you apply these effects.
Thanks, I did as you asked - just added particular with it's default setting, pre-composed and added Time Remap.
That seems to work fine as well, but as soon as I do either of the following scenarios it crashes:
-Have Partcular Precomp shorter than Main comp (My Instance - Particular Comp 5 Seconds, Main Comp 10 Seconds)
-Add Time Remap to Particular Comp
-add a keyframe 1 frame before the end of the Precomp.
-Delete the last keyframe (So particles don't disappear
-Extend the comp to the end
-(I would usually use a Loop expression at this stage - but AE crashes)
-Have Particular Precomp in a Main Comp
-Move to the middle of the Precomp
-Add a Hold Keyframe
-This ends in a crash
Let me know if this is fine on your side.
Thanks for the help
I have sent through a bug report as there does not seem to be an isolated/individual problem and I have read several reports of the same issue as well as tested on other users machines.
This is only happening in CC 2014.
Experiencing the same problem Time Remapping or reversing nested comps that use particular. The application is using a layer emitter to build a logo where the only way to make it build from Particles is by reversing the effect. Tried this with a basic particular comp with same crashing/hanging results on multiple machines.
I logged a bug with Trapcode at the same time I did with Adobe.
I do however feel like it is a similar bug to that which was causing crashes only in CC 2014 with regards to plugins like unMult etc. which seemed to be a problem on Adobe's side.
The Unmult bug was entirely different and unique. It was a bug that only affected effects with no properties.
During our process of switching platforms, I've found this bug on the Windows side only. It's re-producable every time on the Windows machines. The issue does not occur on Mac platform. Can anyone here confirm that Red Giant is actually aware of this bug?
quick steps to re-produce:
add particular v2.2.3 to solid
add freeze frame keyframe to pre-composed layer
I found solution for me. I install particular 2.2.2 instead of 2.2.3 and all works fine.
Happens to me on OSX with After Effects CC 2014 and Particular 2.2.3. Solution was to install downgrade Particular to anything before 2.2.3.
All I'm doing to cause the crash is precomp Particular and then time remap that comp.