Yeah, we're actually using MDT5 at work now. Took me a while to swap from using primitive solids and boolean solid editing commands to using the parametric feature based modeling in MDT. By the way, all the rendered pics I've posted were created using AutoCAD R14 and primitive solids.

Lots of work.
Autodesk's way of doing parametric feature modeling isn't nearly as easy for me to use as ProE or solidEdge for some reason. I think Inventor is supposed to be better in this regard, but I'm not sure.
One of the best things about Mechanical Desktop is that Algor (FEA) has a package that integrates with MDT. It has a feature called direct memory transfer, and creates the surface mesh
inside MDT... and then exports the mesh data (matrices) to ALGOR. It's so much easier to create good FEA models using this process, instead of creating meshes from the ground up in ALGOR's modeler, or using IGES and hoping things come out well (and they never do).
All those tips for rendering work just the same in MDT4/MDT5 as they do for ACAD R14/2000/2002. I don't think MDT has any different or better rendering options... perhaps just a few better shading and orbiting commands.
While I'm at it, another tip, if you work with shaded models much: if you have a decent graphics card, go to Assist | options | system | properties. Changes acceleration from software to hardware, and browse and find the wopengl7.hdi (maybe 6 in MDT4) driver. This will allow the GPU to accelerate shaded models instead of doing software shading. With a Radeon 8500, the difference is astonishing. Even with a GF2 GTS, it's much faster in hardware. It can get rid of some odd shading artifacts too, but it seems to introduce a few of its own (my crosshairs tend to leave "ghosts" now?). There's also a D3D driver, but it had several glitches when I tried it.
Whew, need to get back to posting single word or smiley posts.
