Assigning to Art to gather his insight into how showEffect should be working.

In the renderer, the values for showEffect and showEffectLength are simply included in the call to updateProperties that is sent to the client. In the client side, these values are stored and checked at two different points (one for client-side mode and another for server-side mode) to see if there's an effect to execute. If there is, then a call to ice.ace.animation.run() is made. It would be convenient to find out whether the problem occurs in both modes or only in server-side mode, as the latter is more tricky. Probably, the recent changes to add ace:ajax support broke the way effects were working.

Not sure what I was doing differently when I made this issue, but I can't reproduce the problem. Maybe there was an interaction at that stage due to some regression I hadn't yet taken care of.

Worked fine in client and server side modes.