Modeling the Enterprise in Cinema 4D

[dan1701a]

Originally Posted by scifieric

Now that's one heck of an idea!

Yeah, who wants to take on that challenge?

Seriously, it seems like many of the techniques you use to model the ship are the same no matter what app you use (with the possible exception of Blender). And most of the terms are the same between apps (heck, even Moray has an "extrude" function). Somebody should be able to put a generic tutorial together with cross-refs between apps, so that when one calls for a "lathe" and another calls for a "spin" everybody will know what it's talking about. Or maybe someone could simply gather all the different terms between apps and cross-ref them as a start.

And no, I'm not volunteering!

[scifieric]

Originally Posted by dan1701a

And no, I'm not volunteering!

But it sounded like you just did ...

LOL!

[evil_genius_180]

That's a great tutorial so far, Dan. I'll have to get a better look when I'm not so tired and see if there's anything I can borrow on the ship I'm building. As you say, it's all similar in any app. Between you and Eric, I don't think anyone on this site has any excuse why they can't build this ship.

Originally Posted by dan1701a

And no, I'm not volunteering!

I thought Jedilaw was volunteering. He did say "we" should make the super tut...

[Roliba]

Yes, I deffinatly heard him volunteer.

*Teach you to hide my droids... sniff.

[dan1701a]

Originally Posted by scifieric

But it sounded like you just did ...

LOL!

I'm having a hard enough time with the B/C deck...an uber-tutorial would pretty much wreck my marriage!

[dan1701a]

And, as an FYI (and a bump to keep this thread near the top), I'm still working on the little nit-noid stuff. I finally got my B/C deck to work properly, so as soon as I get a chance I'll re-start the tutorial. I think, though, there may be fewer common techniques between C4D and other apps, so it may not be as helpful, but maybe somebody will get something out of it.

[scifieric]

I tend to find that I learn something, even if there is no tool similarity with my application. Even if it just gets me to think of a new way of doing something, it's worth it!

[dan1701a]

Originally Posted by scifieric

I tend to find that I learn something, even if there is no tool similarity with my application. Even if it just gets me to think of a new way of doing something, it's worth it!

And hopefully I'll learn an easier way to do it!

[Roliba]

Originally Posted by scifieric

I tend to find that I learn something, even if there is no tool similarity with my application. Even if it just gets me to think of a new way of doing something, it's worth it!

That's it exactly. Most of us here already have a fair to midling grasp of the programs we use. The real help of tutorials is to get us to think of a problem a different way. For example, for my secondary hull, I use a lathed spline, it never even accurred to me to use a cylinder and scale the sections down. The bitch of it is, both acheive exactly the same thing.

[dan1701a]

Originally Posted by Roliba

That's it exactly. Most of us here already have a fair to midling grasp of the programs we use. The real help of tutorials is to get us to think of a problem a different way. For example, for my secondary hull, I use a lathed spline, it never even accurred to me to use a cylinder and scale the sections down. The bitch of it is, both acheive exactly the same thing.

Until I learned how to use the "close polygon" function of C4D, the reason I used the cylinder is, when I Boole'd the fantail, it left me with a solid surface and few, if any, mesh errors. Doing a lathe, I discovered, gave me mesh errors when I Boole'd the fantail.

But some of the techniques ScifiEric uses tend to turn the light bulb on for me, and that's what I hope to do for others...as soon as I make sure they work for me, and they're repeatable.