Collision drastically affects shading in BI #51685

Closed
opened 2017-05-31 22:33:17 +02:00 by Serge Lyatin · 13 comments

System Information
Win7 64

Blender Version
Broken: 2.78a

Short description of error
Render produces different shading for two objects which are sharing same mesh data. But one object has got Collision modifer, another - doesn't.

Exact steps for others to reproduce the error
I know, that you are not developing BI anymore, but anyway. Render file, then check/uncheck Switch node checkbox to see the difference.
Collision_render_artifact.blend

**System Information** Win7 64 **Blender Version** Broken: 2.78a **Short description of error** Render produces different shading for two objects which are sharing same mesh data. But one object has got Collision modifer, another - doesn't. **Exact steps for others to reproduce the error** I know, that you are not developing BI anymore, but anyway. Render file, then check/uncheck Switch node checkbox to see the difference. [Collision_render_artifact.blend](https://archive.blender.org/developer/F614629/Collision_render_artifact.blend)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @SergeL

Added subscriber: @SergeL

Added subscriber: @mont29

Added subscriber: @mont29

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2017-06-01 09:13:31 +02:00

That’s no bug, afaik no render engine survives well to coplanar faces… Numerical imprecision just makes it impossible to decide which face is visible for which pixel, generates auto-shadowing, etc.

That’s no bug, afaik no render engine survives well to coplanar faces… Numerical imprecision just makes it impossible to decide which face is visible for which pixel, generates auto-shadowing, etc.
Author

Sorry, but I don't understand how the same mesh has different shading due to collision modifier, which does nothing in this case. Also Cycles produce the same shading with or without Collision modifier.

Sorry, but I don't understand how the same mesh has different shading due to collision modifier, which does nothing in this case. Also Cycles produce the same shading with or without Collision modifier.

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'

Eeeeek! Ok, totally completely misunderstood the report here, sorry!

Now, issue here is with triangulation, looks like collision modifier can affect base mesh in some cases, yuck. :/

Eeeeek! Ok, totally completely misunderstood the report here, sorry! Now, issue here is with triangulation, looks like collision modifier can affect base mesh in some cases, yuck. :/
Bastien Montagne removed their assignment 2017-06-01 16:51:09 +02:00

Added subscriber: @ideasman42

Added subscriber: @ideasman42

Tried to understand what’s going on here for quite some time now, and… am running out of idea.

Issue is not with Collision modifier, that one does not affect DM data at all - and anyway, tried emptying its evaluation function and changed nothing.

So am assuming issue is somewhere in modifiers stack evaluation itself (aka mesh_calc_modifiers()), but could not pinpoint any differences here… Imho it's either tessellating issue, or poly normal issue, but both seem to be handled exactly the same way in both cases. @ideasman42 may have more ideas/insight?

Tried to understand what’s going on here for quite some time now, and… am running out of idea. Issue is not with Collision modifier, that one does not affect DM data at all - and anyway, tried emptying its evaluation function and changed nothing. So am assuming issue is somewhere in modifiers stack evaluation itself (aka `mesh_calc_modifiers()`), but could not pinpoint any differences here… Imho it's either tessellating issue, or poly normal issue, but both seem to be handled exactly the same way in both cases. @ideasman42 may have more ideas/insight?

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Germano Cavalcante self-assigned this 2019-10-28 14:22:11 +01:00

I can't reproduce the problem in blender 2.79, so I suppose this has already been fixed.

I can't reproduce the problem in blender 2.79, so I suppose this has already been fixed.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#51685
No description provided.