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

[meta] GLES3 backend restrictions #1574

Open
1 of 6 tasks
kvark opened this issue Jun 30, 2021 · 0 comments
Open
1 of 6 tasks

[meta] GLES3 backend restrictions #1574

kvark opened this issue Jun 30, 2021 · 0 comments
Labels
api: gles Issues with GLES or WebGL area: api Issues related to API surface help required We need community help to make this happen.

Comments

@kvark
Copy link
Member

kvark commented Jun 30, 2021

This is spawned from #1510. We are trying to express all the additional restrictions in wgt::DownlevelCapabilities, but some things we don't know how to express, yet. So this issue is meant to track them.

  • GL is inherently single-threaded. It's unclear if it's valid to access an EGL context from multiple threads even if they are externally synchronized. It seems like it could work on some drivers but not the others.
  • each texture is only allowed to be used with at most one sampler (combined) in all the shaders making a pipeline.
  • unable to select mipmap levels and array layers for the views of sampled textures
    • we can modify the texture state to limit the mipmap levels, but this would affect all the views into this texture at once
    • the array layer restrictions could possibly be implemented on the shader side, but this is work
  • unable to interpret 2D array texture as cubes - Handling cube textures in GLES backend #1614
    • currently we detect if it can be a cube map, and make it a cube map. This is a hack we deserve, but not the one we need.
  • base instance is not supported
  • base vertex is not supported
    • exposed as wgt::DownlevelFlags::BASE_VERTEX
    • perhaps, we can still work around it in a way similar to base instance?
@kvark kvark added help required We need community help to make this happen. area: api Issues related to API surface labels Jun 30, 2021
bors bot added a commit that referenced this issue Jul 2, 2021
1584: Update testing limits for rpi4 r=kvark a=cwfitzgerald

**Connections**

Related to #1574. Exposed #1583.

**Description**

Changes the reftesting limits to be tolerant of how the RPI4 renders. Fixes the debug half of #1577. 

Fixes some naming issues as well.

**Testing**

It is


Co-authored-by: Connor Fitzgerald <[email protected]>
bors bot added a commit that referenced this issue Jul 2, 2021
1584: Update testing limits for rpi4 r=kvark a=cwfitzgerald

**Connections**

Related to #1574. Exposed #1583.

**Description**

Changes the reftesting limits to be tolerant of how the RPI4 renders. Fixes the debug half of #1577. 

Fixes some naming issues as well.

**Testing**

It is


Co-authored-by: Connor Fitzgerald <[email protected]>
bors bot added a commit that referenced this issue Jul 2, 2021
1584: Update testing limits for rpi4 r=kvark a=cwfitzgerald

**Connections**

Related to #1574. Exposed #1583.

**Description**

Changes the reftesting limits to be tolerant of how the RPI4 renders. Fixes the debug half of #1577. 

Fixes some naming issues as well.

**Testing**

It is


Co-authored-by: Connor Fitzgerald <[email protected]>
@teoxoy teoxoy added the api: gles Issues with GLES or WebGL label Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: gles Issues with GLES or WebGL area: api Issues related to API surface help required We need community help to make this happen.
Projects
None yet
Development

No branches or pull requests

2 participants