Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is one temporary solution for parallax jittering, partially fixing #94005.
One way to fix the discrepancy between camera and canvas items with odd motion speeds is by manually setting the camera's position to the snapped value, so anything that depends on the camera's position also gets the snapped value. This is a brute force method and may create problems with other systems, so I'd like to avoid it until we know for sure it wouldn't be an issue, or can find an alternative.
Parallax2D
depends on the camera's position, but sets the node's position every time the camera moves, so there's no harm in passing a snapped value to the parallax node. Until we have a long-term solution, this will prevent jitter for parallax movement while pixel snap is turned on.After:
2024-07-07.10-20-06.mp4