Together with the intermediate deliverable D1.4 (Month 18), this document explains how the RAGE project defines, develops, distributes and maintains a series of applied gaming software assets through a high-level methodology and infrastructure that are needed to support the work in the project, as well as after the project has ended. The asset creation methodology, the quality assurance considerations and the asset metadata requirements are merged together and implemented into a single asset creation wizard, which supports and guides asset owners through the process of asset submission to the Ecosystem portal. It complements the metadata editor that was developed earlier, but which in some respects turned out to be demanding for asset devel...
Demo of the TwoA asset (formerly HAT asset) with the DropEm game in the Monogame engine
In this deliverable, we give detailed description of all end user tools developed in the frame of WP...
This deliverable is aligned with Milestone 15: “Market place implementation and launch”. As part of ...
Together with the intermediate deliverable D1.4 (Month 18), this document explains how the RAGE proj...
This deliverable (D1.4) is an intermediate document, expressly included to inform the first project ...
This deliverable deals with the asset integration methodology employed in the RAGE project. A consid...
This paper describes the structural architecture of the RAGE repository, which is a unique and dedic...
Software assets are key output of the RAGE project and they can be used by applied game developers t...
Deliverable 6.2 describes and summarizes the final results of the population of the RAGE Ecosystem p...
This paper presents the architecture of the RAGE repository, which is a unique and dedicated infrast...
This paper presents the architecture of the RAGE repository, a unique and dedicated infrastructure ...
This paper describes the structural architecture of the RAGE repository, which is a unique and dedic...
This document provides guidance for launching and performing the initial operations of the RAGE Foun...
Demo of the TwoA asset (formerly HAT asset) with the DropEm game in the Monogame engine
In this deliverable, we give detailed description of all end user tools developed in the frame of WP...
This deliverable is aligned with Milestone 15: “Market place implementation and launch”. As part of ...
Together with the intermediate deliverable D1.4 (Month 18), this document explains how the RAGE proj...
This deliverable (D1.4) is an intermediate document, expressly included to inform the first project ...
This deliverable deals with the asset integration methodology employed in the RAGE project. A consid...
This paper describes the structural architecture of the RAGE repository, which is a unique and dedic...
Software assets are key output of the RAGE project and they can be used by applied game developers t...
Deliverable 6.2 describes and summarizes the final results of the population of the RAGE Ecosystem p...
This paper presents the architecture of the RAGE repository, which is a unique and dedicated infrast...
This paper presents the architecture of the RAGE repository, a unique and dedicated infrastructure ...
This paper describes the structural architecture of the RAGE repository, which is a unique and dedic...
This document provides guidance for launching and performing the initial operations of the RAGE Foun...
Demo of the TwoA asset (formerly HAT asset) with the DropEm game in the Monogame engine
In this deliverable, we give detailed description of all end user tools developed in the frame of WP...
This deliverable is aligned with Milestone 15: “Market place implementation and launch”. As part of ...