Username:    Password:    Remember Me?         

Reverie World Studios Forums - View Single Post - Modding races
Thread: Modding races
View Single Post
  #9  
Old 07-20-2009, 12:19 AM
Joseph Visscher's Avatar
Joseph Visscher Joseph Visscher is offline
Reverie World Studios - Lead Level Designer, Senior Gameplay Programmer, 3D Animator, 3D-2D Artist.
 
Join Date: May 2007
Location: Canada B.C.
Posts: 1,279
Joseph Visscher has extremely good reputationJoseph Visscher has extremely good reputationJoseph Visscher has extremely good reputationJoseph Visscher has extremely good reputation
Default

Quote:
Originally Posted by Aametherar View Post
I figured something like that, but there is still the fact as mentioned above, creating unit skins isn't exactly something you can just whip up, it takes a lot of work! (unless you live in photoshop, which I don't)

you mean texture, skin is the mesh envelopes in the model, made with 3ds max.

there are mutiple steps for creating a new unit:

Modeling object in 3ds max

UVW mapping / texturing -- using photoshop to create a .dds then layering it onto the unit aranging every single face of the model,, if you have over 300 faces,,, well thats several hours of work not even including creating the texture!

Creating blip or bone skeleton and staging them inside the mesh of the new unit, adjusting all the limit angles of the bones (Elbows can not invert and rotate backwards right?)

A skin modifier or commonly known as "Rigging" must be applied, it works with the blip or skeleton of the unit to grab each and every poly of the mesh; just like our flesh is attached to our bones. The influence of each and every poly must be adjusted perfectly (if you lift your arm, is your right toe forced to lift right up with it? No.).

Now will the finished model and it's rigged you need to animate it via blip/bones.

Using the bones to create keyframe animations you bring your new unit to life; this is when you can have your new unit pick his nose and scratch his butt at the same time.

Then begins the creation of all the animations needed such as, run, walk, attacks, death, idle actions (picking nose goes here!) to wound to brutal counter attacks.

Next is using dof's exporter to export your mesh and animations to files the game can understand.

The exported animations and meshes are then opened with our model viewer which helps us set various things such as default unit scale, animation time and most importantly animation events which tells the game engine what to do on that animation, such as when a sword should 'hit' and cause damage on what frame in the animation(Why wound you get damaged from a sword hit if he's still preparing to swing the sword at you?).

Next is to Create the main unit file which links all of the animations and their file locations, unit properties, abilities, and all functions required basic and advanced, most of this is already done with our current 'Proto' System which sets up 'default' function actions in an undetermined coding environment.

Your unit should be available in the game if everything is error-less, if you made an error, the game will tell you where the error is caused.

You can then adjust some other files for your unit, creation small icons for your unit on the hud, his abilities and his production button.

You can then add a production button to another building/object/unit or what ever you want to do with the Icon etc. you can do pretty much anything.

You want your new unit to rain down out of the sky in a large meteor? Well, create the meteor object, create tons of cool effects, make it as a projectile, then create a new object to shoot the projectile from the sky on a location way down below,,, on projectile hit spawn your unit. Bang, you got yourself a kickass new wizard ability: "Mentor Minions"

Only limit your going to meet is time.

Sorry about the grammar, I'm about to go to bed heh.
__________________
Joseph B. Visscher - JBV3737

Bugs aren't the problem, figuring out how to fix them is.
Reply With Quote