Skip to content

[Merged by Bors] - Fixing confusing near and far fields in Camera#4457

Closed
AronDerenyi wants to merge 11 commits intobevyengine:mainfrom
AronDerenyi:no-camera-near-far
Closed

[Merged by Bors] - Fixing confusing near and far fields in Camera#4457
AronDerenyi wants to merge 11 commits intobevyengine:mainfrom
AronDerenyi:no-camera-near-far

Conversation

@AronDerenyi
Copy link
Contributor

Objective

Solution

  • Removed the near and far fields from the camera and the views.

Changelog

  • Removed the near and far fields from the camera and the views.
  • Removed the ClusterFarZMode::CameraFarPlane far z mode.

Migration Guide

  • Cameras no longer accept near and far values during initialization
  • ClusterFarZMode::Constant should be used with the far value instead of ClusterFarZMode::CameraFarPlane

@github-actions github-actions bot added the S-Needs-Triage This issue needs to be labelled label Apr 11, 2022
@alice-i-cecile alice-i-cecile added A-Rendering Drawing game state to the screen C-Bug An unexpected or incorrect behavior C-Docs An addition or correction to our documentation C-Usability A targeted quality-of-life change that makes Bevy easier to use and removed S-Needs-Triage This issue needs to be labelled labels Apr 11, 2022
Copy link
Contributor

@superdump superdump left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please test the many_lights example with a 3D orthographic camera and log the appropriate near value as extracted from the orthographic projection to check it is correct. :)

Fixed the near value calculation and added comments

Co-authored-by: Robert Swain <robert.swain@gmail.com>
@cart
Copy link
Member

cart commented May 10, 2022

I just independently came to the same conclusion with my recent camera work. I think this is a good call.

Copy link
Contributor

@superdump superdump left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a shame to have to remove the CameraFarPlane option, but it's easy enough to configure a constant far plane instead if you need it.

@superdump
Copy link
Contributor

@robtfm @cart any objections to merging this?

@robtfm
Copy link
Contributor

robtfm commented May 14, 2022

no objection from me. ClusterFarZMode::CameraFarPlane was really only there because it was the way clusters used to work and i didn't want to remove support for it without a good reason. this is a good reason.

@alice-i-cecile alice-i-cecile added the S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it label May 16, 2022
@superdump
Copy link
Contributor

bors r+

bors bot pushed a commit that referenced this pull request May 16, 2022
# Objective

- Fixes #4456 

## Solution

- Removed the `near` and `far` fields from the camera and the views.

---

## Changelog

- Removed the `near` and `far` fields from the camera and the views.
- Removed the `ClusterFarZMode::CameraFarPlane` far z mode.

## Migration Guide

- Cameras no longer accept near and far values during initialization
- `ClusterFarZMode::Constant` should be used with the far value instead of `ClusterFarZMode::CameraFarPlane`
@bors bors bot changed the title Fixing confusing near and far fields in Camera [Merged by Bors] - Fixing confusing near and far fields in Camera May 16, 2022
@bors bors bot closed this May 16, 2022
robtfm pushed a commit to robtfm/bevy that referenced this pull request May 17, 2022
# Objective

- Fixes bevyengine#4456 

## Solution

- Removed the `near` and `far` fields from the camera and the views.

---

## Changelog

- Removed the `near` and `far` fields from the camera and the views.
- Removed the `ClusterFarZMode::CameraFarPlane` far z mode.

## Migration Guide

- Cameras no longer accept near and far values during initialization
- `ClusterFarZMode::Constant` should be used with the far value instead of `ClusterFarZMode::CameraFarPlane`
@DotRed108
Copy link

How do you migrate this if you were previously using .near field

@superdump
Copy link
Contributor

How do you migrate this if you were previously using .near field

What were you using it for?

exjam pushed a commit to exjam/bevy that referenced this pull request May 22, 2022
# Objective

- Fixes bevyengine#4456 

## Solution

- Removed the `near` and `far` fields from the camera and the views.

---

## Changelog

- Removed the `near` and `far` fields from the camera and the views.
- Removed the `ClusterFarZMode::CameraFarPlane` far z mode.

## Migration Guide

- Cameras no longer accept near and far values during initialization
- `ClusterFarZMode::Constant` should be used with the far value instead of `ClusterFarZMode::CameraFarPlane`
ItsDoot pushed a commit to ItsDoot/bevy that referenced this pull request Feb 1, 2023
# Objective

- Fixes bevyengine#4456 

## Solution

- Removed the `near` and `far` fields from the camera and the views.

---

## Changelog

- Removed the `near` and `far` fields from the camera and the views.
- Removed the `ClusterFarZMode::CameraFarPlane` far z mode.

## Migration Guide

- Cameras no longer accept near and far values during initialization
- `ClusterFarZMode::Constant` should be used with the far value instead of `ClusterFarZMode::CameraFarPlane`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-Rendering Drawing game state to the screen C-Bug An unexpected or incorrect behavior C-Docs An addition or correction to our documentation C-Usability A targeted quality-of-life change that makes Bevy easier to use S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Confusing near and far fields in Camera

7 participants