3D View alpha channel transparency behaviour changes depending on object creation order #55130

Closed
opened 2018-05-20 01:45:49 +02:00 by sok0 · 5 comments

The alpha channel transparency behavior masks older objects while allowing newer objects to be seen.

In other words, If you create a Cube first, then a plane with alpha transparency the plane masks the cube from view.

But

if you create a plane with alpha transparency then a cube, the cube is not masked.

Furthermore

If you create a Cube first, then a plane with alpha transparency the plane masks the cube from view. Then if you duplicate the cube, the duplicated cube is not masked. Then if you duplicate the plane, it masks everything again.

In the attached example, Cube was created first, Then Plane, Then Cube.001, Then Plane.001, Then Cube.002.

Additionally, behavior changes when objects are selected. In the above described example no objects are selected. Selected cubes are always masked by planes with alpha transparency. Selected planes never mask cubes.

It looks like there was an attempt at some point to remedy this problem by adding Object data Display Transparency option. However this has other undesirable consequences like elimination of the selection outline.

The default behavior is illogical. Requiring objects to be duplicated in the order that you want them shown is not logical. The behavior changing depending on object selection is also illogical; why would you want an object to disappear when it is selected?alpha transparency.blend

The alpha channel transparency behavior masks older objects while allowing newer objects to be seen. In other words, If you create a Cube first, then a plane with alpha transparency the plane masks the cube from view. But if you create a plane with alpha transparency then a cube, the cube is not masked. Furthermore If you create a Cube first, then a plane with alpha transparency the plane masks the cube from view. Then if you duplicate the cube, the duplicated cube is not masked. Then if you duplicate the plane, it masks everything again. In the attached example, Cube was created first, Then Plane, Then Cube.001, Then Plane.001, Then Cube.002. Additionally, behavior changes when objects are selected. In the above described example no objects are selected. Selected cubes are always masked by planes with alpha transparency. Selected planes never mask cubes. It looks like there was an attempt at some point to remedy this problem by adding Object data Display Transparency option. However this has other undesirable consequences like elimination of the selection outline. The default behavior is illogical. Requiring objects to be duplicated in the order that you want them shown is not logical. The behavior changing depending on object selection is also illogical; why would you want an object to disappear when it is selected?[alpha transparency.blend](https://archive.blender.org/developer/F3398773/alpha_transparency.blend)
Author

Added subscriber: @sok0

Added subscriber: @sok0
Author

uploaded the wrong file... use this one instead{F3398841}

uploaded the wrong file... use this one instead{[F3398841](https://archive.blender.org/developer/F3398841/alpha_transparency.blend)}
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Alpha sorting was a long-standing 'problem' but it will be fixed in 2.8.
This has been reported a couple of times, see #43093, #51964, #46349, #49376, #44826, #41731

But there is a workaround though of the top of my head:

I guess consensus here was to close these reports as 'wont fix in 2.7' ... and enjoy eevee in 2.8 :)

Alpha sorting was a long-standing 'problem' but it will be fixed in 2.8. This has been reported a couple of times, see #43093, #51964, #46349, #49376, #44826, #41731 But there is a workaround though of the top of my head: - parent all of your objects to an empty - unparent them in the desired drawing order - voila, proper drawing order is restored :) [have a look at this tutorial https://www.youtube.com/watch?v=4mSGOTaoCgM] I guess consensus here was to close these reports as 'wont fix in 2.7' ... and enjoy eevee in 2.8 :)
Member

Closed as duplicate of #43093

Closed as duplicate of #43093
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
No Assignees
2 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#55130
No description provided.