Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Renaming rendering/2d project settings. #46552

Merged
merged 1 commit into from
Mar 1, 2021

Conversation

lawnjelly
Copy link
Member

@lawnjelly lawnjelly commented Mar 1, 2021

The rendering/quality/2d section of project settings is becoming considerably expanded in 3.2.4, and arguably was not the correct place for settings that were not really to do with quality.

3.2.4 is the last sensible opportunity we will have to move these settings, as the only existing one likely to break compatibility in a small way is pixel_snap, and given that the whole snapping area is being overhauled we can draw attention to the fact it has changed in the release notes.

Class reference is also updated and slightly improved.

pixel_snap is renamed to gpu_pixel_snap in the project settings and code to help differentiate from CPU side transform snapping.

projsettings2d

Notes

  • We had a small discussion this morning and generally seemed ok with the idea of fixing this.
  • People using the existing pixel_snap setting will need to set gpu_pixel_snap in the new 2d tab to get the same behaviour.
  • use_nvidia_workaround also changes, but few people will effectively be using this now that batching is the default for GLES2 and GLES3.
  • As usual let me know any suggestions for improvements / better names.
  • It is clear we now have a source of confusion between pixel_snap and transform_snap. Renaming to gpu_pixel_snap is a compromise to try and differentiate the two. It will probably require a page in the documentation to fully go over these options once everything is finalized.

The rendering/quality/2d section of project settings is becoming considerably expanded in 3.2.4, and arguably was not the correct place for settings that were not really to do with quality.

3.2.4 is the last sensible opportunity we will have to move these settings, as the only existing one likely to break compatibility in a small way is `pixel_snap`, and given that the whole snapping area is being overhauled we can draw attention to the fact it has changed in the release notes.

Class reference is also updated and slightly improved.

`pixel_snap` is renamed to `gpu_pixel_snap` in the project settings and code to help differentiate from CPU side transform snapping.
@lawnjelly lawnjelly requested review from a team as code owners March 1, 2021 11:51
@akien-mga akien-mga added this to the 3.2 milestone Mar 1, 2021
@kuruk-mm
Copy link
Contributor

kuruk-mm commented Mar 1, 2021

Nice, I suggest to announce like a rework on the pixel snaps to improve 'Pixel Art Games', that would call the attention to many users to review their settings.

Because there are two new options, and the existing one was renamed.

Right now I saw in https://godotengine.org/article/release-candidate-godot-3-2-4-rc-3
New option to snap 2D transforms to whole coordinates, helps prevent jitter on pixel art camera motions.

@akien-mga akien-mga merged commit 7e2e96c into godotengine:3.2 Mar 1, 2021
@akien-mga
Copy link
Member

Thanks!

@lawnjelly lawnjelly deleted the projsettings_2d_renames branch March 1, 2021 12:54
@akien-mga akien-mga modified the milestones: 3.2, 3.3 Apr 20, 2021
@siddharthroy12
Copy link

siddharthroy12 commented Jun 11, 2021

Where is the transform snap option?
Screenshot_2021-06-11_15-05-12

@lawnjelly
Copy link
Member Author

They were reverted in #46657. See the linked post for more discussion.

For an example of one way of doing pixel snapped 2d retro games, see https://github.com/lawnjelly/godot-snapping-demo.

Elephant34 added a commit to Elephant34/godot-docs that referenced this pull request Aug 4, 2021
Changed the tip on how to enable pixel snapping as it changed in 3.3 (see godotengine/godot#46552)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants