Jump to content


0 A.D. Art Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Enrique

  1. Enrique

    Art Dev. Task tracking

    Last updated 08/03/2018 This thread is to keep track of the Art tasks that needs to be done and who is working on which one. Keep it clean, post only when you are going to start a task and when it has been finished and approved or commited by someone of the team. - Do not post suggestions. Create a new topic or use any suggestion thread. - Do not post Wips. Create a ===[TASK]=== thread on the Art forum for this matter. - Do not post references. Use the relevant task thread. - LEGAL WAIVER: Please read this before contributing and abide by it. *We can't assure that your models will be used for the final game, and we n 're also looking for a certain quality level, don't get upset if your model doesn't make it into the game, practice is the best way to improve. Useful links: How to Import/export assets and bake AO maps in Blender3D Blender 3D UV unwrapping tips How to export animations from Blender3D to 0AD Tips & requirements of the engine: - Approx triangle count for buildings: small 2k-5k, mid 4k-6k, big 6k-8k, wonders 8k-12k. - The engine uses .DAE (Collada) format for models and animations. - The engine does not render double-faced polys, so if you want a polygon with both faces rendered, you need to duplicate it and flip the normals. - The engine does not tile the textures like blender does, so when UV mapping, keep the UV islands within the texture space. - We use two UV coordinates, one with overlapping UVs for diffuse, normal/parallax and specularity and another non-overlapping for AO maps. - Building models need to extend below the ground (-Z axis) because it can be visible when the building is constructed in uneven terrain. - To get the correct scale it is very useful to import a building from the game into blender as a reference. SIMPLE TASKS ESSENTIAL TASKS BUILDINGS UNITS UNITS ANIMATIONS OPTIONAL TASKS BUILDINGS PROPS ANIMALS FLORA GEOLOGY UI
  2. Enrique

    0AD units upgrade

    Wildfiregames presents: 0AD's unit upgrade. -Why do you work on this upgrade when you should be working on pathfinder and performance improvements? -Please note that this upgrade has been done by an artist who hasn't any knowledge in programming. This upgrade has not taken away any precious work time to 0AD programming developers who continue to work on the needed pathfinder and performance improvements. -Why do you make this upgrade? For a number or reasons: Unit models are very old, around 6-7 years old. These new models are closer to today's industry standards. UV mapping and model proportions aren't ideal on the current models. The new ones have realistic human proportions and much better UV mapping. Old animations cannot be modified, only created from scratch. With the new models we can maintain the blender source files of the animations and modify them at will. Since we share the blender source files, the team and the community can make variations for their own model variations and still use the new armature. Old model's armature (skeleton) is very basic and limited. With the new model's armature we can achieve more detailed animations and are capable of basic prop animation -Are these new models already implemented? Do they work with the old animations? -No. The models are finished and ready to start animation production. We will remake all the unit animations and implement them when there are almost all of the required animations completed. However, the models are commited to the SVN version of the game with some test examples that you can check in the map editor. These examples and the models will be released in the next Alpha release (Alpha18) if you don't wan't to set up a SVN version. To check some unit examples in SVN, go to the map editor and in the object tab, search for all actors and filter by "newunit". Once selected click on "Switch to action viewer" to isolate the unit and zoom in. (please note these are just examples and they aren't final unit setups) -Do you have increased the number of unit variations of the game? -Yes, now there are non-armored unit variations, and armored unit variations with some differences. There are plans to add some more in the near future if time permits. -Can I make my own animations for my mod and use these new models? -Yes you can! Check at the bottom of this post to download the blender source file(s) of the armature and check the SVN newunit xmls example for setting up your own units. Don't forget to check the presentation video where there's a short explanation of how the armature works. -What is left to be done before I can play with these new models? -Since the unit heads have different size than the old ones, all the helmets in the game must be resized to fit them. Also as pointed a few lines above, we're going to upgrade all the animations to fit these new models. When these two tasks are complete or close to completion, we'll implement them and you'll be able to play 0AD with them. -Is there something I can make to help with this task? -Yes! If you are a skilled animator with experience in human models' animations you can open a thread in "Applications and contributions" subforum, tell us about yourself and show us some of your animation works! Male unit variations (Old Work in progress): (Click following images to enlarge) Female unit variations (Old work in progress): Download the blend file and start animating! Enjoy! New unit upgrade animation template.zip
  3. 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
  4. Introduction This is a guide covering how to import assets from the game to blender, create a second UV coordinates, bake the AO maps and export again. The game's buildings are usually divided in different .dae files (one per diffuse texture used) Usually, they consist in one main ".dae" file located in "meshes/structural" and one or more ".dae" children (props) that are attached to the main file, this "prop" daes are located in "meshes/props". (this is not always the case) In this example, we're going to bake the AO map for the celtic civil centre. 1.- Import the mesh into blender3D Inside blender, remove the starting cube, camera and point light. Go to file->import-> Collada (.dae) and select the .dae file to import. This building consists on three files: celt_civic3.dae, celt_civic3_props_1.dae and celt_civic3_props_new.dae If blender shows an error importing: *Note: The file may be imported rotated -90º in the X axis. To solve this, simply center the pivot point at the origin with SHIFT+C, select the cursor for your pivot point, select the asset and hit "R" for rotate, "X" for the axis, and then type "90" on the numpad and hit enter. Each time you import an asset, it is important that you create a new material with the name of the .dae or the texture that is going to use if you know it. This will let us separate the object again after we join all the meshes together. 2.- Set up a new UV coordinates. Select all your meshes and join them with CTRL+J Go to "object data" panel, scroll down to UV Maps menu and click the "+" sign to create a new UV coordinates. --Select the building, enter in edit mode with TAB. --Open a window with the UV/Image editor. Click in "new image" and "ok" in the pop-up menu. This creates a new 1024*1024 black image where we will bake the Ambient occlusion. --Now let's unwrap the model automatically. Go to object mode, select the model, use "CTRL+A" and select "apply scale" this will recalculate the scale of our building, so the polygons could be unwrapped nicely. --Enter "edit mode" with TAB. select all with "A" and hit "U" and select "Smart UV Project" in the pop-up menu. --In the next menu select the following settings: 3.- Baking the AO into our new generated black image. Preparing the AO settings: go to the "world" tab in the settings panel, mark the checkbox of Ambient occlusion and set it to "multiply". Scroll down to the "Gather" pannel and change the samples to something between 20-25 --We have the model ready to bake the AO map. Go to the render tab, scroll down to the "bake" panel (click on the "bake" pannel if it is closed) and use the following settings: --Then click "bake" and wait until the baking process is completed (this will take a while depending on your machine) --Once finished, you can hit "N" in the viewport to open a toolbar, go to the "display" menu, and click in the "texture solid" checkbox. This way you can see the AO map we have just generated on the model and check if it has been correctly generated. ------If you see black strange black faces where it shouldn't, the polygon normals are probably facing the wrong direction. This could be fixed selecting the black faces and then hit "W" and select in the pop-up menu "flip normals". ------If you find the problem where there are dotted black parts, it's probably because there are two or more polygons overlapping each other. You'll have to tweak the model sightly to fix this issue. --Once the bake is finished and you're happy with it, remember to save the image generated so it doesn't get lost. In the UV editor select Image->save image As... 4.- Separating the mesh by materials Now that we have our AO map, and the model has a second UV coordinates for the AO, we have to separate it's pieces again and export the parts one by one. To separate by materials, enter "edit mode". Make sure you don't have anything selected hitting "A" twice. Go to the materials tab, select the first material on the list, and click "select" button. This will select all the faces that have that material assigned. Once selected hit "P" and select "selection" in the pop-up menu. Repeat this step for each material (prop) you have imported. NOTE: Now that you only need to export the objects into .daes again, is a VERY NICE moment to save the .blend file in case the export process goes wrong. 5.- Exporting the meshes back to .dae files. This is the last part. You have to export the objects one by one. Make sure the following requirements are met: - There's nothing else on the scene except the mesh you want to export (even hid objects breaks the export) - You have to remove every material applied on the mesh. - There are no lights, armatures or other objects in the scene. - You have your object selected. Then you simply go to File->export-> Collada (.dae) and select the file to export or overwrite the old one. After that, reload the .blend file and repeat this step with the rest of the objects (or hit CTRL+Z a few times until you get back the other meshes and repeat the process with the next one) I hope it's somewhat understandable and useful .
  5. I've been gathering swordfighting techniques as well as other weapons used in 0AD's timeframe to have references for animations that the new meshes will have. I try to look for realistic/historical techniques rather than hollywood/coreographed moves. I have quite a big list so far, but I thought posting some of them in case someone is interested in fencing techniques... there are some videos that explain well the uses of shield as well as lost techniques that were probably used, as well as slow, easy moves where its easy to extract nice poses and basic stances. I enjoyed (and learned) a lot while watching them and I think they're quite interesting, so here they are: Ancient archery technique: https://www.youtube.com/watch?v=M1KC1Os-_NE Viking bigshield techniques:
  6. Needs to be for 2 passengers, anchor for 4 horses. Just the chariot no horses. Bonus: textures for the two units in the first image: Hey! here is some help in how to create textures in Blender!
  7. We will need textures for units of the following fellas: -Guy in the right with the "armpit-level-skirt" And from here the fully-armored gentlemen: (note the right one also has futurama-bender-like plating in the arms) Here's some help and ideas to create the textures! easy and fun!
  8. Please use this thread to report any issues with the new unit meshes and animations commited recently. It was a big commit so it may have some stuff that needs fixing.
  9. The mesh is full with NGons. Collada and game engines doesn't like NGons. Solution: Triangulate the mesh before exporting. -Select the object -Go to edit mode with TAB -Go to face mode select with Ctrl+TAB, choose face selection from the pop-up menu -Press "A" to select all the faces -Press Ctrl+F to open face specials menu, choose "triangulate faces" Ngons should be replaced by triangles now and is safe to export. ---------------------------------- El objeto está lleno de NGons. (NGons son polígonos con más de 4 vertices). Al formato collada y a los motores de juegos no les gustan estos polígonos (no son compatibles). La solución es convertir los NGons en triángulos antes de exportar el objeto. -Seleccionar el objeto -Ir al modo edición con la tecla TAB -Presionar Ctrl+TAB y elegir el modo de selección de caras/polígonos. -Presionar "A" para seleccionar todos los polígonos. -Presionar Ctrl+F y seleccionar "triangulate faces" en el menu que aparece. Ahora los NGons deberían haber sido reemplazados por triángulos y debería funcionar al exportar. Recuerda quitarle cualquier material asociado y borrar todos los objetos salvo el que quieres exportar de la escena como ya comentó Lion.
  10. Enrique

    Animation Mesh Switch Out

    Here's the link to the online SVN repository. -> http://svn.wildfiregames.com/public/ps/trunk/ It's like 0AD folders and files, just navigate to the folder you need the file from, then rightclick, save as and boom, you have the dae file without copying/pasting the whole code. http://svn.wildfiregames.com/public/ps/trunk/binaries/data/mods/public/art/animation/biped/new/ That would be the folder with all the new animations for the new meshes. New animations can be done with the blendfile of the animation template. Just create a new action, animate the stuff, and export it. All new meshes (like your new tunic variation) can use those new animations.
  11. Enrique

    Animation Mesh Switch Out

    You don't need to go through each bone, you only need to do it for the new vertices you created for the tunic, the rest of the mesh maintain its bone weights, so only the few new vertices you created need weight painting. Glad it worked. Please take a look to the new meshes actors, the prop-bones have different names than the old meshes ones.
  12. Enrique

    Animation Mesh Switch Out

    What process did you follow to get there?. Are you re-rigging the whole thing with automatic weights? If you do so, you'll need to uncheck "deform" in the bone options tab for every bone that is not used in deformation, like the knees target, elbows target and all the prop-bones. Otherwise blender may assign weights to bones that are there only to help animating, not deformation thus the game thinks that there should be more bones to do the animation. Ideally you should: -Import the mesh that you want to modify. -Erase the armature that comes with it, then modify the mesh as desired. -Once you got your tunic variation, append the armature from the blendfile provided earlier. -Add an armature modifier to the mesh and choose the appended armature. -Move the bones to see your new vertices are assigned to any vertex group, and if not, do it manually (the changes are not big, so you won't have to spend much time with it) If you do automatic rigging, you may add vertex groups of bones that are not declared to deform the mesh and errors will occur. -Export.
  13. Enrique

    Animation Mesh Switch Out

    If you want to do your model from the new unit models that will debut in the next alpha, you can grab the animation template at the end of the following post: Use the same process as the previous post, but with this blendfile. If you prefer to start modifying from a different (longer tunic) variation than the one on that blendfile, you can choose from the following (they're named the same as the old variations): http://svn.wildfiregames.com/public/ps/trunk/binaries/data/mods/public/art/meshes/skeletal/new/ Just remember to rig it to use the armature from the blendfile, not the one that gets imported from the collada files and it should work.
  14. Enrique

    Animation Mesh Switch Out

    There are some steps there that may generate the issues. Specially importing the used armature from a collada file to export it back (bones are often broken) If you have the mesh already done, rig it to the following armature in the blendfile that you can find in this post: This way you have the armature "as it was created in blender" without importing it. Just assign the vertex groups (do the rigging) of your mesh to the armature found in that blend file and export. Let me know if the issue persists. EDIT: Keep in mind that modifying the hero mesh for your longer tunic variation will make only compatible with the hero UV textures (heroes have different UV layouts than the standard unit) That's the reason why in your image (although it is broken due to the collada export) you can clearly see that one foot is correctly mapped, but the other is not.
  15. Wtf Lion you've seen how the engine has been developed from different people and how art has evolved over time to get advantage of the changes. It was built from scratch. Also it was already pointed that the aoe engines were propietary so it isn't even possible to take stuff from it. I don't see any other similarities it could have other than art style legacy and rts camera. Almost all 3d games use dynamic lighting for example and that doesn't mean that one game is similar to another.
  16. A good starting point would be adding the armour of the legs and trump in the elephant skin texture, and then do the armour of the right side of the texture with gold/bronze plating. Useful textures; binaries\data\mods\public\art\textures\skins\skeletal\maur_elephant_hero.png binaries\data\mods\public\art\textures\skins\skeletal\maur_elephant_siege.png References: Here are some tips in how to make textures in Blender by rendering!
  17. Enrique

    0 A.D. on YouTube

    darn... that music video is really cool. I wonder how could have looked like with the new meshes...
  18. Enrique

    Carthaginian scaffolding

    @LordGood Any plans on progressing with the construction-progression actors?
  19. Creo que sería mejor enseñarle a cómo encontrarlas por él mismo en las carpetas del juego Lion
  20. Enrique

    Gameplay guideline

    I think this adds uneeded complexity and houses with higher pop is good enough for addressing repetitive interactions. If women should have a bigger role, I think it should be in a different way. I like the proposal. Even there are some things that I was initially against (splitting iron resource) but you made some good points about the reason behind adding it.
  21. Para que te hagas una idea, el nuevo modelo de los caballos tiene 800 triangulos. Algo aproximado estaría bien. Un colaborador hizo un modelo basado en el oso actual, pero se puede mejorar bastante. Sería ideal que le hicieses también textura y esquelto para animación si te ves capaz. Aquí te dejo el hilo, que aunque esté en inglés hay algunas imágenes para hacerte una idea:
  22. Enrique

    Victory Conditions Ideas

    Forgot to update here about the flag cart, it's being worked on. Just in case somebody was thinking to jump to the task to avoid duplicate work. WIP ( *Note: It's PBR shading, not GLSL)
  23. Hola mike, bienvenido a los foros. Has probado el juego? La pera no se ve mal, pero no sé donde habrás leído que hacía falta una... quizás skhorn se refería al árbol, un peral que la traducción al inglés será directamente "pear". Te pregunto si has probado el juego ya que lo que buscamos son modelos eficientes en polígonos, (es decir, la menor cantidad de polígonos posible, sin que se vea mal). 0AD es un juego de estrategia y por ello la cámara por defecto es más o menos isométrica y bastante alejada del suelo para tener una vista estratégica. Se puede hacer zoom, pero es limitado. No disponemos de sistema de nivel de detalle, por lo que tenemos que ser estrictos con la cantidad de polígonos en el caso de objetos que van a ocupar poco espacio en pantalla. En este caso, la cantidad de vértices/polígonos para una pera sería mucho más bajo que ese modelo, y en el caso de necesitar muchas peras en cajas o cestas, usaríamos una textura de un montón de peras en lugar de usar modelos. Si estuvieses interesado, estaría muy bien contar con formaciones rocosas, árboles, piedras, arbustos, plantas, ruinas.... para decorar mapas. En el caso de que estuvieras interesado, dime en qué tipo de modelos lo estarías para darte referencias y concretar más. Respecto a las animaciones que has compartido, son bastante básicas. Estaríamos buscando algo parecido a este ejemplo. Respecto a las texturas, dada la naturaleza del proyecto deberían de estar publicadas bajo CC-BY-SA 3.0 o superior (o de dominio público) o que seas tú el autor de las texturas, claro. (Es decir, texturas de páginas web "populares" no suelen servir, ya que tienen licencias que no permiten ser usadas en otros proyectos)
  24. Enrique

    Testing Propositions

    Reading this saddens me deeply.
  25. Enrique

    Testing Propositions

    That's the point of the discussion. Impactful changes. It's not the first thread I read about the game not being appealing through the point of "checking it out". More arcade? what? You asked for specific solutions/ideas, and he gave you a list of posts with specific ideas. He then proceeded to put a quick draft of overall core gameplay system and you started nitpicking it when it was clearly an example. The point is, don't be so defensive about the game. 0AD It's not perfect, and DarcReaver is clearly wanting to prove a clear point here, even if it sounds harsh. Doesn't seem to me that it's for the sake of just complaining, but to actually realize the issue. Also it's not just a random player as it seems he has experience on RTS game dev and modding.