Motion blur not working

Flame Flame Questions
1

HI there,
Has anyone else had problems with motion blur in Action in Flame 2025?
If I try to adjust the shutter setting it breaks the motion blur and I only get a single sample rendered.
Any suggestions as to how to fix it?

Thanks,
Dan

2

The obvious questions first:

  • Are you in preview mode and not 3D mode?
  • Adaptive degradation off?
  • Motion blur animated?
1 Like
3

I’m in preview mode.
Adaptive Deg is off.
Motion blur is not animated.
When its set to 20 samples and .5 Shutter I can see what is expected, but if I bring the Shutter down at all then it stops working. If I change the Phase the single sample moves as expected.

I’m running on Rocky Linux

4

Is your motion blur keyframed at all? If so, make sure the interpolation isn’t set to Constant or w/e.

5

No keyframes. Its very strange, 7 Samples and .25 Shutter is fine but if I change the Samples to 8 then it breaks. Back to 7 and its good again…

I’ve done a full restart and no different

6

Next series of questions. Did you try:

  • New project?
  • New user?

A new user solved a very similar problem for another fellow Flame artist last week.

7

oh, I’ll give it a try

8

@DanCullen - @SamE was having some unusual motion blur problems recently.

9

I was having issues with Motion blur in the G-Mask tracer. After setting mo blur prefs to .5, 7 samples it rendered black. Sounds different, but possibly related.

10

Hello ! Can you try to look at the result in a mux after the action ?
Had this issue a week ago and the action output was not showing the motion blur but it was there

11

Hi, I’ve the same problem now. Did you fixed it?

12

I seem to recall fixing this by either rebooting (VRAM leaks) or Ctrl-shift-D on the action node to duplicate it.

1 Like
13

Hi Lisa,
My understanding is that the motion blur problem is a bug that is caused when the start frame number is very high, usually as a result of converting timecode/camera-code to frame numbers.
It is fixed in the latest release, I think.
I would try reformatting the source clip start frame number to 1 or 1001 and see if that fixes it.
If I can find the relevant release note I’ll post it here.
I hope this helps..

Dan

1 Like
14

Thank you so much for your help. :clap: I solved the problem.

15

Thanks, I also tried to do this but it didn’t work. Thanks anyway for answering me.