-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
GSOC 26: keep bump map slopes correct at image edges #9095
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
Open
Nixxx19
wants to merge
4
commits into
processing:main
Choose a base branch
from
Nixxx19:bump-edge
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+32
−10
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
fed6919
read bump map slopes from both sides so edges don't flatten
Nixxx19 3338f3f
note that maps need to tile to wrap cleanly around a shape
Nixxx19 1f3fedb
Merge branch 'main' into bump-edge
davepagurek 441e131
Merge branch 'main' into bump-edge
Nixxx19 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this apply to other textures like bump maps? Also I think for shapes like sphere() it won't end up mattering because there aren't faces that go past 1 in texture coordinates, so it's probably sufficient to leave out the textureWrap bit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the tiling half applies to any texture wrapped around a sphere, plain
texture()included, so that part isn't bump specific.the
textureWraphalf is though, and i think it does still matter. you're right that no face goes past u=1, but the bump path deliberately samples one texel to each side of the current coordinate to work out the slope, so at u=1 that lookup does read past the edge even though the face doesn't.i just tested it on this branch to be sure, same build and same map, only difference being the
textureWrap(REPEAT)line: without it there's still a visible seam down the sphere, with it the surface is clean. the both-sides change in this pr made it much fainter than it was (one side still clamps instead of both), but it didn't remove it.happy to drop the mention if you'd rather keep the docs lighter, or move it somewhere less prominent. can also post the two screenshots if it's useful to see the difference.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if you have screenshots that'd be helpful for context! but ok if p5 does apply it to all textures including bump textures then that's good, I wasn't sure if it would actually get applied to it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep it does get applied.
bumpTexture()binds through the same texture path as any other map, so whatevertextureWrap()is set to is what the sampler uses when the slope lookup reads past the edge.here they are side by side, same sphere and same map, the only difference is the wrap mode:
left is the default clamp, where the lookup runs off the edge and reads the same texel back, so the slope flattens along that column. right is
REPEAT, where it wraps to the other side instead.