Develop and Download Open Source Software

Android Game Engine

We call for your help with the Japanese translations for project summaries. The submitted translations will be posted after simple evaluation. (Not only the translation itself is going to be checked, but we also make sure it's clear of wiki format problems. Especially problems that are related to the layout, such as line breaks and links, will be checked, so please give heed. When there appears to be a problem with the translation itself or the layout, we may not be able to post your translation. We often see problematic cases related to links. When there's going to be a line of Japanese text right after the URL, please make sure to leave a space to separate.) Also, even with projects that may already have their summaries translated, if you find an outdated translation or typographical errors, please update. Login to start translating. When you are done, you will find your name at the bottom of the summary as the translator.

You are not Logged in. If you submit this translation, your name will not show on the this project page (will be logged as "translated by an anonymous user").

Project Description:

English:
(Last Update 2014-03-28 08:04)

AGE is a multi-threaded game engine for Android using OpenGL ES2 shader-based rendering.
In-depth GL knowledge is not necessary to get started; use the OBJ loader to bring in your favorite models from Blender and elsewhere, attach textures, and start rendering!
Threads are used strategically to partition different activities, e.g. initialization, framerate, timer, game cycle.
Threads use the apartment model, and communicate by message passing.
The drawing cycle is inverted from typical game loops. AGE uses a dedicated timer for framerate, and the SurfaceView is in on-demand rendering mode.
Game components opt-in to system services by implementing the "marker" interface corresponding to the service.
Game components enter the system via Install Pipeline, an asynchronous "standard" implementation that keys on the marker interfaces and performs the "protocol" for that marker. There are also Event and Uninstall pipelines.

No Japanese Translated Data
Japanese: