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

Map depth image in Unorm16 for full range #2016

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

dfriederich
Copy link
Contributor

The mapping from Unorm16 encoded depth images did map half of the range to the max color value, hence causing that the same gray tones were used twice, for values < 0.5 (0x8000 before unorm), or >= 0.5. Fixing the normalization to linearly map the whole range.

The mapping from Unorm16 encoded depth images did map half of the range
to the max color value, hence causing that the same gray tones were used
twice, for values < 0.5 (0x8000 before unorm), or >= 0.5.
Fixing the normalization to linearly map the whole range.
@ci-tester-lunarg
Copy link

Author dfriederich not on autobuild list. Waiting for curator authorization before starting CI build.

@dfriederich
Copy link
Contributor Author

With this fix:
image

@ci-tester-lunarg
Copy link

CI gfxreconstruct build queued with queue ID 367658.

@dfriederich
Copy link
Contributor Author

I tried copying how it looked before, but somehow I fail (maybe some company firewall, but it did let me add the image above, odd). Anyhow, before this PR, the middle grays in the image above were dark black, then immediately afterwards some white area. While it is interesting to see the specific depth of 0x8000 so clearly, it did confuse me, I did not understand where this black to white border in some of the part of the image is from.

@dfriederich
Copy link
Contributor Author

(restarted the browser. This is how it looks without this PR)

image

@ci-tester-lunarg
Copy link

CI gfxreconstruct build # 6039 running.

@ci-tester-lunarg
Copy link

CI gfxreconstruct build # 6039 failed.

@bradgrantham-lunarg
Copy link
Contributor

bradgrantham-lunarg commented Feb 8, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants