From EncyclopAtys
| Line 72: | Line 72: | ||
| − | + | [[Category:Development Team]] | |
| − | |||
{{Portal Forge}} | {{Portal Forge}} | ||
[[Category: Tutorials]] [[Category:Dev]] | [[Category: Tutorials]] [[Category:Dev]] | ||
Revision as of 20:53, 14 September 2019
•
•
•
•
•
Contents
Roles of the group
- Creation of programms (conception, update, coding)
- Providing the Ryzom and NEL tools from RyzomCore for the various platforms
- Integration of the creations in a set exportable to the Ryzom server.
Volunteers joinable on IRC
- Emiro (DE/EN)
- Kervala (FR/EN)
- Madi (FR/EN)
- SIELA1975 (EN/DE/FR): programmation in C++, java and Objective-C.
- Shikitiwa (FR/EN)
- YannK (FR/EN)
- Zorroargh (FR/EN)
Dev Contact for Ryzom Core on IRC
- Botanic (Responsible: Web Services (AMS))
- Dfighter (Responsible: Ryzom Core Studio (previously OVQT))
- Kaetemi (Responsible: Asset Build Pipeline, 3ds Max Plugins, Sound, 3D)
- sfb (Community Lead, Responsible: Ryzom Core Wiki)
Tools
- Test server (Yubo) access: http://forge.ryzom.com/wiki/Yubo_accounts
- Ryzom Arkitect (Ark): http://forge.ryzom.com/wiki/ARCC_intro_EN
- Sheetids of all spawnable objects : http://forge.ryzom.com/all_spawn/
Meetings reports
TODO list
- Help Ryzom Core team to polish RyzomCore Studio and its plugins (old OVQT), fix bugs and propose recent compilated version of the tool and plugins for all platforms (Windows/Linux/Mac). We really need efficient tools if we want to attract non-developper peoples, and there is not enough people in Ryzom Core nowadays to developp and debug the tools.
To know more about Dev/Integration
To integrate the creation of the other poles in an exportable kit towards the Ryzom server, we will need to make the tools and infrastructures necessary to the developement of the zone available to the community of the project.
Making the Ryzom, NEL and RyzomCore tools available on the various platforms (OVQT/WorldEditor). It would be sad not to take advantage of the extended user base of those tools to stabilize or improve them, taking advantage of the users feedback and their patches. With that in mind, a coordination with the RyzomCore group would be a plus (especially since a GSoC project about the adjustment and improvement of OVQT has been approved for 2014). The Ryzom Core team publishes stable releases at https://ryzomcore.atlassian.net/wiki/display/RC/Downloads.
- The graphic pipeline: this comprises the tools and scripts permitting the generation (but not only the generation) of the client's graphic files. This pipeline uses 3DSMax to export 3D models towards NEL. Two approches are envisioned here:
- Client comp solution: as for the NEL/Ryzom tools, we need to make available to the community a way for everybody to configure at home a pipeline for the files necessary to the server. We also need to provide an adequate configuration for the New Zone project and a unified assets base.
- Server solution: the Ryzom pipeline configuration isn't a meager task. In addition, it requires a owner tool. The 3D modelisation being mostly the field of an artist community whose not necessarily all that good with informatics, the idea is to propose a "pipeline" public server permitting the automatic generation of the NEL files following the sending of the originals by this community. Take note that offline tools like OVQT permits us to see those 3D models in NEL format without needing to place them in a game server.
The pipeline's scripts have already been ported to Python by the Ryzom Core team and work under Linux.
3ds Max 9 has been successfully used with NeL plugins under Wine by the Ryzom Core team. Instructions are over at https://ryzomcore.atlassian.net/wiki/display/RC/3ds+Max+on+Linux. For usability, it is required to patch Wine with the following patch to fix a bug in Wine http://bugs.winehq.org/show_bug.cgi?id=31434.
- The test server: the organisation surrounding a test server depends on the choice made for its hosting: either on the Ryzom test server or by the community. The experience of the Khaganat team could also be adapted to this project. The have a virtual machine (VM) virtualbox with a game server that could function at the same time as a game client on a user computer for testing. This VM also disposes of a script to regenerate the client's datasheets of the game without needing to use the pipeline (except for the graphic files). It's used by the members of the project Khaganat for their object insertion tests and the elements of the world: armors, mobs, etc.
The Ryzom Core team has designed the assed build pipline in such way that it can selectively build subsets of the game data (such as leveldesign sheets) by adding specific parameters to the build command. Batch scripts are provided for your convenience.
