Possible Z-fighting background images using Depth = Both #60484

Closed
opened 4 years ago by RomboutVersluijs · 19 comments

System Information
OSX 10.11.6
Intel Iris Pro 1536 MB

Blender Version
2.80, 3c3d80ea22, 2019-01-08 23:33

Short description of error
It looks like the new method for background images has a small issue when Depth is set to Both. It looks like there is some kind of Z-fighting or normal issue perhaps. It looks like noise, weird effect

Exact steps for others to reproduce the error

  1. Use any scene or new scene as long as there are object in the viewport
  2. Add image as Empty
  3. Use any image and place it around an object or in between
  4. Now hovering the mouse over the image or moving the scene will show a weird noise kind of effect. Sort of like normals or z-fighting
  5. setting Depth to Front or Back solves this "issue"

Ive attached a screengrab of this

Z-fighting-or-normal-issue-ref-images.gif

**System Information** OSX 10.11.6 Intel Iris Pro 1536 MB **Blender Version** 2.80, 3c3d80ea22af, 2019-01-08 23:33 **Short description of error** It looks like the new method for background images has a small issue when Depth is set to Both. It looks like there is some kind of Z-fighting or normal issue perhaps. It looks like noise, weird effect **Exact steps for others to reproduce the error** 1. Use any scene or new scene as long as there are object in the viewport 2. Add image as Empty 3. Use any image and place it around an object or in between 4. Now hovering the mouse over the image or moving the scene will show a weird noise kind of effect. Sort of like normals or z-fighting 5. setting Depth to Front or Back solves this "issue" Ive attached a screengrab of this ![Z-fighting-or-normal-issue-ref-images.gif](https://archive.blender.org/developer/F6280493/Z-fighting-or-normal-issue-ref-images.gif)
Poster

Added subscriber: @RomboutVersluijs

Added subscriber: @RomboutVersluijs
Collaborator

#60846 was marked as duplicate of this issue

#60846 was marked as duplicate of this issue
Collaborator

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Collaborator

Can't reproduce it on my machine right now. Could you create a .blend file that shows the bug (on your machine)? Make sure to pack the image into the file.

Can't reproduce it on my machine right now. Could you create a .blend file that shows the bug (on your machine)? Make sure to pack the image into the file.
Poster
Here is a file [Image-ref-depth-issue.blend](https://archive.blender.org/developer/F6286899/Image-ref-depth-issue.blend) ![Screen Shot 2019-01-14 at 12.38.20.png](https://archive.blender.org/developer/F6286891/Screen_Shot_2019-01-14_at_12.38.20.png)
Collaborator

Added subscriber: @fclem

Added subscriber: @fclem
Collaborator

Looks fine when I open it, so it is probably gpu/os related..
Are your drivers up to date?

Screenshot from 2019-01-14 17-46-05.png

Looks fine when I open it, so it is probably gpu/os related.. Are your drivers up to date? ![Screenshot from 2019-01-14 17-46-05.png](https://archive.blender.org/developer/F6286942/Screenshot_from_2019-01-14_17-46-05.png)
Poster

I dont have supported GPU, nothing to update. See first post for Hardware. Its an Intel Iris Pro.

Is the setting still the same? Thinking about it, why does it show being behind a object, what is default when you can choose front or back??
Is front default or is back default?

I dont have supported GPU, nothing to update. See first post for Hardware. Its an Intel Iris Pro. Is the setting still the same? Thinking about it, why does it show being behind a object, what is default when you can choose front or back?? Is front default or is back default?
Poster

I see perhaps the cause now. If i change MultiSample under Preferences > General > OpenCL > MultiSampling from None to 2 or more it gets less noticeable.
But still shows very faint,.

Before
Screen Shot 2019-01-14 at 12.38.20.png

After
Screen Shot 2019-01-14 at 12.52.42.png

I see perhaps the cause now. If i change MultiSample under Preferences > General > OpenCL > MultiSampling from None to 2 or more it gets less noticeable. But still shows very faint,. Before ![Screen Shot 2019-01-14 at 12.38.20.png](https://archive.blender.org/developer/F6287008/Screen_Shot_2019-01-14_at_12.38.20.png) After ![Screen Shot 2019-01-14 at 12.52.42.png](https://archive.blender.org/developer/F6287006/Screen_Shot_2019-01-14_at_12.52.42.png)
brecht commented 4 years ago
Owner

Added subscribers: @santbg, @brecht, @WilliamReynish

Added subscribers: @santbg, @brecht, @WilliamReynish

Added subscriber: @elbox01

Added subscriber: @elbox01
santbg commented 4 years ago

This problem doesn't just appear on my mac when I reported it. I just found out that it also appears on the work computer.
Capture.png
BugWindows.blend
System Information
Operating system: Windows 10, Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz 3.40 GHz, 16,0 GM (RAM)
Graphics card: Intel(R) HD Graphics 4600
Blender Version
blender-2.80-936014ea8c74-win64, 2019-03-12
Short description of error
When dragging an image to the ViewPort and placing an object in front of or behind it presents a noise in the image
Exact steps for others to reproduce the error

  1. Start Blender
  2. Drag an image to the viewport
  3. I place a plane or a cube in front or behind and noise appears in the image.
This problem doesn't just appear on my mac when I reported it. I just found out that it also appears on the work computer. ![Capture.png](https://archive.blender.org/developer/F6810515/Capture.png) [BugWindows.blend](https://archive.blender.org/developer/F6810517/BugWindows.blend) **System Information** **Operating system:** Windows 10, Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz 3.40 GHz, 16,0 GM (RAM) **Graphics card:** Intel(R) HD Graphics 4600 **Blender Version** blender-2.80-936014ea8c74-win64, 2019-03-12 **Short description of error** When dragging an image to the ViewPort and placing an object in front of or behind it presents a noise in the image Exact steps for others to reproduce the error 1. Start Blender 2. Drag an image to the viewport 3. I place a plane or a cube in front or behind and noise appears in the image.
fclem was assigned by JacquesLucke 4 years ago
Poster

My guess is that the default none. For me it works when i choose front or back. Perhaps this is the issue, the old version had only 2 options, this now has basically 3.

My guess is that the default none. For me it works when i choose front or back. Perhaps this is the issue, the old version had only 2 options, this now has basically 3.
santbg commented 4 years ago

Mac Version: blender-2.80.0-git20190321.9105e1d08467-x86_64 (2019-03-21) work fine for me. Check it up

Mac Version: blender-2.80.0-git20190321.9105e1d08467-x86_64 (2019-03-21) work fine for me. Check it up
Poster

I used this one, edbf15d3c0, master, 2018-11-28, from Blender and seems to work fine now :)

https://www.dropbox.com/s/w4s8xmgmq7dylsf/Z-fighting-or-normal-issue-ref-images-solved.gif?raw=1

I used this one, edbf15d3c044, master, 2018-11-28, from Blender and seems to work fine now :) https://www.dropbox.com/s/w4s8xmgmq7dylsf/Z-fighting-or-normal-issue-ref-images-solved.gif?raw=1
fclem commented 4 years ago
Collaborator

does using the "use alpha" option also work?

does using the "use alpha" option also work?
Poster

Yes, hardly visible due to the blunt Axis colors. But it seems to work.

Screen Shot 2019-03-22 at 19.31.46.png

Not sure why, but looks like Axis colors are slight transparent orso. They are less vibrant than the color input in the Theme panel

Yes, hardly visible due to the blunt Axis colors. But it seems to work. ![Screen Shot 2019-03-22 at 19.31.46.png](https://archive.blender.org/developer/F6867341/Screen_Shot_2019-03-22_at_19.31.46.png) Not sure why, but looks like Axis colors are slight transparent orso. They are less vibrant than the color input in the Theme panel
fclem commented 4 years ago
Collaborator

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
fclem closed this issue 4 years ago
fclem commented 4 years ago
Collaborator

Ok the axes are going through but that's a side effect of alpha blending. So main issue is resolved.

Ok the axes are going through but that's a side effect of alpha blending. So main issue is resolved.
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/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
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/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
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
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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
No Assignees
7 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#60484
Loading…
There is no content yet.