Jump to content


WFG Retired
  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Wijitmaker

  1. Alright, so row 393 means nothing in the .dae file: It is simply </source> So, what is 393 in your skeleton.xml file? Also, could you share the code of your actor file?
  2. I wondered, so fisherman_paddling.dae is the same as fisherman.dae?
  3. This helps. Could you post the fisherman.dae file? Lets look at line 393. Also please share your current skeleton file your using.
  4. Soo... the engine log doesn't give you any errors? Looking at this code again: http://www.wildfiregames.com/forum/index.php?showtopic=15552&view=findpost&p=233174 DEF- doesn't seem to apply to root. Try taking it off root. Also note that the structure I have above was based on the ORG- heirarchy. I'm not certain that the DEF- is the same (should be). You also shouldn't have to create your own seperate standard biped - but I suppose it was worth a shot
  5. Daniel, try Ben's suggestion. Example: <bone name="shoulder.L"><target>l_clavicle</target> Add "DEF-" like this: <bone name="DEF-shoulder.L"><target>l_clavicle</target> Or try "ORG-" or "MCH-" It is odd, because the other skeleton rigs from blender (BlenderChicken as an example) in the skeleton.xml file don't call these out. This last weekend I tried getting a .bvh out of Max and into Blender - no luck. I was trying to export a .fbx from Max into Motion builder - then exporting a .bvh from MB to Blender. Something isn't working right. I'll give it a shot next weekend again. Also, it would be helpful to describe any errors the engine throws out at you. Hopefully the engine error would be descriptive enough to tell us what is breaking. Michael - I would have no objections.
  6. Try this adding this to the skeleton.xml file and running it: <skeleton title="Blender biped" target="biped"> <identifier> <root>root</root> </identifier> <bone name="root"><target>root</target> <bone name="hips"><target>pelvis</target> <bone name="spine"><target>spine</target> <bone name="ribs"><target>spine1</target> <bone name="neck"><target>neck</target> <bone name="head"><target>head</target> </bone> </bone> <bone name="shoulder.L"><target>l_clavicle</target> <bone name="upper_arm.L"><target>l_upperarm</target> <bone name="forearm.L"><target>l_forearm</target> <bone name="hand.L"><target>l_hand</target> </bone> </bone> </bone> </bone> <bone name="shoulder.R"><target>r_clavicle</target> <bone name="upper_arm.R"><target>r_upperarm</target> <bone name="forearm.R"><target>r_forearm</target> <bone name="hand.R"><target>r_hand</target> </bone> </bone> </bone> </bone> </bone> </bone> <bone name="thigh.L"><target>l_thigh</target> <bone name="shin.L"><target>l_calf</target> <bone name="foot.L"><target>l_foot</target> <bone name="toe.L"> </bone> </bone> </bone> </bone> <bone name="thigh.R"><target>r_thigh</target> <bone name="shin.R"><target>r_calf</target> <bone name="foot.R"><target>r_foot</target> <bone name="toe.R"> </bone> </bone> </bone> </bone> </bone> </bone> </skeleton>
  7. Ok, I parsed it and took out all the crap. I think it should look something like this. Now it just needs to be tagged and attributed correctly in the skeleton.xml file... then tested. Daniel, can you try that? <node name="root"> <node org="hips"> <node org="spine"> <node org="ribs"> <node org="neck"> <node org="head"> </node> </node> <node org="shoulder.L"> <node org="upper_arm.L"> <node org="forearm.L"> <node org="hand.L"> </node> </node> </node> </node> <node org="shoulder.R"> <node org="upper_arm.R"> <node org="forearm.R"> <node org="hand.R"> </node> </node> </node> </node> </node> </node> <node org="thigh.L"> <node org="shin.L"> <node org="foot.L"> <node org="toe.L"> </node> </node> </node> </node> <node org="thigh.R"> <node org="shin.R"> <node org="foot.R"> <node org="toe.R"> </node> </node> </node> </node> </node> </node> A simple text editor with a find/replace tool does wonders.
  8. I can't get my dreamweaver to load... that is the tool I would use to go through and delete (find/replace) out all the attribute / element junk that isn't needed. Ben your right on Daniel, please bear with me and my computer issues.
  9. I took a look at the .dae file and I think this is your heirarchy. I haven't broken it down, but I think you can parse it out to structure it to fit the format of the skeleton.xml file:
  10. No worries. My point is not just to get animations from blender into the game, but to make them compatible with the existing human biped model and animations so that everything is shared and can be used by any person with a variety of software (Max, Maya, Blender, XSI, etc...). Getting any old animation into the game from blender shouldn't be hard Pureon has done that many times - it is getting it to be cross compatible which is trickier. It would be foolish to start creating a whole new batch of unique humanoid animations that are using a blender specific model. Unless this team thinks it has the resources to replace all the existing animations an models to make it common.
  11. Ok, perhaps I can get the animation out as a .bvh file. This is generally a motion capture file type that is generated by some sort of motion capture device. Max takes that data and turns it into a .bip file, and that is what Character Studio uses as it's animation format. FYI there is a lot of .bvh files in our repository for you blender users to play with: http://trac.wildfiregames.com/browser/art/trunk/art/animation/resources/bvh I'll see if I can get an export of a .bvh from max to blender with some sort of script (or tools, I think there must be something out there on the web for this).
  12. I thought maybe the cubes would show you where the bone's joints should be located, and their size. I'll check out the .dae when I get home from work. Can a blender user answer the .FBX question? That could be a great format to transfer animation between Max and Blender.
  13. For the unused animations... is it possible some of the files are duplicated and used in another folder? Many of them look like they are unused because we are waiting for return of the run/stamina feature. Animations are a precious commodity so I find it odd that any are not in use.
  14. Ok, I've got Max working finally! Note to self: Thanks to this link - http://forums.cgsociety.org/archive/index.php/t-247858.html So, this is what an imported skeleton should look something like. I've included the geometry points for reference. skeleton_export.zip Does this help? I see blender has the ability to export a .fbx file? Is it capable of opening one as well?
  15. Try exporting a .dae file and I think it could be used to read the names of the hierarchy structure as the .dae file sees it.
  16. The source files for all the max animations are already in the Art SVN repository. Anyone with an active Max account should be able to reopen the .max files and export a .dae from it.
  17. I'm afraid the best I can do is get you an export of what it should be like. I'll try to figure out how to do that. Though it might be easier said than done... My 3ds Max isn't working at the moment and I think I have to reinstall windows to get it up. I've got some cdilla issues.
  18. Well, this that max does that might be a max only feature. For example, if I created two simple boxes (similar to like what is started with when blender opens up each time) and if I linked one box to another box... this effectively creates a hierarchical structure of bones. If you re-sized these boxes you could make it more like the shape of an... arm for example. Max then allows you to apply a modifier called "skin" to the mesh you want to modify with animation and define this simple hierarchy of boxes as the 'bones'. That is one option, the other option is to actually use the bones object in max that help automate a lot of things for you like scaling and IK constraints. Does blender allow you to create a hierarchy out of geometry that could later be turned into "bones" that would allow you to rig your model and apply envelopes and vertex weights - or are you forced to use bones?
  19. Well, I took a look at blender tonight, and it looked as foreign to me today as it did 5 years ago. I was able to figure out how to import a .dae model (I picked one of the male tunics I think - they are all the same, so it doesn't matter). When I delete the mesh and look at the bone structure that was imported, it is awful. Bones aren't oriented correctly links are off... etc. I don't think the software's import is working so well. Anyway, there might be a way around that. Let me ask you blender guys this - can you make any object (geometry) a bone in blender or is a bone a unique sort of an object? If so, what I could do is export Character Studio's bones as a mesh and they could be imported and linked up in Blender later? The importer seems to do fine with geometry... Notice the bones orientation is off and the dotted line links between the bones. They look like one point is correct, but the other end of many of the bones in the spine area, the ends of the appendages, and the props are flying in the wind.
  20. Just an FYI, the tool that was used prior to Atlas to make maps (SCNed) had the ability to import a black and white height map. It would be nice to have this functionality restored, enabling users not just to plug in RMS generated height maps, but also real world height maps (both at a continent level and at a battlefield level). Bryce was a neat old tool used to generate some great height maps, having some cool features like erosion. May be worth a look. http://en.wikipedia.org/wiki/Bryce_%28software%29 (looks like there might be a free limited version out there?)
  21. Similar to Michael's suggestion. Perhaps remove the hull of the ship (temporarily) while to get your rig set up. Once the oars look right, move the hull back into position.
  22. I had another thought today on this reading the RMS map thread Michael posted about the problem of to many trees. Would it be any advantage in having a second 'forest dynamic border' (unvisible to the player) that is based on trees? This could possible block out clumps of areas that the pathfinder could omit from it's long pathfinder calcuations? This would be a Boolean default property in the actors that 90% of the units in the game would be constrained by. Dunno - not being a programmer, I'm purely conceptual. Just a thought, I have no idea if it would actually work in code
  23. It is hard for me to give you instructions because I don't know enough about blender to see what your seeing. I guess I could install it and try my theories myself, but I'm a total noob with the software. It would be worth a start though perhaps. Could you point me to a download of the same verion of the software you are using? Also, here this might be worth take a look at. This is the basic structure of the dude: http://trac.wildfiregames.com/wiki/ArtDesignDocument#Tools The portion of the file you would be looking at is: 1 <skeletons> 2 <standard_skeleton title="Standard biped" id="biped"> 3 <bone name="root"> 4 <bone name="pelvis"> 5 <bone name="spine"> 6 <bone name="spine1"> 7 <bone name="neck"> 8 <bone name="head"> 9 <bone name="DUMMY_headnub"/> <!-- kept for binary compatibility with PSA files --> 10 <bone name="l_clavicle"> 11 <bone name="l_upperarm"> 12 <bone name="l_forearm"> 13 <bone name="l_hand"> 14 <bone name="DUMMY_l_finger0"> 15 <bone name="DUMMY_l_finger0nub"/> 16 </bone> 17 </bone> 18 </bone> 19 </bone> 20 </bone> 21 <bone name="r_clavicle"> 22 <bone name="r_upperarm"> 23 <bone name="r_forearm"> 24 <bone name="r_hand"> 25 <bone name="DUMMY_r_finger0"> 26 <bone name="DUMMY_r_finger0nub"/> 27 </bone> 28 </bone> 29 </bone> 30 </bone> 31 </bone> 32 </bone> 33 </bone> 34 </bone> 35 <bone name="l_thigh"> 36 <bone name="l_calf"> 37 <bone name="l_foot"> 38 <bone name="DUMMY_l_toe0"> 39 <bone name="DUMMY_l_toe0nub"/> 40 </bone> 41 </bone> 42 </bone> 43 </bone> 44 <bone name="r_thigh"> 45 <bone name="r_calf"> 46 <bone name="r_foot"> 47 <bone name="DUMMY_r_toe0"> 48 <bone name="DUMMY_r_toe0nub"/> 49 </bone> 50 </bone> 51 </bone> 52 </bone> 53 </bone> 54 </bone> 55 </bone> 56 </standard_skeleton> 57 58 <!-- 59 60 The <skeleton>s must specify all the bones that may influence vertexes of 61 skinned meshes. The <bone name> is the name of the bone in the relevant 62 modelling/animation program. The <identifier> name is used to determine 63 whether this <skeleton> applies to the data found in a given model file. 64 65 <target> must be the name of a bone in the standard_skeleton identified by 66 <skeleton target>. 67 68 The hierarchy of bones is mostly irrelevant (though it makes sense to match 69 the structure used by the modelling program) - the only effect is that 70 the default <target> (i.e. when none is specified for a given bone) is 71 inherited from the parent node in this hierarchy. 72 73 --> 74 75 <skeleton title="3ds Max biped" target="biped"> 76 <identifier> 77 <root>Bip01</root> 78 </identifier> 79 80 <bone name="Bip01"> 81 <target>root</target> 82 83 <bone name="Bip01_Pelvis"> 84 <target>pelvis</target> 85 86 <bone name="Bip01_Spine"> 87 <target>spine</target> 88 89 <bone name="Bip01_Spine1"> 90 <target>spine1</target> 91 92 <bone name="Bip01_Neck"> 93 <target>neck</target> 94 95 <bone name="Bip01_Head"> 96 <target>head</target> 97 98 <bone name="Bip01_HeadNub"/> 99 100 <bone name="Bip01_L_Clavicle"> 101 <target>l_clavicle</target> 102 103 <bone name="Bip01_L_UpperArm"> 104 <target>l_upperarm</target> 105 106 <bone name="Bip01_L_Forearm"> 107 <target>l_forearm</target> 108 109 <bone name="Bip01_L_Hand"> 110 <target>l_hand</target> 111 112 <bone name="Bip01_L_Finger0"> 113 114 <bone name="Bip01_L_Finger0Nub"/> 115 116 </bone> 117 </bone> 118 </bone> 119 </bone> 120 </bone> 121 122 <bone name="Bip01_R_Clavicle"> 123 <target>r_clavicle</target> 124 125 <bone name="Bip01_R_UpperArm"> 126 <target>r_upperarm</target> 127 128 <bone name="Bip01_R_Forearm"> 129 <target>r_forearm</target> 130 131 <bone name="Bip01_R_Hand"> 132 <target>r_hand</target> 133 134 <bone name="Bip01_R_Finger0"> 135 136 <bone name="Bip01_R_Finger0Nub"/> 137 138 </bone> 139 </bone> 140 </bone> 141 </bone> 142 </bone> 143 </bone> 144 </bone> 145 </bone> 146 147 <bone name="Bip01_L_Thigh"> 148 <target>l_thigh</target> 149 150 <bone name="Bip01_L_Calf"> 151 <target>l_calf</target> 152 153 <bone name="Bip01_L_Foot"> 154 <target>l_foot</target> 155 156 <bone name="Bip01_L_Toe0"> 157 158 <bone name="Bip01_L_Toe0Nub"/> 159 160 </bone> 161 </bone> 162 </bone> 163 </bone> 164 165 <bone name="Bip01_R_Thigh"> 166 <target>r_thigh</target> 167 168 <bone name="Bip01_R_Calf"> 169 <target>r_calf</target> 170 171 <bone name="Bip01_R_Foot"> 172 <target>r_foot</target> 173 174 <bone name="Bip01_R_Toe0"> 175 176 <bone name="Bip01_R_Toe0Nub"/> 177 178 </bone> 179 </bone> 180 </bone> 181 </bone> 182 </bone> 183 </bone> 184 </bone> 185 </skeleton> 186 187 <skeleton title="XSI biped" target="biped"> 188 <identifier> 189 <root>Biped_GlobalSRT</root> 190 </identifier> 191 192 <bone name="Biped_GlobalSRT"> 193 <target>root</target> 194 195 <bone name="Biped_Spine01"> 196 <target>pelvis</target> 197 198 <bone name="Biped_Spine02"> 199 <target>spine</target> 200 201 <bone name="Biped_Spine03"> 202 <target>spine1</target> 203 </bone> 204 </bone> 205 </bone> 206 <bone name="Biped_Lshoulder"> 207 <target>l_clavicle</target> 208 </bone> 209 <bone name="Biped_Lbicept"> 210 <target>l_upperarm</target> 211 212 <bone name="Biped_Lforearm"> 213 <target>l_forearm</target> 214 </bone> 215 </bone> 216 <bone name="Biped_Rshoulder"> 217 <target>r_clavicle</target> 218 </bone> 219 <bone name="Biped_Rbicept"> 220 <target>r_upperarm</target> 221 222 <bone name="Biped_Rforearm"> 223 <target>r_forearm</target> 224 </bone> 225 </bone> 226 <bone name="Biped_neck"> 227 <target>neck</target> 228 229 <bone name="Biped_head"> 230 <target>head</target> 231 </bone> 232 </bone> 233 <bone name="Biped_Lthigh"> 234 <target>l_thigh</target> 235 236 <bone name="Biped_Lshin"> 237 <target>l_calf</target> 238 </bone> 239 </bone> 240 <bone name="Biped_Rthigh"> 241 <target>r_thigh</target> 242 243 <bone name="Biped_Rshin"> 244 <target>r_calf</target> 245 </bone> 246 </bone> 247 <bone name="Biped_Lhand"> 248 <target>l_hand</target> 249 <bone name="Biped_Lfingers"/> 250 </bone> 251 <bone name="Biped_Lfoot"> 252 <target>l_foot</target> 253 <bone name="Biped_Ltoe"/> 254 </bone> 255 <bone name="Biped_Rhand"> 256 <target>r_hand</target> 257 <bone name="Biped_Rfingers"/> 258 </bone> 259 <bone name="Biped_Rfoot"> 260 <target>r_foot</target> 261 <bone name="Biped_Rtoe"/> 262 </bone> 263 </bone> 264 </skeleton> So... if you notice in the code above, there are 3 sections (Philip please correct me if I'm wrong here). Rows 1-56 is defining the standard biped. That is a generic biped that the game engine uses. Rows 75-185 is the 3ds Max version of the biped. It is saying for example... in row 100 & 101 that 3dsmax bone named: Bip01_L_Clavicle equals l_clavicle on the generic biped (see row 10). Rows 187-264 is the XSI version of the biped. It is saying for example... in rows 206 & 207 that XSI bone named: Biped_Lshoulder equals l_clavicle on the generic biped (see row 10). Sooooo, what I foresee for Blender is a similar variant that is like the 3ds max and XSI versions that will need to be created. It would have the same number type, size, constraints, etc... of bones (this can hopefully be achieved by importing an existing .dae file) - however you can rename the bones as Blender requires (maybe it doesn't care?). Once the changes are made you need to make a bit of code to tell the game engine what the new bone names equals on the generic biped. Hopefully that is somewhat sensible... let me know if you need some clarification. In the past we had requested programming to support vertex animations. I'm not sure what the status of that is or ever will be, but that would accomplish the same thing. In the short term, for an immediate solution, we have the ability to create as simple one bone animation/rig that would effectively do what you want to do. It just isn't something as easy for the artist as exporting an unboned vertex based animation.
  24. There you have it! I haven't really had a need in the past to do such an animation, so I don't think you'll find baton twirling to be frequent motion Yes, there are numerous motion capture files in the repository. I forget the format, but I believe some of them could work with blender (though most were intended for max and it's Character Studio software). These aren't perfect, but they provide some great fluid animations. I used many of them with slight alterations (to get them to repeat and loop properly, shorten to one action per animation, etc...).
  25. I think it may be possible to animate the prop point nodes. I've never tried it. Only one way to find out though Nice work with your first ever animation! This shouldn't require any coding, what do you think you need to code?
  • Create New...