# Filament render

ApertusVR's main feature is that it is built up from a core-engine and various plug-ins. This implies that it is possible to use different graphics engine for different platforms. So even, ApertusVR mainly uses Ogre render on Windows, the engine responsible for rendering on Android is the open source Google product, called *Filement* .

![](https://4044724383-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LEyKyxZqxfQ560k-THK%2F-MFZS8CpsRsU0m5HwoFY%2F-MFZWrpX1l4aS3qKSO70%2Ffilament_logo.png?alt=media\&token=375e69db-f094-4d7b-a63a-13c2995b38f9)

> *Filament is a real-time physically based rendering engine for Android, iOS, Linux, macOS, Windows, and WebGL. It is designed to be as small as possible and as efficient as possible on Android.*&#x20;

The rendering system on Android is implemented as a Java plug-in (with the use of the Filement engine). Therefore in this guide we will assume that you are familiar with the ApertusVR Java-interface. If this is not the case, please read the documentation on the JNI-plugin:

{% content-ref url="jni-plugin-android" %}
[jni-plugin-android](https://apertus.gitbook.io/vr/plugins-android/jni-plugin-android)
{% endcontent-ref %}

To learn more about Filament check the official github repository:

{% embed url="<https://github.com/google/filament>" %}

The following pages will guide you through to learn how to use, configure, and extend this module of the ApertusVR library.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://apertus.gitbook.io/vr/plugins-android/untitled-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
