Jump to content

Enrique

WFG Retired
  • Posts

    2.338
  • Joined

  • Last visited

  • Days Won

    96

Posts posted by Enrique

  1. Looks great, though, there should be quite a bit of tweaking left. I don't think the black areas are really the problem, but there are some regions where the reference image doesn't cover well, such as the back, and the legs. It looks great from the side, but in game, it'll be viewer from above most of the time.

    There is also quite a bit of highlight in the texture, which should preferably be painted over with a neutral grey body color (the region on his back is almost white).

    Correct.

    Nice work projecting it though. Stan you should try to improve the texture once projected through GIMP or Blender's texture painting.

    I finished texturing this fine model. I think I scaled the model though, not sure if it was already set to in-game scale. Good job everyone.

    post-13528-0-35954000-1426204223_thumb.j

    white_rhino_final.zip

    • Like 4
  2. Nice to see you back modelling and animating wraitii! :D

    Very nice overall :)

    My input would be on marking a little some characteristic look of the hyenas: the fact that they normally walk with the head quite low, and the fact that their back legs are much shorter than the front ones compared with other quadrupeds (thus making a slope on their spines seen in auron's reference http://media.web.britannica.com/eb-media/34/82634-050-865C2055.jpg).

    waiting to see the animations :P

  3. Hey nice job Stan!

    I like all of them except the one with the hole, it looks too fake. The rest are looking pretty good!

    You should try also going for some lowpoly flower groups. keep it up!

    On a side note, be carefull with the saturation of the mushrooms, too bright/saturated colors may make the player think they're collectable/food. Otherwise, nice work.

  4. I took a closer look at Hatra on the UNESCO site. It seems to stretch from the Parthian empire well into the Sassanid and Islamic empires. There are a lot of influences to peel apart in this region.

    We can pull hellenistic influences out of this, but as far as a 1:1 translation I think we're giving a lot of Roman and Sassanid era details that will really muddy up the historical accuracy.

    Even the Apamaea reeks of Roman influence

    Pulling inspiration out of Pergamon is probably our best bet for the Hellenized east, at least as far as the civic buildings are concerned.

    (I'm all for persian formalities though)

    I'm all for finding another solution to the CC if you agree with me on this point, Enrique.

    We'll discuss this further soon.

    I've made some better columns for seleucids. Overall the texture you made is quite good, I'm going to touch some values and probably make it 2048*1024 to have some more room for more stuff

    post-13528-0-38910400-1426182145_thumb.p

    • Like 7
  5. Hello Kicking_Bird,

    Regarding terrain textures:

    As already noted by a lot people in the thread, several terrain textures have quite some age already (as you already know the project has been going on for several years). Normal/Parallax, Specularity and AO maps were introduced in 2012 after the roman set was done. These features weren’t planned, and an awesome contributor took it and implemented them by his own (which is one of the many benefits of open source development). Before that, several artists had just a basic lighting render model where they did the best they could to make things look nice, which involved textures with shadows and highlights in them and contrast noise to counter the plain lighting.

    With this background, you can see that nobody made these textures like they are “on purpose” or “by mistake”, but it was a workaround of the possibilities of the engine at that time. Surely they can be improved, you’re more than welcome to start working on it and show us what you can achieve.

    Regarding LOD:

    It isn’t implemented. The contributor who made the sweet graphic improvements had it planned after he implemented deferred lighting, but sadly he disappeared from the forums and project before that (one of the inconveniences of open source). That’s the main reason artists have to work with more-limited-than-standards polycount and make use of hard edges and smoothing groups to deal with shapes and can’t go chamfering every edge. Another thing we have to deal working for 0AD is the fact that the diffuse and normal maps are shared between all the strutures sets, which doesn’t give you all the freedom you want when using them and it pushes the improvisation and creativity of the artist to make use of them in the best way possible. The only non-shared maps between same civs structures are AO maps, which are just greyscale images and doesn’t eat so much memory space than having one normalmap and one diffuse texture for each one. (And since there’s no LOD system, we can’t make use of lower res textures dynamically either)

    This shared textures also generates the problem of the different pixel density ratios, where even if you make your best effort designing the texture and trying to make each piece the closest to its final size on the model, there will always be situations where pixel density will vary in the model since the texture wasn’t specifically designed for that particular model.

    Regarding the Persian wonder:

    The current one in the game seems to not be as accurate as it could be, so the last decision about it was to use the Gate of all Nations. I started it some time ago but didn’t finish it yet. You can check the direction I took here: http://wildfiregames.com/forum/index.php?showtopic=17552

    I have an updated version with more detailed/accurate columns I can upload if you would like to take it from there, unless you want to start from scratch.

    Last thing, I’d like to take a look at your work examples and/or older projects. Sadly the link you provided in the first post is not working for me (not found)

    And welcome to the forums by the way!

    • Like 8
  6. I'll drop quickly my input in some of the anims, I'll elaborate more later at home:

    Mining: I think the arch of swinging the axe should be exaggerated a little bit. The pickaxe don't get momentum, it goes from almost stopped to full speed blow too quick IMHO. Also could use a step forward when giving the blow and move it back to original pose when drawing back the pickaxe?? just thinking loud, you have freedom to see what fits ;)

    Carrying ore: I like that we're going to have different carrying animations (yay!). I think that when carrying ores, their back should lean backwards (to counter the material weight). Right now they bend forward, which I think looks unnatural. (Imagine yourself carrying something very heavy in your hands walking forward and you'll see how you lean backwards to keep balance)

    Chopping wood: I know that you used Lion's reference to make the animation (around 1:50 I think) however, that woman is chopping wood as fast as she can for a competition. If you're going to make a hard task like chopping, you want a more relaxed back stance. Right now they're bending too much forward, they'll have a big back ache from that pose if they're going to keep chopping for a long time. Also the legs may be too "crouched" but I think it's because I'm seeing them leaning forward too much. The arms timing and the swing flow is perfect though, I really like it and looks very natural.

    Carrying wood: Perfect :)

    Walking: Looking pretty good :D

    Keep up that good work man! really digging your work!

    • Like 1
  7. Thanks everyone, i'll keep searching for good poses and reading everything you're saying here, opinions are very important for the animation's development.

    and please be patience, this is not a hard work but it's a little bit slow.

    In the mean time, where i can upload one .Dae file to test it? i need to know if there's an issue with the c4d's exporter before i continue making more animations.

    http://www.mediafire.com/view/12ioop2vl1086qa/FemaleCitizen_Dress_Seeding.dae

    Let's show you some modding so you can make your own tests in the game:

    This is a look at the newunit_fem.xml actor: (open the .xml file in notepad or notepad++ is better)

    This file is located in \0AD\binaries\data\mods\public\art\actors\units\hellenes\

    <?xml version="1.0" encoding="utf-8"?><actor version="1">  <castshadow/>  <group>    <variant frequency="1" name="Base">       <animations>        <animation file="biped/new/fem_idle_long.dae" name="Idle" speed="100"/>        <animation file="biped/new/fem_idle_short.dae" name="Idle" speed="100"/>      </animations>      <mesh>skeletal/new/f_dress.dae</mesh>      <props>        <prop actor="props/units/heads/new/head_female_test.xml" attachpoint="head"/>      </props>      <textures>        <texture file="skeletal/hele_fem_d.dds" name="baseTex"/>      </textures>    </variant>        </group>  <material>player_trans.xml</material></actor>

    In this example, you can see the animations that are going to play when "idle" (no attacking/not moving) are the following:

        <variant frequency="1" name="Base">       <animations>        <animation file="biped/new/fem_idle_long.dae" name="Idle" speed="100"/>        <animation file="biped/new/fem_idle_short.dae" name="Idle" speed="100"/>      </animations>

    The speed is obviously the speed to play the animation, and the file is the path where the ".dae" of the animation is located.

    Just overwrite the path with your animation's path (better place your animation in the same folder as the "biped/new/" folder) and the unit will play it when spawned in atlas. These .xml are just for test, so don't worry to change them as you please to test your animations ;)

    In resume this is how "visual actors" work in the engine, it's a ".xml" that tells the engine where are the mesh in the <mesh> labels, the <textures>, the props, animations...

  8. Hi Jos3BV, amazing work as usual.

    I'll drop my input:

    First some explanations on my list:

    -The difference between relaxed/ready:

    This is because we want the units to look more aware of their surroundings, so we want to have a relax pose when no enemies are nearby, and one "ready" when enemies are close. An example would be units with shield: if no enemies are nearby, they will have their shield down, at a side relaxed. And when they have enemies nearby, they should bring the shield up and get "ready" in a pose closer to the attack loop, but still "idle". For ranged units, relaxed would be the javelin or arch down, at a side and when they're "ready" with the javelin up ready to shoot, and their arch loaded too.

    This is an example I made about static poses to give an idea of what I had in mind:

    Same for walking and running, if they're walking/running towards the enemy it makes sense that the units raise their shield according to the incoming danger. Right now units walk around the battlefield like if they're walking in the park ^_^

    *(NOTE: units being aware of units nearby to change their idle/walk/running animation is not yet implemented, but will be. So we need these animations)

    This difference makes that females do not need a "ready" stance for idle/walking/running since they do not attack. Sorry I didn't make clear that before.

    -Female walking looks too manly, let's try to make it a little more feminine (more hips-heavy, less shoulder heavy). The flow of the loop is great though :) .

    We want walk/run/idle for females to be different from males.

    -Mining... I think the previous iteration was better. Something close to what we have now would be nice. Good reference: http://youtu.be/sPwXhtg94-M?t=2m33s

    You're doing an amazing job man! keep it up! :thumbsup:

    And forget at the moment about horses and fishing animations, core unit's animations are high priority now :)

    • Like 4
  9. Your animations and transitions look incredible man. I really like them even if they're not finished yet. The big problem is that the engine doesn't support transitions between animation states (states = loops) yet.

    I still have to make some minor tweaks to the armature that I posted, like adding one or two prop-bones, but I think it shouldn't create incompatibility with the work you already did.

    I'll do them asap if you're willing to keep making this awesome stuff.

    Here's a list draft of the animations I could think of. Ask any question/doubt you may have about them or how the engine manages the animations. (Even in spanish if it easier for you lol ;) )

    Common:

    -Seeding

    -Mining

    -Gather fruit

    -Slaughter / cavalry slaughter (killing animals to gather food)

    -Build

    -Promotion / cavalry promotion

    -Farmfield gather

    -Chopping wood

    -Treasure gather?

    -Carry resources (same anm? different animation for each resource?)

    -Death /cavalry death

    Infantry:

    For the sake of identifying units easier, infantry animations will be divided into the following types, each type will have different idles/rest positions as well as attack animations. Walk and run animations will be very similar between infantry types (and will be less work) but the arms position will vary depending of the weapons and props of the units.

    These are the initial types I could think of:

    Shield+sword, Shield+spear, Shield+javelin, Only Bow/Bow+shield, Only javelin, Hoplite, Pikemen, 2h weapon, Slinger

    Each of this type of units will have its own variations of the following animations:

    -Idle relax

    -Idle ready

    -walk relax

    -walk ready

    -run relax/slow/jogging

    -run ready/charge

    -Attack melee / ranged

    -Custom deaths

    Cavalry

    Shield+sword, Shield+spear, Only spear, Shield+javelin, Only javelin, Bow

    -Idle relax

    -Idle ready

    -Walk relax

    -Walk ready

    -Trot

    -Charge

    -Attack melee/ranged

    -Custom deaths

    Support:

    -Healer crane walk/run

    -Healing

    -Trader walk /run

    -Pushing siege?

    -Mounting/dismounting siege?

    -Firing siege?

    Formations:

    -Testudo:

    -Front line idle/walk

    -Back line(s) idle/walk

    -Syntagma:

    -Front line idle/walk/run/attack

    -Medium line idle/walk/run

    -Back line idle/walk/run

    -Phalanx

    -Phalanx idle/walk/run?

    -Phalanx attack

    Special:

    -Howdah attack?

    -Fake physics stunts?

    -Hero Idles?

    -Capturing/throw torches?

    -Chariot riding?

    • Like 3
  10. Check the last step he makes to return to original position. It's just too quick. If you manage to stop the video where he starts to make the step forward is less than 1/3rd of the timeline.

    Don't try to work on a fast loop. Just try to balance the number of frames from start to the shooting, to resting again. start - shoot - back to start. The speed of the animation can be tweak later.

  11. I'd rather go to the Hatra structure directly, the one that you made the front blueprint LordGood. Nice work on the structures by the way. I like the overall color scheme and the columns. The temple looks very nice, my favorite so far. I'm not sure if I like the defense tower though, having the wall-columns in a military building doesn't look like it fits (unless I'm missing a reference that shows accuracy)

    If you let me, I'll make the texture following the color scheme that you set, and will go for a 1024*2048 texture as I did with ptolemies.

    This is what I want for the Seleucid CC:

    post-13528-0-77602100-1420201489_thumb.j

    • Like 1
  12. It's totally necesary use Blender to animate? i'm good with animations and i wanna contribute but i use to work on Cinema 4D. It seems that i can export everything like you say here from C4D without any problem (COLLADA, etc). An any case i can learn to use Blender and contribute anyway, i'm really exited about this proyect.

    It's not obligatory, but it's the team standard. For unit animations we provide the mesh and armature in .blend format (blender standard) I guess you can try to export it as .fbx or .dae for cinema, but you'll probably lose some functionality.

  13. For the standard archer animation, I made an idle where the archer would have his arrow already drawn and resting on the bow ready to shoot (archer_ready). The firing animation would be just aiming and shooting, then picking a new arrow and rest it again in the bow to begin the loop again. I think this could look pretty good in the game and lower the starting animation frames so the arrow would be shot earlier in the animation loop.

    The problem I see with Stan's animation is that now it is playing slow, and remember that we want the animation to loop and it will play much faster, which will make the non-smooth movements even less smooth.

    This is a very nice example of a good draw-shoot animation: http://www.wildfiregames.com/forum/index.php?showtopic=19490&p=301834

    It's short, loops nice and the pose is very natural.

  14. Yes, I see, but are they implemented? I open the scenario editor and the models are not the same..... they are still the old pointy and ugly face ones.

    -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)

    From the first post ;)

    • Like 2
  15. I agree.

    I just though that tweaking the neck a bit would fit more on the "average" proportions of the breed. I've been checking it hiding the "hairy lose" faces. I'll use them for alpha-transparency hair still.

    I think I'll leave the head size as the original and shorten the neck just a tiny bit (not as much as the comparison screenshot I posted earlier)

×
×
  • Create New...