Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by oDDity

  1. Well here's the thing you don't understand about keyframe animation - it's not about copying reality. If you wanted that, then just use mo cap. Animation is about filtering out and keeping only what's essential to making things seem real, and then exaggerating or diminishing and cleaning it up. That's why it can be done cleanly and effectively on one layer using a small strategic number of controls and channels. It's more of an impression of movement than photorealism you should be after. That's where the real skill lies. It's pointless trying to layer ever more subtle rotations and translations on top. If you do the main layer effectively, it's not needed. It's like people in sculpture who think the details are the most important part, so you see these shit model with terrible proportions, no form, no rhythm, no weight, they've just spent 90% of the time intricately sculpting details of wrinkles and pores on a model that is never going to be any good.. A good sculpture looks good at every stage of development, even the earliest layout, and the same should be true of animation.
  2. It all depends how effectively they're being used. They can be used effectively by animators who already know how to animate properly - that is, in a disciplined fashion where they keep control of every channel on every control - but they are also open to abuse by lesser animators who think layers are the be all and end all and just use them to key the crap out of everything and toss more layers on top as a quick fix. What those animators are literally doing is constantly using layers to correct the sloppy animation they did on previous layers, because the previous layer is now fucked and messed up with lots of redundant keys and channels which shouldn't even be there. To me, that's not easier, because now you have tons of layers with tons of keys and channels crapped all over them, instead of just one layer with nice neat keys on the specific channels you need. Animators should have to learn to animate properly first, without layers, and then learn how to use layers only to compliment real sklills.
  3. Well this is the point, the normal map size needs to be decided on a case by case basis, rather than being batch reduced to a certain resolution.
  4. It'll not reduce their visible quality. Games like RtCW used 256 and 128 textures and it still looks damn good. Normal maps don't suffer from size reduction as much as the detail in colour maps. The 1024's were never intended as final game resolution, it was just in case they had to be edited etc Taking a quick look through the textures, there's a lot of 1024 normal maps that could even be knocked down to 256, considering the low frequency information they're carrying.
  5. You Will NOT notice smaller normal maps. The size of them is insignificant compared to the actual texture.
  6. It'd be crazy to do them all as dxt3. Most of the textures don't have an alpha channel, so you'd be doubling the size for nothing. As for normal maps, if they have to be left as targas, then all the 1024's should be reduced to 512 ,adn the 512's to 256. The difference will not be noticed.
  7. NAh, you barely notice the difference. Also, are mip maps really necessary, since you can shave another 200kb off that by not having them. Doesn't sound much, but over 1000 textures, that 200mb saved.
  8. You only need dxt3 if there is an alpha, otherwise dxt 1 will do, which is half the filesize. A 1024x texture should be around 600kb.
  9. Now you've reduced your argument down to something reasonable like 'layers are helpful and make things easier' rather than 'it's virtually impossible to do some animations without layers', I agree.
  10. This is where you need to learn to keep control of you channels and not all the bad habits you've picked up in MB of keying the crap out of everything. When I shake my fist vigorously, all I get is some y rotation on my hips. This leaves x, y and z translations free for larger movements, and you still have x and z rotation free. You have 6 channels to work with for each bone/ik control, and professional animators use them wisely and separately, and use each channel for the appropriate movement, setting as few keys as possible and using weighted curves to get from one position tot he next. Your assertion that most animation, even the simple noob sort of animation you've done, cannot be done without layers, is borne out of pure ignorance of professional animation techniques. I agree layers are a quick fix, they can let you be sloppy and lazy and get away with it, but they're in no way essential for good complex animation.
  11. To take your earlier example of a shaking fist, you should be using FK and not IK for that. You would animate the main shaking fist from the elbow and hand and the secondary overall arm movement you wanted to add, you would do from the shoulder. Your problem is you only know how to use IK so you have to do everything by moving the fist. The arm is a three piece system of overlapping movement, with delay and followthrough, and IK is useless for that.
  12. I did a quick video tut of animating a (rough) walk cycle with this new rig. Should help you get around in maya. You use the shift+middle mouse button for selecting and on the timeline and MMB for dragging tangents in the curve editor. Also MMB on the timeline to jump around without moving the animation to that time, so you can set hold keys. http://www.pixelwerks.be/pictures/walktut.7z
  13. Ha, listen to this guy would you. He didn't even know what motionbuilder was until I told him and made some tutorials on how to work it, and now he's trying to tell me how it is. You do not need layers to do overlap and secondary motion. Layers are just the the easy lazy noob way of doing it. Real animators do not need layers because they keep complete control of each specific channel of their animation and do all their work with curves. When you use curves properly you do not need many keys, just the main pose keys. You're way out of your depth here, so don't bother arguing any more.
  14. Believe me, the vast, vast majority of professional animators do not use motionbuilder, they use maya or some othwer 3d app. In fact, virtually no one uses motionbuilder for keyframe animation. It's purpose is correcting motion capture. They find no problem doing feature animations exponentially more complicated and subtle than a warm hands loop without motionbuilser layers. Those layers really just make you lazy and give you a bad habit of keying the crap out of eveything. In maya you keep it clean and only key the specific channel you need, so the y rotation of the upper arm for example, and you keep a nice clean curve for that in the graph editor and and do any amount of subtle work with it there. You set only the few keys you need on the specific channels you need and it makes editing easy.
  15. This model hasn't got many animations, and I think those were imported from the citywatch. What animations will be needed for the builder guard for the release map? I've got more work on the the next few weeks, so I won't be able to do much.
  16. Yes, character sets are perfect for this. I just hadn't looked into trax/character sets in maya before. Here's the mb with the new rig. I'm going to reskin the mesh though. There are two slightly different versions of the file, one with IK arm setup and one with fk arms, because I don't know how to set up ik/fk switching on the arms. I find pure fk arms are great for walk cycle type anims, but ik arms can be useful for things like sword anims where the character is interacting with props.
  17. Since it's probably too late for the city watch guard, there being too many variations what with SH and all the animations, I'm doing the builder guard for now, and since that's being used for the release it makes sense. I reproportioned the model, built a whole new skeleton from scratch, built a new ik animation rig from scratch and animated a patrol walk. Motionbuidler should be cut out of the pipeline. It's unnecessary, but when I started this pipeline a few years ago I didn't know enough about maya. Now that I do, it can be used for the whole pipeline. The trax editor can be used for swapping different animation between characters, and I've already built a rig that better for keyframe animation than the one in motionbuilder, which is only set up for adjusting motion capture.
  18. You'll just need to take this new mesh when it's done and split it up the way you had it before so it will still work with the skins. Which way the mesh is split up is irrelevant to me, so you can change it to whatever you want, it won't affect the rig or animations.
  19. Yeah, that's it. If I comment out the skin line it works.
  20. It seems to me that the actual in-game model is not using the shaders that are specified in the md5mesh. When I do a testmodel command in the game it works fine.
  21. Is there some sort of extra skin material on the city watch guard in the game, because he's showing up black for me and his hands are displaying shadows ever though the shader in the md5mesh I exported is pointing to hands which have shadows turned off. IT works ok when I do a testmodel in-game and looks ok in the editor, but the actual model in-game is black.
  22. My new rig? I haven't uploaded it yet. The new one is quite a bit different to the old one, but the bone positions are pretty much identical. It's not a lot of work to tweak the proportions of a model and skin it to a rig, and that's all that's needed to be done to fit the citywatch variations to the the new setup.
  23. I haven't changed the Uv mapping on the citywatch model at all, so I'm sure the different skins will still work. However, for any actual model alterations SH has made away from the default citywatch model, he will have to take his models, adjust the proportions using this new model as a template and then weight it to the new skeleton and export the md5mesh. All the animations will work. I'm going to do this for the builder guard as well, and the city watch elite.
  24. I completely rebuilt the skeleton now. Apart from the fingers it only has 22 joints now. I added proper 5 fingered hands because you cannot properly control the bending of 3 loose fingers with one joint since they are different lengths. Finger animation is not a big deal anyway, it's either in the default relaxed pose I used to have as the default, or it's gripping something. There's no need for complex finger animations. The old claw hand just looked so terrible I has to replace it. What is the sword_cube piece of geometry for? Is that used in doom for something? I have a sword bone and a bone at the back for attaching a bow or hammer, and I kept the knee bones since I remember they are used for IK in doom. Also, what about the shadow mesh, does that have to be weighted to the skeleton and exported along with the regular md5mesh? All remains to do now is to tranasfer al lthe aniamions onto this new rig which shouldn't be too much trouble using motionbuilder.
  25. Yes, I know all about going into component mode and setting the joint orientations, I had the original skelington hands set up like that, but I didn't make this new 3 fingered hand, it was done later for the low poly hands. I will just setup a proper 5 fingered hand then and make that the new standard hand. @For this i used Maya 7.0. I returned the rig in t-pose and imported one of the plotted animations. The way it was always done to get fbx into maya. Yes, but motionbuilder is much better at coping with sharing animations between different skelington hierarchies than maya is, so it's easier to do it there.
  • Create New...