Eevee: No Motion Blur on linked objects #78561

New Issue

Adriano Oliveira · 2020-07-03T04:15:14+02:00

Adriano Oliveira commented

2020-07-03 04:15:14 +02:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14

Blender Version
Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-07-02 22:21, hash: 5a13f682ee

Short description of error
Local rigged characters have MB even with Shutter=0.5; BG Sep.=100; MaxB=32; Steps=1.
Same character linked in a new file has no Eevee MB with Shutter=0.5; BG Sep.=100; MaxB=32; Steps=1 (you have to raise above 1).
It seams to affect only deformeble meshs.

Exact steps for others to reproduce the error

Take any a charcater (local to the file). Animate its Armature. Render with Eevee MB with Shutter=0.5; BG Sep.=100; MaxB=32; Steps=1.
Link the same charcater to a new file. Animate its Armature. Render with Eevee MB with Shutter=0.5; BG Sep.=100; MaxB=32; Steps=1.
or
Download attached files to the same directory
Open shot.blend
Render (F12)
Only the unlinked object will have motion blur
shot.blend
lib.blend

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14 **Blender Version** Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-07-02 22:21, hash: `5a13f682ee` **Short description of error** Local rigged characters have MB even with Shutter=0.5; BG Sep.=100; MaxB=32; Steps=1. Same character linked in a new file has no Eevee MB with Shutter=0.5; BG Sep.=100; MaxB=32; Steps=1 (you have to raise above 1). It seams to affect only deformeble meshs. **Exact steps for others to reproduce the error** - Take any a charcater (local to the file). Animate its Armature. Render with Eevee MB with Shutter=0.5; BG Sep.=100; MaxB=32; Steps=1. - Link the same charcater to a new file. Animate its Armature. Render with Eevee MB with Shutter=0.5; BG Sep.=100; MaxB=32; Steps=1. or - Download attached files to the same directory - Open `shot.blend` - Render (F12) Only the unlinked object will have motion blur [shot.blend](https://archive.blender.org/developer/F8662150/shot.blend) [lib.blend](https://archive.blender.org/developer/F8662151/lib.blend)

Adriano Oliveira commented

2020-07-03 04:15:14 +02:00

Added subscriber: @AdrianoOliveira

blender-admin commented

2020-07-03 04:15:14 +02:00

#79393 was marked as duplicate of this issue

Adriano Oliveira changed title from ~~No Eevee Motion Blur with Step 1 for linked characters~~ to No post-process Eevee Motion Blur with linked deformeble meshes

2020-07-03 18:22:09 +02:00

Adriano Oliveira commented

2020-07-03 18:24:10 +02:00

I have updated the title.
With further investigation, it seams the problem is that post-process blur is not working with linked deformeble meshes. Only accumulation blur does.

I have updated the title. With further investigation, it seams the problem is that post-process blur is not working with **linked** deformeble meshes. Only accumulation blur does.

Paul Szajner commented

2020-07-03 21:59:07 +02:00

Added subscriber: @sozap

Paul Szajner commented

2020-07-03 21:59:07 +02:00

I can confirm this is happening in our production files.

Here are some test files that demonstrate the issue, lib.blend contain a rig.
shot .blend contain a cube and the rig, both are animated.

Download both files, open shot .blend and render a frame, the cube get blurred while the other that is skinned to the armature isn't blured...
shot.blend
lib.blend

As a side note, this was working in the intial commit , but once this bug https://developer.blender.org/T78073 was fixed this new issue appear ...

I can confirm this is happening in our production files. Here are some test files that demonstrate the issue, lib.blend contain a rig. shot .blend contain a cube and the rig, both are animated. Download both files, open shot .blend and render a frame, the cube get blurred while the other that is skinned to the armature isn't blured... [shot.blend](https://archive.blender.org/developer/F8662150/shot.blend) [lib.blend](https://archive.blender.org/developer/F8662151/lib.blend) As a side note, this was working in the intial commit , but once this bug https://developer.blender.org/T78073 was fixed this new issue appear ...

Germano Cavalcante changed title from ~~No post-process Eevee Motion Blur with linked deformeble meshes~~ to Eevee: No Motion Blur on linked objects

2020-07-07 20:17:22 +02:00

Germano Cavalcante commented

2020-07-07 20:17:22 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Richard Antalik commented

2020-08-05 04:44:30 +02:00

Added subscribers: @LaStefan, @iss, @mano-wii

Ebubekir Özdemir commented

2020-08-08 12:20:33 +02:00

Added subscriber: @krizalid55

Ebubekir Özdemir commented

2020-08-08 12:20:33 +02:00

Actualy its working on linked object. but if you select instance collection in linking options motion blur ignoring objects in instanced collection. Basicly character meshes are visible in outliner its getting motion blur, if not it not getting motion blur. I tested 3 different ways. But also our studio using the left side method for linking. I hope the picture is descriptive.

Actualy its working on linked object. but if you select instance collection in linking options motion blur ignoring objects in instanced collection. Basicly character meshes are visible in outliner its getting motion blur, if not it not getting motion blur. I tested 3 different ways. But also our studio using the left side method for linking. I hope the picture is descriptive. ![bug_report.jpg](https://archive.blender.org/developer/F8758627/bug_report.jpg)

Clément Foucault was assigned by Dalai Felinto

2020-08-10 17:05:15 +02:00

Dalai Felinto commented

2020-08-10 17:22:24 +02:00

Added subscribers: @dr.sybren, @dfelinto

Dalai Felinto commented

2020-08-10 17:22:24 +02:00

A few things:

It indeed doesn't work for rigged linked objects.
What @krizalid55 suggests is a different enough workflow that doesn't really work as a workaround for this issue (instanced proxified collections).

Clément: Sybren is helping Sergey a lot with depsgraph. You can ask him for some help if the issue is not obvious (and it is depsgraph related)

A few things: * It indeed doesn't work for rigged linked objects. * What @krizalid55 suggests is a different enough workflow that doesn't really work as a workaround for this issue (instanced proxified collections). Clément: Sybren is helping Sergey a lot with depsgraph. You can ask him for some help if the issue is not obvious (and it is depsgraph related)

Clément Foucault commented

2020-08-12 01:26:21 +02:00

Added subscriber: @Sergey

Clément Foucault commented

2020-08-12 01:26:21 +02:00

The issue comes from this workaround:

  if (!oedata->geom_update) {
    /* FIXME(fclem) There can be false positive where the actual mesh is not updated.

           * This avoids a crash but removes the motion blur from some object.
           * Maybe an issue with depsgraph tagging. */

    mb_geom->use_deform = false;
    oedata->geom_update = false;

    GPU_VERTBUF_DISCARD_SAFE(mb_geom->vbo[MB_PREV]);
    GPU_VERTBUF_DISCARD_SAFE(mb_geom->vbo[MB_NEXT]);
  }```


But this is also caused by the fact the object is not tagged with `ID_RECALC_GEOMETRY` which then triggers the above workaround.

cc @Sergey @dr.sybren

The issue comes from this workaround: ```lang=cpp ``` if (!oedata->geom_update) { /* FIXME(fclem) There can be false positive where the actual mesh is not updated. ``` * This avoids a crash but removes the motion blur from some object. * Maybe an issue with depsgraph tagging. */ ``` mb_geom->use_deform = false; oedata->geom_update = false; ``` ``` GPU_VERTBUF_DISCARD_SAFE(mb_geom->vbo[MB_PREV]); GPU_VERTBUF_DISCARD_SAFE(mb_geom->vbo[MB_NEXT]); }``` ``` But this is also caused by the fact the object is not tagged with `ID_RECALC_GEOMETRY` which then triggers the above workaround. cc @Sergey @dr.sybren

Sergey Sharybin commented

2020-08-12 09:59:27 +02:00

From this brief explanation sounds like the workaround is wrong :)

Can you explain things a bit deeper? Is it something when geometry is (in)directly modified and ID->recalc does not include ID_RECALC_GEOMETRY? Do you have simple file which can be investigated from the depsgraph side?

From this brief explanation sounds like the workaround is wrong :) Can you explain things a bit deeper? Is it something when geometry is (in)directly modified and `ID->recalc` does not include `ID_RECALC_GEOMETRY`? Do you have simple file which can be investigated from the depsgraph side?

blender-admin commented

2020-08-12 17:02:28 +02:00

This issue was referenced by 1eab858dbc

This issue was referenced by 1eab858dbc8455d48eebcb896310efa583526207

Clément Foucault commented

2020-08-12 18:07:43 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Clément Foucault closed this issue

2020-08-12 18:07:43 +02:00

Thomas Dinges added this to the 2.90 milestone 2023-02-08 16:26:17 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Eevee: No Motion Blur on linked objects #78561