Leaderboard

Cool. The more civs the better. In general we could create a variety of props for each epoch. Then the factions simply get assigned which props they are allowed to use for their buildings and culture. This way Chinese would only be able to construct buildings with for them typical roofs (depending on trade and cultural exchange perhaps others too). Also this would allow to assign each prop a timeframe (starting and end point of time). This would make the factions evolve over time.

Wrong. Prop bones do not record animation.... Name them whatever you want but not "prop-". You'll need to add a skeleton.xml for the balls armature, and use the root to attach them, or whatever the center of the animation is.

An updated version of this guide is available on the Wiki. Introduction This is a guide covering how to export and set up animation files from Blender3D into 0AD as well as some tips and general guidelines for get the animations working in 0AD. The Blender3D version used for this guide is 2.65a newer versions might have problems with the Collada exporter. Last blender version (2.69) works fine for exporting animations. Animations have three main requeriments in order to get them working in 0AD. These are: 1.- The file with the mesh and armature (COLLADA file) 2.- The file(s) with the different animations of the armature (COLLADA file(s)) 3.- The file XML defining the armature (called skeleton in 0AD) with its bones names and hierarchy. The last step is to specify the animations that the unit will have available on its different states in the XML actor file of the unit (i.e. Walk, run, death, idle...) Rig setup: When setting up the rig to animate your mesh, there are a lot of options to configure it to make the animator's life easier and achieve good results with less effort. Sadly, there are some limitations in how much animation and skeleton data the COLLADA format can export. Here are some points to keep in mind when configuring your rig to make animations for 0AD: -Avoid disabling "inherit rotation" in bones. While it's a very nice blender feature, when exporting your animation the bones that have their inherit rotation checkbox disabled end up inheriting their parent's rotation, plus the extra rotation you add in the animation resulting in weird and undesired behaviours. There's a tricky workaround for this, which is creating a helper bone which the bone that you don't want to rotate will copy its rotation. -Make sure the rig have the correct scale, and has its scale applied before start animating. Resizing your rig and/or mesh and applying its new scale before baking the animation may end up messing the animations you may already have, specially if you have any IK (Inverse Kinematics) setup in your rig. Here's a workaround that may or may not work: -Scale to the correct size the mesh+armature file and re-export it. -Export the baked animation(s) to dae with their incorrect size, but correct animation. -Import them back into blender, scale them correctly, and export them back without applying the scale one by one. -Mark the "Clear Constraints" checkbox when baking an action if you use any IK or constraint. Specially if you use constraints like "copy rotation" and "copy location". Once the action is baked without "Clear Constraints", it may appear in blender that it worked fine, but it will not when exported to collada format. -Save your .blend file before exporting. You will lose your rig constraints when baking the animation, plus importing collada animation files back to blender is not working propperly to date (11/24/2013). Because of this, if you want to tweak an animation, or use the same skeleton/rig to create a new one, the only way to do it right now is using the .blend file. In this guilde, we're going to set up the animations for a wild animal unit "Tiger" that will be controlled by the IA "Gaia". 1.- Export the .DAE file with the armature In this step, we're going to use Blender3D to create the first main file needed for the unit's animation. This file tells the engine the relationship between the bones and the mesh. Before this step, you should create in Blender3D the armature (skeleton from now on), and the mesh that is going to use it, apply the skeleton to the mesh and tweak the vertex wheights that each bone will move (this is not covered in this tutorial). Before exporting the mesh and the armature, you should make sure that both objects are centered in the origin point of the scene and both object's origin points locations match. To move the object's origin points to the scene origin point (coordinates 0,0,0) first use "SHIFT+C" this will make your 3D cursor to center into the scene origin, then select the mesh and the skeleton with rightclick and shift rightclick and use "CTRL+ALT+SHIFT+C", in the pop-up menu select "Origin to 3D cursor". Now make sure you remove from the "action editor" any action currently used by the skeleton (if any) and move the timeline back to the first frame if it isn't there. [1b – Optional image removing the action editor's action] Also make sure your skeleton is in the default pose (also called resting pose). To do this, select the skeleton, use "CTRL+TAB" to enter pose mode, hit "A" to select all bones and use "ALT+G", "ALT+R" and "ALT+S" to reset the bone's position, rotation and scale, this will put the armature in it's resting pose. Now we're ready to export the mesh and skeleton. Make sure there's nothing else in the blender scene other than the armature and mesh (remove lights, other meshes, helpers/empties...). In "Object Mode" select the mesh first with rightclick and then the armature with "shift+rightclick" (the order is important) then go to the menu in the top of the screen and use "File --> export -- > Collada (Default) (.dae)" Navigate to the folder where you want the file to be created, name the file and hit enter or click Export. *Note: These "mesh+armature" files are stored in \0AD\binaries\data\mods\public\art\meshes\skeletal\ 2.- Export the .DAE file animations In Blender3D, you have to use the "action editor" to create the different actions (or animations) that you want to export into 0AD to use them. These actions are usually: walk, run, idle, attack, and death, but you can make variations of each one or make more types of actions if desired. This tutorial do not cover how to animate in Blender3D but I'll give you links to animation tutorials and tips for the animations at the end of it. 2.1- Bake the action to keyframes In 3D animation software, you animate inserting keyframes or "posing" your skeleton along a timeline, and then the software computes the space between keyframes with intermediate poses which makes the movement motion. The closer one keyframed pose is to another, the quicker the motion will be from one pose to another, and the further the keyframed pose is to another, the slower the motion will be. To make an animation file readable for 0AD, you have to bake the action into keyframes in Blender. This is the process of creating a keyframe for each frame if a bone has changed its position from the previous frame. This is done automatically by Blender3D when baking the action. To bake an action into keyframes, first select the action to bake in the action editor, then adjust the "start frame" and "end frame" on the timeline to match the action length. After that, select the skeleton, enter in pose mode with "CTRL+TAB" and select all bones with "A". Once you have selected all bones, move the mouse cursor into the 3D viewport, hit "space" to bring the search option menu and type "bake action" then select "Bake Action" in the menu. A menu for the "Bake Action" option will emerge, uncheck "Only Selected" checkbox, !and check "Clear Constraints" checkbox (specially if you use IK and/or constraints) and click OK This will automatically insert keyframes between the poses you used to animate. 2.2- Export the animation .DAE file This is the same process as the first point. This will create the file containing the actual animation that will be played in 0AD's engine. Switch from pose mode to edit mode with "CTRL+TAB" select the mesh first with rightclick, then the armature with shift+rightclick, go to "File --> export -- > Collada (Default) (.dae)" Navigate to the folder where you want the file to be created, name the file and hit enter or click Export. *Note: These animation files are stored in \0AD\binaries\data\mods\public\art\animation\"unit type"\ **Note2!!: Units with different meshes but same skeletons can share these animation files and use it even if the animation files have been exported with different meshes. However, each unit needs to have its own "mesh+skeleton" .dae file that we have created in the first step. Repeat 2.1 and 2.2 for each animation of the unit and name them accordingly (i.e. tiger_walk, tiger_death, tiger_idle_01, etc...) 3.- Create the XML file defining the skeleton 0AD needs a .XML file to define the skeleton's name, bone hierarchy and bones' names. These skeleton .XML files are located in "\0AD\binaries\data\mods\public\art\skeletons\" You'll need one skeleton .XML file for each different skeleton you want to use in 0AD. The easiest way to set up one, is to open an existing file and modify it with the information of the new skeleton you want to add and save it as a new file. You can open .XML files with any text editor software. I recommend notepad++ to do so (personal preference). This is an example of the syntax that you need to use to setup the file correctly: Note how each child bone is defined under its parent bone line before closing the parent's bone definition with "</bone>" The RootBone is the bone in the armature that controls every other bone in it. Note: If you have any bone name in the skeleton containing a dot "." you have to use an underscore "_" in this file instead when writing the bone's name. To know the hierarchy of your skeleton, you can use the outliner window in Blender3D and expand the armature contents. There you can see which is your root bone, and the childs of each one of them. Once you have completed setting up the file, use "save as" and save the .xml file with an appropiate name in the folder specified at the beginning of this section. -Specifiying the animations for the unit in its actor Every unit (or entity) in 0AD has it's own .XML file which contains information that tells the engine different properties of that entity. These files are called actors. Some properties that contains these actor files are: -Mesh: the mesh that will be displayed in the engine for that entity or unit. -Prop(s): Actors can be used within other actors. They're called props. You need an empty/helper/bone with its name starting with "prop-" to specify where you want the actor to be shown. -Variants : These are possible variants of a unit (used for unit diversity) as well as states that a unit may have. -Texture(s): The texture or textures that the mesh will use. -Animation(s): Animations that the unit or entity can use and the variant/state associated with that animation. Animations in the actor files are normally specified just before the <mesh> tag in the following format: The <animation> tags in this example include the location and filename of the animation (created in section 2), the name of the variant/state that will use that animation specified by "name=", and the speed that the animation will play. The animation speed gives you control over the speed that the animation will play independiently of the speed it had when exported from Blender3D. Loading and hiding props during an animation: There's a special case for animations where you can load prop's actors and make them dissapear during the animation. The first animation specified in the example with the variant name "Build" uses this case. You specify with fractional numbers when the prop will show up with "load=" and when it will dissapear with "event=" during the animation. The number "0" means the start of the animation and "1" the end of it. The variants are normally specified after the textures in the actors. Here's the variant definition of "Build" from the previous example: In this example the actor "wood_1_a.xml" is going to be loaded at 25% of the duration of the build animation, and it will dissapear at 75%. You specify where the prop actor will be placed with "attachpoint=" . The attachpoint value needs to be the name of a bone, but it is mandatory that the bone name starts with "prop-". When you specify the prop-bone name you ommit the "prop-" part of the name, but if it's declared in a variant that is going to use "load=" and "event=" you have to start the name of the prop-bone with "loaded-" (in this example, the bone's where the actor is going to appear is "prop-beam". Note*: For static meshes without skeleton, you can use empties parented to the mesh with the name prefix of "prop-". You can later use this empty location to spawn an actor on it's place when defining the props between the <prop> tags right after the <mesh> definition in the actor file. 2015 Edit: - Blender collada export now works better and there's no need to bake the animations even if using IK setups. This reduces considerably the size of the animation collada file. - In order to get clean loops in pyrogenesis, you have to export including the first and last keyframe of the loop. In theory, it is the same keyframe and should be avoided, but the engine needs this duplicated keyframe. In resume: export the first and last keyframe in the animation loop to get a clean looping animation. - Blender now supports "clean channels" option when selecting keyframe channels and deletes the keyframes that do not add anything new to the animation. This reduces the size of the animation file without altering the animation at all. Just select all keyframes in the action editor, hit "X" and select "clean channels" Rigging Tutorials: http://vimeo.com/30073532 http://vimeo.com/30072564 http://vimeo.com/30078317 Animation Tutorials: http://www.cgmasters.net/free-tutorials/epic-looping-idles/ http://cgcookie.com/blender/2011/08/22/animating-a-character-picking-up-an-object/ Import/export 0AD assets and AO baking: http://www.wildfiregames.com/forum/index.php?showtopic=17542&p=273078

RTS and ARPGs are if you look beyond the outer shell actually quite similar, basically you zoom in a bit more, change the controls and add a loot, inventroy and character skills system. So I thought it would be a cool idea to use 0 A.D. as a base for a ARPG like Diablo. Besides the mentioned changes to the code, one would have to have higher quality character models and some simple changes to the AI I guess. Most of the enviromental art of 0 A.D. is good enough to even stand up to a closer zoom, so that would give us a great start. Not sure if caves are possible too with the 0 A.D. engine, but otherwise an outdoor RPG would be sufficient I guess Sadly I am no programmer, but if we would find a team to work on this, I would for sure contribute to the 3D art department. Additionally to that, there could be a cool new cooperative game-play type where you can team up with a few friend and play against an RTS like A.I. to defend your home town or such. I don't think something like that has been done before in ARPGs, so that would be cool to try out. We could also stay true to the 0 A.D. roots and try to make a ARPG without magic in a somewhat accurate historical setting. Obviously not totally realistic, but also a nice change to all the Diablo clones So what do you think? Anyone interested in taking up the task of coding this as a mod?

The Saxons. Only Available during tutorial and Hastings Battle. Yup Indeed but thought it was intentional. What do you need. I can import AI files in 3dsmax.

Salute. Sorry for delay. I see there is not much interest in images. Then just "short" description: I'll upload blender files if everything correct. wolf_pack.zip

Hace rato varios usuarios quieren hacer un Mod mesoamericano, sería bueno Olmecas, Mayas, Zapotecas y Aztecas/mexicas.Sos mexicano. Verdad? ----------- This guy wants to Add Olmecas culture to game in a Mod.

estaba planeando hacer un mod que agregara a los olmecas

voy traducirHe wants be part of modd team. He does 3D models and good scenarios. Trinketos mostranos unas imágenes para poder ver.

Solved/solucionado.

@Hephaestion : Here is the trick. Make three bones. Name them prop-bone001 prop-bone002 prop-bone003. Give them the animation you want. Make an xml with the new skeleton if needed. Then Make another project in blender with the ball. After that, you will just have to put a ball in the xml at the positon of the prop.

Hi guys! Sorry for my inactivity. I have an Osprey e-book about Viking ships. However, I'm currently out of town and is hard pressed to do some reading. Will post, hopefully within this week.

It's usually easiest to use the 3D Cursor to mirror bones. - Position 3D Cursor at the center (Shift+S -> Cursor to Center) - Switch Pivot Point to 3D Cursor (Period Key, or the drop down on the header) - Select the bones that need to be symmetrical - Duplicate (Shift+D) and Cancel (Esc) so bones duplicate but aren't moved - Mirror (Ctrl+M -> choose appropriate constraint: X, Y, or Z, click to confirm) it should use the 3D Cursor as the pivot point. If you name things using .L or .R you can use the Flip Names option in the Armature Menu. It'll change Arm.L to Arm.R for you, but only works with that exact naming syntax.

Texture WIP

Sorry for the late reply, weekend and wife and all @Hephaestion's 27 March reply: I was thinking that the tie up of the children to houses is necessary, to have players who create more houses have more children, and since you've said that a similar cap is already implemented, then that would make it easier to implement. I like too the moving outside the house/ community, and resorting to banditry. That would definitely make for a much more immersive "city-building" feel to the game. I like it! I would also like that technological "spill" to neighboring tribes. But I'd suggest that technological "spill" be more pronounced if a certain tribe is in direct contact of the source, compared to ones that are not in contact or an enemy. Surely a tribe which is friendly would get more access to the technology than a tribe that is hostile. As to history, well, we humans never learn. We are bound to repeat history, unless the Annunaki arrive at last. I am also drawn to the TW series because of the real time battles, like stan said, and their ability to recreate historical battles using formations/ morale and such. The sieges too are worth its playtime. With 5% luck and 101% hardwork, 0 AD will hopefully become the standard of modern RTS for years to come, just like Romulus says.

If you want some suggestions about the texture, -As I said in post #17 in this thread, the sail is always propped to the ship, so you can have more room for the actual ship texture. (They use different texture files) -Texture size you posted is not squared (it is 1165x1028), the game do not allow texture resolutions that aren't powers of 2 (256x256, 512x512, 1024x512, 256x1024 ....) -Small/Medium boats use 256x256 or 512x512 textures, I guess you aimed here for a 1024x1024, wich is good, just scale down and done, but the fact that the props texture (Barrels and crates) has such small texture space, it will make the props look very low-res compared with the deck/hull when scaled down. - Red stripes on the cloth should be transparent if you were aiming for playercolor. The last section on this post explains very well how playercolor works: http://www.wildfiregames.com/forum/index.php?showtopic=18340&p=286095 - Texture distribution could be better, things like the yellow flower of the tail don't need such a big portion of the texture if there isn't any detail on it (plain color) Which btw I think playercolor there would look cool Also the row could be rotated so it's perpendicular to the bottom and not placed in diagonal, which eats a lot of unnecessary space. Not a big fan of the wood texture in the head and tail, but that's personal preference. I hope this do not sound too harsh, they're just points for you to improve.

Final commit from me. Boat.7z

Hmmm, the siege wall towers have 10 crush armour, while regular wall towers have 5. So that makes the sieges less effective against them. Maybe we should start with fixing that