[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-07-27。"],[],[],null,["# Godot renderer options\n\nGodot supports two rendering engines: GLES2 and GLES3. You should choose\nbetween GLES2 or GLES3 when you start your project, and avoid switching if\npossible. Projects can switch back and forth between these two rendering\nengines, but switching requires additional migration work.\n\nOn Android, these renderers use the OpenGL ES 2.0 and OpenGL ES 3.0 APIs\nrespectively. The GLES3 renderer has more sophisticated capabilities and\nfeatures, while the GLES2 renderer is compatible with more Android devices. The\nrenderers also produce slightly different visual output for identical input\nscene data. This disparity is caused by the GLES2 renderer using a sRGB color\nspace while the GLES3 renderer uses a linear color space.\n\nChoosing a renderer\n-------------------\n\n### GLES2\n\nThe GLES2 renderer is most appropriate for 2D or 3D projects with modest graphic\nrequirements, and is compatible with virtually all active Android devices. If\nyour project is designed to run well on older devices, and you intend to support\nthem, GLES2 may be the best choice.\n\nAn important limitation of the GLES2 renderer on Android is that only one\ncompressed texture format is supported: ETC1. ETC1 doesn't support an alpha\nchannel. Other engines may use dual ETC1 textures as a workaround, with one\ntexture containing color data and a second texture containing the alpha channel\ndata. Godot doesn't do this. Projects using the GLES2 renderer on\nAndroid must use uncompressed textures when including an alpha channel.\nUncompressed textures use significantly more memory and don't perform as well as\ncompressed textures. Older devices with limited resources in particular may\nhave issues when using large uncompressed textures, including running into\nmemory limits.\n\nAdvanced rendering features might\nnot be available to the GLES2 renderer. Limitations of the\nGLES2 renderer include but are not limited to:\n\n- Poor performance scaling per active real-time light.\n- Lack of support for rendering features such as high-definition range, refraction properties, screen space reflections, or screen space ambient occlusion.\n- Restrictions on shader complexity.\n- Lack of real-time global illumination support.\n- Lack of GPU acceleration support for particles.\n\n### GLES3\n\nThe GLES3 renderer is compatible with the approximately 90% of active Android\ndevices that have OpenGL ES 3.0 support. Only the oldest of active Android\ndevices lack OpenGL ES 3.0 support.\n\nWhile the GLES3 renderer is compatible with\nany OpenGL ES 3.0 device, be aware that older\ndevices are less likely to run at acceptable\nframe rates. Some older devices also contain graphic driver bugs in their OpenGL\nES 3.0 implementations. The GLES3 renderer on Android has limited mitigations\nfor driver bugs. These issues are less of a concern on newer devices.\n\nThe GLES3 renderer supports the ETC2 texture compression format on Android.\nUnlike ETC1, ETC2 includes support for an alpha channel.\n\nFor more information, see the [Godot Documentation - Differences between GLES2 and GLES3](https://docs.godotengine.org/en/stable/tutorials/misc/gles2_gles3_differences.html)"]]