Hi,

I've been busy editing a simple motion graphics title for my YT channel, which consists of 2 pngs that zoom in and rotate in 3D space (3D Source Alpha, with some colour grading to alter the colours on the pictures), and a logo that "ripples" in (using a NewBlue transition - can't remember the exact name) with FXHome Ignite Express Auto Light Flares plugin to add a halo-y flare.

The Ignite Express flare was keyframed to expand in size and intensity towards the end of the clip to give a white-out effect, and this was fine when I saved the clip.

Then I decided to add some motion blur to the video bus and save it. Whilst it was open with the motion blur just added, the flares seemed to be doing what I expected (but I didn't check the keyframes specifically)

Now when I've come back to edit it a bit more (change the flare type and keyframe timing) having added the motion blur, saved it and left it overnight, the keyframes have disappeared. This would be annoying enough, but there is some really odd behaviour going on too:

1) I add a keyframe in the plugin window - it will put a marker in for the selected option of intensity or size - okay, seems reasonable;

2) I go to add the corresponding keyframe for the other option, and the original option's keyframe just vanishes and that property resets itself;

3) I try to add more than one keyframe for anything and all keyframed properties in the window vanish and reset!

I tried several things, including removing the plugin from the clip and re-inserting the plugin, removing the clip from the timeline and re-inserting it (then adding the plugin), removing the motion blur on the video bus, removing the media from the project and even switching the Auto Light Flares to the manual "Light Flares" plugin in Ignite Express, but the same weird behaviour still persists...

In the end I managed to get curves to let me keyframe one parameter (size) on the manual "Light Flares" plugin, which achieved the effect I was after well enough for my purposes, but it was more work-around than any kind of solution.

I'm not really after too much help here, as I'm fairly certain that it will be some sort of interaction between the Ignite Express plugin, Vegas (16.307), the project files and my specific hardware, but I did wonder if anyone had seen this type of behaviour before?

Cheers!