Skip to content

Conversation

@bridgewaterrobbie
Copy link
Contributor

@bridgewaterrobbie bridgewaterrobbie commented Apr 25, 2025

Initial work for CreateTexture and TextureView calls that we will support in this first pass.

BUGS=[403532779]

@bridgewaterrobbie bridgewaterrobbie force-pushed the ebridgewater/wgpuTextureHandlingBegin branch from d185a51 to cc22348 Compare April 28, 2025 17:52
@bridgewaterrobbie bridgewaterrobbie added the internal Issue/PR does not affect clients label Apr 28, 2025
@bridgewaterrobbie bridgewaterrobbie changed the title wgpu: stashing WIP on texture stuff, this is messy wgpu: textures and initial textureview work Apr 28, 2025
@bridgewaterrobbie bridgewaterrobbie marked this pull request as ready for review April 28, 2025 19:35
@bridgewaterrobbie bridgewaterrobbie force-pushed the ebridgewater/wgpuTextureHandlingBegin branch 3 times, most recently from 32af21d to 48801ea Compare April 28, 2025 20:54
@bridgewaterrobbie bridgewaterrobbie force-pushed the ebridgewater/wgpuTextureHandlingBegin branch from 48801ea to d76ce50 Compare April 29, 2025 13:41
@bridgewaterrobbie bridgewaterrobbie force-pushed the ebridgewater/wgpuTextureHandlingBegin branch from d76ce50 to 3f43aba Compare April 29, 2025 21:34
@bridgewaterrobbie bridgewaterrobbie changed the title wgpu: textures and initial textureview work webgpu: textures and initial textureview work May 1, 2025
@jneljneljnel jneljneljnel added the webgpu Issues/features for WebGPU backend label May 1, 2025
uint32_t width, uint32_t height, uint32_t depth, TextureUsage usage,
wgpu::Device device) noexcept {

// First the texture aspect
Copy link
Contributor

@jneljneljnel jneljneljnel May 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean the aspect for the Texture View? wdym here? Is this a helpful comment?

// layout index for efficiency. Add guards if wrong.
entries[index] = std::move(entry);
}
// From createTextureR
Copy link
Contributor

@jneljneljnel jneljneljnel May 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this comment will get stale very quickly when the swapchain uses it, do we need it?

@AndyHovingh
Copy link
Contributor

@bridgewaterrobbie this can be closed now yes? I think this was merged in another PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal Issue/PR does not affect clients webgpu Issues/features for WebGPU backend

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants