Texture properties not working with OSL enabled and unpacked textures #86764
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#86764
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Linux-5.11.7-arch1-1-x86_64-with-glibc2.33 64 Bits
Graphics card: Mesa DRI Intel(R) HD Graphics 520 (SKL GT2) Intel Open Source Technology Center 4.6 (Core Profile) Mesa 20.3.4
Blender Version
Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash:
02948a2cab
Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-03-19 21:37, hash:
3494946560
Short description of error
I have a texture with RGB channels set to 1 and alpha set to 0. When trying to use this texture with OSL, the alpha property (at least) of the image texture node does not work when the texture is unpacked. I set it to channel packed, expecting the color data to be always white. The problem is that when the texture is unpacked, the color data is black.
Exact steps for others to reproduce the error
bug.blend
Added subscriber: @b5327157
Added subscribers: @Jeroen-Bakker, @mano-wii
Changed status from 'Needs Triage' to: 'Confirmed'
Thanks for the report, I can confirm.
This seems to be related to the pre-multiplication of alpha.
Although this is partly by design, this inconsistency should not exist.
The image editor is also pre-multiplying the alpha even when you just want to see the colors.
This didn't happen before, (maybe it can be considered a regression?)
@Jeroen-Bakker, on this second issue, I don't know if it's related to the changes to the image editor's drawing, but maybe you know what's going on?
The more general question to ask is that why is the OSL texture function doing alpha pre-multiplication in the first place? In such case it will not be possible to recover information from RGB channels when alpha is zero. I am not aware of any requirement regarding pre-multiplied alpha in the OSL specification.