blender
/
blender
134
398
Fork 579
Code Issues 6.3k Pull Requests 754 Projects 19 Wiki Activity

EEVEE Next: Overscan support #110313

Merged
Miguel Pozo merged 6 commits from pragma37/blender:pull-eevee-next-overscan into main 2023-08-03 16:19:17 +02:00
Conversation 3 Commits 6 Files Changed 9 +111 -43
Miguel Pozo commented 2023-07-20 19:10:59 +02:00
Member
Copy Link

Add overscan support for both viewport and final renders.

Add overscan support for both viewport and final renders.
Miguel Pozo added the
Module
EEVEE & Viewport
 label 2023-07-20 19:10:59 +02:00
Miguel Pozo added 2 commits 2023-07-20 19:11:11 +02:00
Miguel Pozo added this to the EEVEE & Viewport project 2023-07-20 19:11:21 +02:00
Miguel Pozo requested review from Clément Foucault 2023-07-20 19:11:28 +02:00
Miguel Pozo force-pushed pull-eevee-next-overscan from 62be001eb0 to 2c86a1fa15 2023-07-20 19:27:47 +02:00 Compare
Clément Foucault requested changes 2023-08-01 12:52:27 +02:00
source/blender/draw/engines/eevee_next/eevee_camera.cc Outdated
@ -133,2 +133,4 @@
}
if ((inst_.scene->eevee.flag & SCE_EEVEE_OVERSCAN) && (inst_.drw_view || inst_.render)) {
float overscan = inst_.scene->eevee.overscan / 100.0f;
Clément Foucault commented 2023-08-01 12:02:14 +02:00
Member
Copy Link

Save overscan into a private member during init. This isn't a parameter that is supposed to change with motion steps.

Also use RE_GetCameraWindowWithOverscan for the render case (where there was a placeholder comment) than create a dedicated function for viewport. I would say define this viewport function as private eevee::Camera method for now, but could be moved to view3D.

Save overscan into a private member during init. This isn't a parameter that is supposed to change with motion steps. Also use `RE_GetCameraWindowWithOverscan` for the render case (where there was a placeholder comment) than create a dedicated function for viewport. I would say define this viewport function as private `eevee::Camera` method for now, but could be moved to view3D.
Miguel Pozo commented 2023-08-01 17:48:21 +02:00
Author
Member
Copy Link

Honestly, I'm not a big fan of splitting viewport/render code like that if it isn`t necessary.
We have plenty of bugs/regressions of features working in the viewport but not on render, and I think duplicating paths like this doesn't help.
Could we maybe have a common implementation, so that both the RE function and the viewport one just call the same function with different parameters?

I'm not sure where it should go, though. In BKE_camera ?

Honestly, I'm not a big fan of splitting viewport/render code like that if it isn`t necessary. We have plenty of bugs/regressions of features working in the viewport but not on render, and I think duplicating paths like this doesn't help. Could we maybe have a common implementation, so that both the RE function and the viewport one just call the same function with different parameters? I'm not sure where it should go, though. In BKE_camera ?
Clément Foucault commented 2023-08-01 17:51:30 +02:00
Member
Copy Link

Yes you can split RE_GetCameraWindowWithOverscan to work with no camera. It is ok if this new function is still inside the RE module.

Yes you can split `RE_GetCameraWindowWithOverscan` to work with no camera. It is ok if this new function is still inside the `RE` module.
fclem marked this conversation as resolved
Miguel Pozo added 1 commit 2023-08-01 17:44:04 +02:00
Miguel Pozo added 1 commit 2023-08-01 19:01:06 +02:00
Clément Foucault approved these changes 2023-08-02 11:19:32 +02:00
Clément Foucault commented 2023-08-02 11:36:14 +02:00
Member
Copy Link

Maybe one last polish you can do, is to reset TAA if overscan changes, because the motion vectors are wrong in this case.

Maybe one last polish you can do, is to reset TAA if overscan changes, because the motion vectors are wrong in this case.
Miguel Pozo commented 2023-08-02 16:37:24 +02:00
Author
Member
Copy Link

Maybe one last polish you can do, is to reset TAA if overscan changes, because the motion vectors are wrong in this case.

Unless I'm missing something, Film::init already takes care of that, since the render_extent and the offset change based on overscan.

> Maybe one last polish you can do, is to reset TAA if overscan changes, because the motion vectors are wrong in this case. Unless I'm missing something, `Film::init` already takes care of that, since the `render_extent` and the `offset` change based on overscan.
Clément Foucault commented 2023-08-03 15:20:07 +02:00
Member
Copy Link

My bad. I think it's only an issue with camera motion blur then.

My bad. I think it's only an issue with camera motion blur then.
Miguel Pozo added 1 commit 2023-08-03 16:18:25 +02:00
Miguel Pozo merged commit 567a2e5a6f into main 2023-08-03 16:19:17 +02:00
Miguel Pozo deleted branch pull-eevee-next-overscan 2023-08-03 16:19:18 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Clément Foucault
Labels
Clear labels   
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
This issue affects/is about backward or forward 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
Issues relating to Wayland windowing support.

  
Interest
Workbench

  
Interest: X11

Issues relating to Xorg/X11 support.

  
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
Issues relating to security: https://wiki.blender.org/wiki/Process/Vulnerability_Reports

  
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 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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
EEVEE & Viewport
Assignees
Clear assignees
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#110313
No description provided.
Delete Branch "pragma37/blender:pull-eevee-next-overscan"

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?