Page MenuHome

Cycles Displacement node not automatically inserted in older files
Closed, DuplicatePublic

Description

I am having an issue with 2.80-ff108aac631-win64 2018-12- 11

I have a testing model that I created in 2.5 and imported into 2.8. when looking at it in the vie{F5927217}

{F5927215}wport shading modes as well as the rendering it works correctly in eevvee, but when I switch to cycles, parts of the model go crazy. I am uploading images as well as the file

System Information win 10 64
Operating system:
Graphics card: quadro

Blender Version 2.80-ff108aac631-win64

(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)
Worked: (optional)

Short description of error

When using cycles rendering in solid, wire, and texture window draws the objects correctly, when switching to rendered draw type or when rendering the object does not render in the correct location.

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).

Details

Type
Bug

Event Timeline

Philipp Oeser (lichtwerk) triaged this task as Normal priority.

This is because the tire.001 material is using displacement (directly from an image/color).
In newer blender versions this needs to go through the (new) dedicated Displacement node.

This is usually inserted for you automatically, the cycles addon runs a bit of code when it sees an older file

if bpy.data.version <= (2, 79, 1) or (bpy.data.version >= (2, 80, 0) and bpy.data.version <= (2, 80, 3)):
    displacement_nodes_insert()

This runs after the normal blender do_versions

bpy.app.handlers.version_update.append(version_update.do_versions)

Not exactly sure why this has not happened in your case (it is not clear what you exactly did when you say "imported into 2.8"... appended? opened the file?).
@Brecht Van Lommel (brecht): do bpy.app.handlers.version_update also run when appending?

I remember a similar issue in T54504 (where this apparently does not run when linking...)

@david (dasmitty101): That all being said, you can easily get around it by manually inserting the Displacement node (that takes the image as input and then goes to the Material Displacement input socket...)

Leaving this open for the time being (so we can get the question answered whether or not the cycles addon do_versions can be improved upon...)

Philipp Oeser (lichtwerk) renamed this task from cycles object displays incorrectly with blender-2.80-ff108aac631-win64 to Cycles Displacement node not automatically inserted in older files.Dec 13 2018, 2:38 PM