Android (32-Bit / 64-Bit)
Gorilla3D supports both Android 32-Bit (ARMv7) and Android 64-Bit (ARM64-v8a) as deployment targets. The renderer is OpenGL ES — version selection depends on the Delphi IDE you compile with.
Since August 2019 Google requires every new app and every update on Google Play to ship a 64-Bit binary. Producing a single 32-Bit-only build is therefore no longer an option for production releases — always deploy at least an ARM64-v8a APK / AAB.
OpenGL ES Versions by Delphi
| Delphi version | Default OpenGL ES | Notes |
|---|---|---|
| Delphi 10.1 / 10.2 | ES 2.0 | Render passes are limited; advanced post-processing is not available. |
| Delphi 10.3.x | ES 3.1+ | Requires NDK API level 21+. Order-Independent Transparency available since v0.8.1. |
| Delphi 10.3.3 | ES 3.1+ | Defaults to NDK API level 22. |
| Delphi 10.4 / 11 / 12 / 13 | ES 3.1+ | Recommended — full feature parity with Windows where the GPU allows. |
Important: Compilations with IDE versions older than 10.3.3 are considered deprecated for Android. We strongly recommend upgrading to the latest IDE before targeting Android.
NDK Configuration
Gorilla3D needs OpenGL ES 3.1, which requires NDK API level 18 at minimum and API level 21+ for Order-Independent Transparency.
- Open Tools > Options > Deployment > SDK Manager.
- Select your Android SDK and switch to the NDK tab.
- For every entry below
android-18, replace it with at leastandroid-18. - For Gorilla3D ≥ 0.8.1 set the minimum to
android-21.
If the linker complains about missing GLESv3 symbols (libGLESv3.so), the NDK API level is still too low — repeat the steps above and clean / rebuild the project.

AndroidManifest Configuration
Declare the OpenGL ES feature inside AndroidManifest.template.xml so the Play Store filters the APK to compatible devices:
<uses-feature
android:name="android.opengl.opengles"
android:glEsVersion="0x00030001"
android:required="true" />
If you target ES 3.2 features explicitly, change 0x00030001 to 0x00030002.
Build & Deployment
- Switch the Target Platform in the Project Manager to Android 32-Bit or Android 64-Bit.
- Select Release when producing store builds; Debug is fine for development on a tethered device.
- Use Project > Deployment to add your model files (
.gorilla,.glb,.gltf, …) and shaders to theassets\internal(or\library\lib\armeabi-v7a/arm64-v8afor native libs) destination. - Sign the APK / AAB through Project > Options > Provisioning before uploading to Google Play.
Native libraries
If you use third-party native libraries (FMOD, Jolt, …) make sure both the armeabi-v7a and arm64-v8a variants are deployed when you ship a universal APK. Mixed bitness will not load on the device.
Verified Feature Matrix
We test on two reference configurations:
- BlueStacks (Android 64-Bit, x86_64 emulator backed by host GPU) — used as a baseline since it can be reproduced reliably on developer machines.
- Google Pixel 9 running Android 16 — the latest hardware available to us at release time.
Legend: ✅ working — ❓ partially / not verified — ❌ not working / known issue
| Feature | BlueStacks (Android64) | Pixel 9 / Android 16 |
|---|---|---|
| FMX Primitives | ✅ | ✅ |
| FMX MaterialSources | ✅ | ✅ |
| Gorilla3D Primitives | ✅ | ✅ |
| Gorilla3D Model | ✅ | ✅ |
| Gorilla3D Model — STATIC | ✅ | ✅ |
| Gorilla3D Model — Uncached Animations | ✅ | ✅ |
| Gorilla3D Model — Cached Animations | ✅ | ✅ |
| Gorilla3D Model — Instancing | ✅ | ✅ |
| Texture formats other than BGRA | ✅ | ✅ |
| Default Materials (Lambert, Phong, BlinnPhong) | ✅ | ✅ |
| Sharing a G3D material with multiple objects | ✅ | ✅ |
| Cross-Material (FMX ↔ G3D) | ✅ | ✅ |
| Pure Color material | ✅ | ✅ |
| VertexColor material | ✅ | ✅ |
| No-Lighting tests | ✅ | ✅ |
| POM material | ✅ | ✅ |
| PBR material | ✅ | ✅ |
| Atlas material | ✅ | ✅ |
| SplatMap material | ✅ | ✅ |
| Layered materials | ❓ | ❓ |
| Layer3D / Layout3D | ❓ | ❓ |
| TextLayer3D | ❓ | ❓ |
| Material Behaviours — fragment shaders | ✅ | ✅ |
| Material Behaviours — vertex shaders (wobble, wind) | ✅ | ❌ only intermittent |
| Depth render pass | ✅ | ✅ |
| Blur render pass | ✅ | ✅ |
| EmissiveBlur | ✅ | ✅ |
| Global Illumination | ❓ | ❓ |
| WBOIT rendering | ✅ | ✅ |
| Composite rendering | ✅ | ✅ |
| OutputLayers | ✅ | ✅ |
| Skybox (Procedural / Blank / CubeMap) | ✅ | ✅ |
| Reflection render pass | ✅ | ✅ |
| Refraction render pass | ✅ | ✅ |
| Environment mapping | ❓ | ❓ |
| MSAA | ❌ | ❌ |
| FXAA | ✅ | ✅ |
| PostFX (with concat) | ✅ | ✅ |
| User shader via VertexShader / SurfaceShader | ✅ | ✅ |
| Water surface material | ❌ crashes when assigning textures | ❌ crashes when assigning textures |
| Particle system — untextured | ✅ | ✅ |
| Particle system — textured (smoke emitter) | ❌ rendered too dark | ❌ too dark; black fragments at blending edge when zooming out |
| Volume rendering | ❌ | ❌ |
Known Issues
- MSAA is not available on Android. The driver path falls back without anti-aliasing. Use FXAA as a screen-space alternative — it is verified to work on every tested device.
- Water surface material crashes when textures are assigned at runtime. This is being investigated; do not ship the water material on Android until a fix is published.
- Textured particle systems (smoke emitter) render noticeably darker than on desktop and may show black fragments at the blending edges on Android 16. Untextured particles work as expected.
- Vertex-shader behaviours (wobble / wind) on Android 16 / Pixel 9 are only applied intermittently — likely a driver-side optimization issue. The same shaders work on BlueStacks.
- Volume rendering is currently disabled on Android due to texture-binding and 3D-texture-format limitations on most ES 3.1 drivers.
Common Errors
- Linker error: undefined reference to
glXxx(GLESv3)
NDK API level is below 18. Increase the NDK level in Tools > Options > Deployment > SDK Manager > NDK, then rebuild. - Black screen on launch
The selected GPU does not advertise OpenGL ES 3.1 — verify withadb shell dumpsys SurfaceFlinger | findstr GLES. - App rejected by Google Play (32-Bit only)
Add the Android 64-Bit target platform and produce an AAB containing both ARMv7 and ARM64 binaries. - Textures appear flipped or red/blue swapped
Make sure the texture format is supported by the device. Many Android GPUs do not accept BGRA — Gorilla3D converts automatically, but custom shaders need to handle channel order.