KTX2 Texture Viewer#275
Open
christinaqiu3 wants to merge 14 commits intoAnalyticalGraphicsInc:masterfrom
Open
Conversation
…rrors The code is trying to find a server/server.js file but when I ran npm run compile it never was built. I just removed it since our extension doesnt need it for now.
…the server activation (thus any changes are unneeded)
… of ktx2hdr.openWebgpuDemo
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
We’re submitting this PR to introduce a new KTX2 Texture Viewer integrated directly into the glTF VSCode extension’s preview panel. This feature adds a dedicated “Open KTX2 Viewer” button that enables users to inspect .ktx2 textures with a range of visualization and analysis tools. The viewer is implemented using WebGPU, providing accurate, real-time visualization of compressed GPU textures.
This work is still a work in progress, but we’re submitting it now to gather early feedback, ensure we’re aligning with the project’s expectations, and to deliver the integration as part of our course final for Shehzan. We’d greatly appreciate any suggestions on architecture, UX, UI consistency with the extension, or general code quality. We plan to continue refining and simplifying the tool for end users after this initial submission.