[DO-NOT-MERGE] Feat/texture budget - #1284
Draft
kevindecibe wants to merge 4 commits into
Draft
Conversation
kevindecibe
force-pushed
the
feat/texture-budget
branch
from
April 1, 2026 20:56
66a200a to
f77a9df
Compare
Contributor
Test @dcl/inspector package
|
Contributor
Test this pull request on macos-latestDownload the correct version for your architecture:Click here if you don't know which version to downloadFor running this unsigned version of the app, you will need to run the xattr command on it:
|
Contributor
Test this pull request on windows-latestDownload the correct version for your architecture: |
kevindecibe
force-pushed
the
feat/texture-budget
branch
from
April 3, 2026 16:55
f77a9df to
c0807eb
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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
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.
Texture Budget Metrics in CH
Context and Problem Statement
[Describe the issue or background that led to this change. What problem are we solving?]
Solution
[Explain the solution implemented, focusing on the approach and key technical decisions]
Key changes:
Testing
Impact
[Describe the user-facing impact and any potential side effects or considerations]
Screenshots
[Include before and after screenshots or videos if it's a UI feature/fix]