Page MenuHome

Surface Deform Modifier Not Rendering Properly in Cycles
Closed, ArchivedPublic


System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: AMD Radeon (TM) R9 390 Series ATI Technologies Inc. 4.5.13547 Core Profile Context 25.20.15027.1003

Blender Version
Broken: version: 2.80 (sub 60), branch: blender2.7, commit date: 2019-05-10 09:55, hash: rB196dbc0f314e
Worked: (Blender 2.79)

Short description of error
The Surface Modifier is not showing in the final render in Cycles. It only appears to render fine during the preview mode. I have attached an image that illustrates the issue.

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]



Event Timeline

Brecht Van Lommel (brecht) triaged this task as Needs Information from User priority.May 11 2019, 12:21 PM

We need a simple .blend and steps to reproduce the problem, a screenshot is not enough information for us to investigate.


Not a problem, here is a blend file that you can use. :)

I tried to reproduce the problem in a new file and I couldn't. It seems like there is an issue with this file in particular, but I can't figure out what it is. The original file worked well in Blender 2.79.

Thank you,

The issue append because objects with surface deform are binded to a mesh with a subsurf that is different from viewport and render.
Activating subsurf on 'oldWarrior_body' disable surface deform on other objects. It's not a bug but how surface deform is working.

Surface deform is quite effective to rig some objects , but depending how it's binded it's get disabled on the viewport ( like when using simplify) or (like in your case) at rendertime .

You may try to have two surface deform : one for viewport that is binded to 'oldWarrior_body' without subsurf, and one enabled at rendertime that is binded to "'oldWarrior_body" with subsurf activated...

Quoted Text The original file worked well in Blender 2.79.

You may have changed settings bettwen 2.79 and 2.8 because this behaviour as always been there.

Thank you for the solution! It makes sense. It works now. I really appreciate the time and the effort. Thank you again :)

Brecht Van Lommel (brecht) claimed this task.

This is a source of confusion that we should try to address once, but indeed it's not a bug then.