Workbench/Solid : Texture interpolation not displaying properly in viewport (shared across all users of an image) #106312

New Issue

Open

opened 2023-03-30 15:37:28 +02:00 by Jake Moore · 5 comments

Jake Moore commented

2023-03-30 15:37:28 +02:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18

Blender Version
Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: 1be25cfff18b
Worked: --

Short description of error
Low resolution textures are no longer being correctly displayed as a sharp graphic in the viewport when the texture interpolation is set to "closest" in the material shader.

feature works as intended in rendered view so long as Eevee or Cycles is selected. Workbench does not work as intended in rendered view.

Exact steps for others to reproduce the error
place object into scene. Locate a low resolution asset such as pixel art and map the texture to the object.

textures have always appeared blurry at first in the viewport but common pixel art practice is to set the interpolation from "linear"(or whichever is set to default) to "closest"

We have 4 materials each having individual Image Texture nodes (but all using the same image).

If you take the example file, and set Interpolation to Closest on all of them, you'll get it working in the viewport as well.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18 **Blender Version** Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: `1be25cfff18b` Worked: -- **Short description of error** Low resolution textures are no longer being correctly displayed as a sharp graphic in the viewport when the texture interpolation is set to "closest" in the material shader. feature works as intended in rendered view so long as Eevee or Cycles is selected. Workbench does not work as intended in rendered view. **Exact steps for others to reproduce the error** place object into scene. Locate a low resolution asset such as pixel art and map the texture to the object. textures have always appeared blurry at first in the viewport but common pixel art practice is to set the interpolation from "linear"(or whichever is set to default) to "closest" We have 4 materials each having individual Image Texture nodes (but all using the same image). If you take the example file, and set Interpolation to Closest on all of them, you'll get it working in the viewport as well.

1.0 MiB

Pixel test.png

677 KiB

850 KiB

Jake Moore added the

labels 2023-03-30 15:37:28 +02:00

Iliya Katushenock commented

2023-03-30 15:45:05 +02:00

Member

I don't think this is a bug since it shouldn't work in the first place. But I'm not sure here.

I don't think this is a bug since it shouldn't work in the first place. But I'm not sure here.

Iliya Katushenock added the

EEVEE & Viewport

Nodes & Physics

labels 2023-03-30 15:45:16 +02:00

Jake Moore commented

2023-03-30 16:06:38 +02:00

Author

Beg pardon, on further investigation it looks like there's an addition facet of the problem that I'd not taken into account. The object that I'd introduced into this scene was originally a .obj.

If I completely remove the default material generated from the accompanying .mtl file and build it from scratch the issue doesn't appear.

I'd missed this originally as the workflow between a native blender object and .obj object has been identical up until this point.

quick recording of the workflow in a previous version for reference:

https://imgur.com/a/WEn5BAm

Beg pardon, on further investigation it looks like there's an addition facet of the problem that I'd not taken into account. The object that I'd introduced into this scene was originally a .obj. If I completely remove the default material generated from the accompanying .mtl file and build it from scratch the issue doesn't appear. I'd missed this originally as the workflow between a native blender object and .obj object has been identical up until this point. quick recording of the workflow in a previous version for reference: https://imgur.com/a/WEn5BAm

Richard Antalik commented

2023-03-30 22:00:23 +02:00

Member

You have tested this in 3.2.0, but I can't reproduce such behavior. That said, I have only 3.2.2 build, but not sure if viewport interpolation would be included in corrective release. Also tested 3.0 and 3.1. This looks like intended behavior to me.

You have tested this in 3.2.0, but I can't reproduce such behavior. That said, I have only 3.2.2 build, but not sure if viewport interpolation would be included in corrective release. Also tested 3.0 and 3.1. This looks like intended behavior to me.

Philipp Oeser commented

2023-04-11 09:48:30 +02:00

Member

I can confirm an issue here.

We have 4 materials each having individual Image Texture nodes (but all using the same image).

If you take the example file, and set Interpolation to Closest on all of them, you'll get it working in the viewport as well.

You should be able to set Interpolation on each of them individually though (I think -- without having looked at code) . ~~If I export the whole thing (after unpacking the texture) to OBJ and then import again, this seems to work as expected.~~

So the issue seems to be that for some reason the property is shared across all materials in the viewport -- and it is unclear which of the Image Texture nodes Interpolation is being considered.

I can confirm an issue here. We have 4 materials each having individual `Image Texture` nodes (but all using the same image). If you take the example file, and set `Interpolation` to `Closest` on all of them, you'll get it working in the viewport as well. You should be able to set Interpolation on each of them individually though (I think -- without having looked at code) . ~~If I export the whole thing (after unpacking the texture) to OBJ and then import again, this seems to work as expected.~~ So the issue seems to be that for some reason the property is shared across all materials in the viewport -- and it is unclear which of the `Image Texture` nodes `Interpolation` is being considered.

Philipp Oeser commented

2023-04-11 10:19:56 +02:00

Member

Well, not so sure anymore how this is intended to work, seems like workbench_material_get_image will get the same image across multiple materials (and Image texture nodes) and switch multiple times. Order obviously makes a difference here then. If you want to be sure for Solid viewport shading, all users of the same image would have to set Interpolation the same.

Will reach out to the module to decide here.
If this is a limitation of Workbench/Solid, it might be good to mention this in the manual.

Well, not so sure anymore how this is intended to work, seems like `workbench_material_get_image` will get the same image across multiple materials (and Image texture nodes) and switch multiple times. Order obviously makes a difference here then. If you want to be sure for Solid viewport shading, all users of the same image would have to set Interpolation the same. Will reach out to the module to decide here. If this is a limitation of Workbench/Solid, it might be good to mention this in the manual.

Philipp Oeser added

EEVEE & Viewport

and removed

EEVEE & Viewport

Nodes & Physics

labels 2023-04-11 10:20:36 +02:00

Philipp Oeser changed title from ~~Texture interpolation not displaying properly in viewport~~ to Workbench/Solid : Texture interpolation not displaying properly in viewport (shared across all users of an image)

2023-04-11 10:22:55 +02:00

Philipp Oeser added the

Images & Movies

labels 2023-07-12 11:24:39 +02:00

Philipp Oeser referenced this issue

2023-07-12 11:35:24 +02:00

Eevee: image sequence data bloc displays different offset attributes when set from different locations (texture editor, shader editor, image locator) #109769

Sign in to join this conversation.

No Label

Animation & Rigging

Asset Browser Project Overview

Automated Testing

Blender Asset Bundle

Dependency Graph

Development Management

EEVEE & Viewport

Images & Movies

Motion Tracking

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Render Pipeline

Sculpt, Paint & Texture

Video Sequencer

Virtual Reality

Blender 2.8 Project

Milestone 1: Basic, Local Asset Browser

Good First Issue

Animation & Rigging

Development Management

EEVEE & Viewport

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Sculpt, Paint & Texture

Needs Info from Developers

Needs Information from User

No Milestone

No project

No Assignees

4 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#106312

No description provided.