UI | HDRI preview #124377

Closed
opened 2024-07-09 01:58:24 +02:00 by ^~^ · 8 comments

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 555.99

Blender Version
Broken: version: 4.2.0 Beta, branch: blender-v4.2-release, commit date: 2024-07-02 18:32, hash: edd1749e2222
Worked: (4.1.1)


@fclem

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 555.99 **Blender Version** Broken: version: 4.2.0 Beta, branch: blender-v4.2-release, commit date: 2024-07-02 18:32, hash: `edd1749e2222` Worked: (4.1.1) **** @fclem
^~^ added the
Type
Report
Severity
Normal
Status
Needs Triage
labels 2024-07-09 01:58:25 +02:00
Member

I can confirm this issue. Setting to high priority since it is a regression, although not a major one.

For developers, here is a description of the issue, and the steps to reproduce:

Description:
EEVEE's HDRI preview is shifted and squished/stretched inside the render border.

Steps to reproduce

  1. Enter material preview mode in the viewport.
  2. In the viewport overlays dropdown, enabled HDRI preview.
  3. Take note of the position and shape of the HDRI preview.
  4. Create a render border (E.g. Control + B then click drag in the viewport) and notice that the HDRI preview shifted inside it, and distort in shape if the aspect ratio of the render border does not match the viewport.
  5. Compare to 4.1.1 where this wasn't a issue.

System Information
Operating system: macOS-14.4.1-arm64-arm-64bit 64 Bits
Graphics card: Metal API Apple M1 Pro 1.2
Blender version: 4.2.0 Beta, branch: blender-v4.2-release, commit date: 2024-07-08 23:30, hash: 1f42c9eb54de


I have left the original report un-modified for moderation to take a look at.

I can confirm this issue. Setting to high priority since it is a regression, although not a major one. For developers, here is a description of the issue, and the steps to reproduce: **Description:** EEVEE's HDRI preview is shifted and squished/stretched inside the render border. **Steps to reproduce** 1. Enter material preview mode in the viewport. 2. In the viewport overlays dropdown, enabled HDRI preview. 3. Take note of the position and shape of the HDRI preview. 4. Create a render border (E.g. Control + B then click drag in the viewport) and notice that the HDRI preview shifted inside it, and distort in shape if the aspect ratio of the render border does not match the viewport. 5. Compare to 4.1.1 where this wasn't a issue. **System Information** Operating system: macOS-14.4.1-arm64-arm-64bit 64 Bits Graphics card: Metal API Apple M1 Pro 1.2 Blender version: 4.2.0 Beta, branch: blender-v4.2-release, commit date: 2024-07-08 23:30, hash: `1f42c9eb54de` --- I have left the original report un-modified for moderation to take a look at.
Alaska added this to the 4.2 LTS milestone 2024-07-09 03:25:03 +02:00
Author

I have left the original report un-modified for moderation to take a look at.

wdym 😑
everything u need to know is in the video 🤨
i keep it nice and short and straight to the point 🙃

> I have left the original report un-modified for moderation to take a look at. wdym 😑 everything u need to know is in the video 🤨 i keep it nice and short and straight to the point 🙃
Member

Hi, video is good but having short description and steps in words helps, see: https://developer.blender.org/docs/handbook/bug_reports/making_good_bug_reports/
For future reports, please avoid tagging module developers. Sometimes it may not be a bug but they would receive a email because you tagged them (sounds like a spam, no?) 🙂


Best to not extend this discussion further and stay on topic of this bug report.

Hi, video is good but having short description and steps in words helps, see: https://developer.blender.org/docs/handbook/bug_reports/making_good_bug_reports/ For future reports, please avoid tagging module developers. Sometimes it may not be a bug but they would receive a email because you tagged them (sounds like a spam, no?) 🙂 - - - Best to not extend this discussion further and stay on topic of this bug report.

@hornpub You have been asked several times now not to tag developers in your reports. It's up to the triaging team to tag reports with corresponding module labels and tag developers directly if needed.

Thanks for your understanding.

@hornpub You have been asked several times now *not* to tag developers in your reports. It's up to the triaging team to tag reports with corresponding module labels and tag developers directly if needed. Thanks for your understanding.
Member

Cause of this issue is that the lookdev spheres are rendered before the film accumulation step. This results into several artifacts what the film accumulation is handling. This includes bordered rendering, but also upsampling and in future it would also effect panoramic rendering.

IOW current implementation isn't what we want.

I will check to move the rendering of the lookdev spheres to after the film accumulation step, but that requires a different render view for them to render correctly. The fix might not make it before the initial release as it won't be tested by many users. But it should be part of a future update.

I might get back to this issue after I did all the platform support issues.

Cause of this issue is that the lookdev spheres are rendered before the film accumulation step. This results into several artifacts what the film accumulation is handling. This includes bordered rendering, but also upsampling and in future it would also effect panoramic rendering. IOW current implementation isn't what we want. I will check to move the rendering of the lookdev spheres to after the film accumulation step, but that requires a different render view for them to render correctly. The fix might not make it before the initial release as it won't be tested by many users. But it should be part of a future update. I might get back to this issue after I did all the platform support issues.
Jeroen Bakker added this to the Viewport & EEVEE project 2024-07-09 09:16:34 +02:00
Jeroen Bakker added
Type
Bug
and removed
Type
Report
labels 2024-07-09 09:16:45 +02:00
Jeroen Bakker self-assigned this 2024-07-09 12:24:08 +02:00
Member

After further investigation the cause is different and the viewport of the 3d viewport isn't reset which pushed the HDRI preview to the render border.

After further investigation the cause is different and the viewport of the 3d viewport isn't reset which pushed the HDRI preview to the render border.
Blender Bot added
Status
Resolved
and removed
Status
Confirmed
labels 2024-07-09 13:30:25 +02:00
Author

@hornpub You have been asked several times now not to tag developers in your reports. It's up to the triaging team to tag reports with corresponding module labels and tag developers directly if needed.

Thanks for your understanding.

why this is a big deal 😑 . the tagged guy himself didnt complane . when he did ill quite 🗿 . otherwise DO NOT interfere

> @hornpub You have been asked several times now *not* to tag developers in your reports. It's up to the triaging team to tag reports with corresponding module labels and tag developers directly if needed. > > Thanks for your understanding. why this is a big deal 😑 . the tagged guy himself didnt complane . when he did ill quite 🗿 . otherwise DO NOT interfere ✋️

@hornpub There are several developers working on Blender. How do you know the one you tagged will be working on this? He will get a mail notification for something he may not even need to look at.

Basically how things work on here are

  1. People report a bug
  2. The triaging team makes sure all relevant infos are there, and mark the report as confirmed if the issue can be reproduced. Also module labels are applied.
  3. Developers then look at this list of issues reported in their module and pick something to work on. This can be anyone.

I hope this is clearer now. Please follow it for further reports.

@hornpub There are several developers working on Blender. How do you know the one you tagged will be working on this? He will get a mail notification for something he may not even need to look at. Basically how things work on here are 1) People report a bug 2) The triaging team makes sure all relevant infos are there, and mark the report as confirmed if the issue can be reproduced. Also module labels are applied. 3) Developers then look at this list of issues reported in their module and pick something to work on. This can be anyone. I hope this is clearer now. Please follow it for further reports.
Thomas Dinges locked as Resolved and limited conversation to collaborators 2024-07-09 23:26:27 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
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
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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 Assignees
5 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#124377
No description provided.