This thread is [currently] solely for the links to

1. application manufacturer's websites
2. tutorial sites for different apps
3. resources for different apps (plugins, objects, that sort of thing)

For example:

NewTek - makers of Lightwave 3D
Flay.Com - LightWave 3D News and Resource site - massive Lightwave resource, updated almost daily, with a searchable database of plugins and tutorials
LightWave Tutorials on the Web Splash Page - HUGE links page of Lightwave tutorials

* * * * * * * * *

Nope, I do it pretty much the same way.
1) One model which is purely alt mode; no hidden robot parts at all.
2) One model which is purely robot mode (any hidden weapons are on another robot mode only model, which is only used when those weapons are))
3) One model whichis fully transformable. This is used for transformation scene animating.
The biggest advantage to this way of working is that you don't need to have extra parts loaded that eat up memory; believe me, when you're working on a big scene this is a VERY good thing.

[/quote][/quote][/quote]

 

There's Photoshop Art and FX Tutorials, it have a Photoshop coloring tutoral there.

 

Ok so here it goes... Here's how I do the huge bots (metroplex/Trypticon).The steps apply to the smaller batch as well... This procedure is for 3dsmax but should apply to other as well. The terms used are all in the helpfile(s) for further explanation.

1)Model everything, and then make sure it looks good. Also make sure that it can transform to resemble the alt mode.
2)Now create a proxy of that robot that's just a bunch of cubes but these cubes share the same bounding box and pivot/rotation points as the highres original.
3)Now Xref the highres with the lowres proxy. You can now animate the lowres and when you render Xref will pull in the highres for the render. Makes animating a breeze, plus it has one major benefit. It separates your model from the animation. Meaning you can keep on continuing to apply texturing and materials and not worry about the animation thats assigned to the model.
4)So when it comes to animating the transformation part I have another xref thats for the alt mode in "reverse". This has all its parts alligned to the parts on the robot.
5) I then create a slider widget in max that will "blend" between the two. This slider pretty much controls the animation keys set to transform between pose 1 and the alt mode. Because it's all set in a expression that controls the slider, all I need to do is animate the slider and watch the robot "transform" in response...
6) weapons and all that other stuff "morphs" or fades out/in as needed. Their transparency is linked into the widget animation as well.

*advantage to working like this*
1) separates render version from animation version, light and responsive animation scenes are a result.
2) continue texturing and lighting without having to worry about losing the animation
3) Do it the way the big studios do ! : )

*disadvantage*
You need to be able to script somethings and tie them all together. Also don't overwrite the scenes your Xref'ng to or your screwed.

Thats it, easy innit?  

C.