Skip to content

Prefer GLES 3 with GLES 2 fallback - #212

Merged
JSUYA merged 2 commits into
flutter-tizen:mainfrom
JSUYA:impeller-gles3-fallback
Nov 5, 2026
Merged

JSUYA merged 2 commits into
flutter-tizen:mainfrom
JSUYA:impeller-gles3-fallback

Conversation

@JSUYA

@JSUYA JSUYA commented Oct 27, 2026

Copy link
Copy Markdown
Member

Flutter 3D scene needs GLES 3; existing GLES 2 devices must still run Impeller.

@JSUYA
JSUYA requested a review from xiaowei-guan October 27, 2026 10:24
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ⚠️ Failed 2026-10-27T10:25:05.846932Z
We couldn’t complete this review. Comment @codex review to try again.
dbc49eb PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Scene needs GLES 3; existing GLES 2 devices must still run Impeller.
@JSUYA
JSUYA force-pushed the impeller-gles3-fallback branch from dbc49eb to bd7d80c Compare October 27, 2026 10:26
@JSUYA
JSUYA requested review from gin7773 and seungsoo47 October 27, 2026 10:26
@JSUYA JSUYA self-assigned this Oct 27, 2026
xiaowei-guan

This comment was marked as duplicate.

@xiaowei-guan xiaowei-guan left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Inline details for the summary review above.

eglCreateContext(egl_display_, egl_config_, EGL_NO_CONTEXT, attribs);
if (egl_context_ == EGL_NO_CONTEXT) {
PrintEGLError();
FT_LOG(Error) << "Could not create an onscreen context.";

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟡 When Impeller is enabled, the first InitializeEGL(3) is speculative: on every GLES2-only device this Error log (and the "No matching configurations found." one above at line 194) will fire even though the ES2 fallback then succeeds and the app runs fine. Error-level logs on a fully-recovered expected path will mislead triage — consider downgrading during the speculative attempt, or logging Error only after all attempts fail. (Summary finding 1)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

As far as I know, most of the TVs we support should be compatible with GLES 3.0.
Based on our agent-based analysis, the only scenario requiring GLES 2.0 is on the Raspberry Pi 3; therefore, such cases are expected to be extremely rare.
If you know any issues regarding GLES 3.0 support on these TVs(old model or version), please share them with us.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Added a check for cases where Flutter 3D is used (--enable-flutter-gpu).

Flutter GPU needs GLES 3, but the engine ships only GLSL ES 1.00 entity
shaders, so FragmentProgram breaks on a GLES 3 context. Keep other
Impeller apps on GLES 2 until the engine provides GLES 3 shaders.
@JSUYA
JSUYA force-pushed the impeller-gles3-fallback branch from b8241a7 to 4d54e83 Compare November 4, 2026 10:51
@JSUYA
JSUYA merged commit fc6478c into flutter-tizen:main Nov 5, 2026
13 checks passed
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.

2 participants