[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vr / w / wg] [i / ic] [r9k / s4s / vip / qa] [cm / hm / lgbt / y] [3 / aco / adv / an / asp / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / qst / sci / soc / sp / tg / toy / trv / tv / vp / wsg / wsr / x] [Settings] [Search] [Mobile] [Home]
Settings Mobile Home
/3/ - 3DCG

Thread archived.
You cannot reply anymore.

File: FB_IMG_1547520670817.jpg (150 KB, 1262x2048)
150 KB
150 KB JPG
Are tutorials even useful for beginners? You're basically just watching a movie and following the persons movements.

Someone who finished the donut tutorial (for instance) won't know much more about actually modeling in 3d, but they may know more shortcuts and may know how menus work better than they did before. But this is all info they could've learned through 20 minutes of reading. It's like reciting the alphabet backwards by copying someone reciting the alphabet backwards and then being proud because you recited the alphabet backwards.

You will learn 90% more effeciently by just trying to render things you want to render and googling tips along the way.

Am I wrong?
File: wisepepe.jpg (21 KB, 320x320)
21 KB
>Are tutorials even useful for beginners?
>You're basically just watching a movie and following the persons movements.
This is essentially how any form of instruction works, especially something that is hands-on
>they may know more shortcuts and may know how menus work better than they did before. But this is all info they could've learned through 20 minutes of reading.
I've found there's a big difference between reading and actually doing something. When you're doing something, and following instruction, you'll learn it much better, especially because there is an end goal in mind. In 3D, knowing shortcuts is absolutely essential. Even if that's all they learned from the tutorial, it would be 100% worth it.
>It's like reciting the alphabet backwards by copying someone reciting the alphabet backwards and then being proud because you recited the alphabet backwards.
As an example, take painting classes. Yes, you're following the motions and copying, but that's the point. Even if the work isn't original, you're learning the fundamentals. You're beginning to understand how the bristles on the brush bend, and how it affects the stroke. You're learning how to mix colors. You're learning everything you need to be able to make your own original work in the future. Yes, you can just read about these things, but if you have someone to show you how, you'll learn it much faster. In my experience, for learning the fundamentals, it's far more efficient to start out copying and imitating, rather than to dive in and do something original from the get-go.
>You will learn 90% more effeciently by just trying to render things you want to render and googling tips along the way.
Not for me. I started out doing this, and went nowhere with it. Everything sucked. Objectively. It was awful. The moment I decided to sit down, follow tutorials, and take serious notes, my skill advanced faster than it ever had.
>Am I wrong?
In my opinion, yes. But this is only my experience.
Even doing something like a shitty paint-by-numbers class, you can learn something. Even if your result is the exact same as the instructor.
You're learning how paint works, how it feels, how it's applied. Mixing and other shit. By the end you won't be an artist or even know how to paint, but you've taken that first step to knowing, which is more than someone who didn't.

As far as 3d tutorials, some people don't know what they want to do. They just want that foot in the door. Having something to start from when you've got no knowledge of the program works gets you on your feet faster than doing nothing, and learning the wrong way of doing something.
Once you're on your feet and know the bare bones basics, then that's a good time to start paving your own path and figuring shit out on your own. If you've got a problem, then google it and figure it out.
If I'm about to learn a new program or something, I'll watch a tutorial or something to get familiar with the workflow. I won't actually do the tutorial, just watch and absorb the knowledge. But we all had to start somewhere.

That being said. Nothing infuriates me more than people posting their tutorial results for "internet points", and then people actually praising them for essentially just following the instructions like a Lego set. They didn't do anything to be proud of, and if left on their own, they couldn't replicate their results. So at the end, they didn't really learn anything. Which I guess defeats my point of tuts being useful. I still think they might be though for people that don't know jack shit about a program and can't even orbit the viewport.
Op here. These are both very true and, thinking about it, I also followed tutorials until I understood the basics. What I found though was that after a few video series I would be learning almost nothing new, just copying the man in the video. I think tutorials are useful but it's like a slope in a way. The first tutorial is a 100% improvement, teaching you the basics of your program and getting your foot in the door. But after a few you kinda stop learning anything new and the value of learning goes significantly down, leaving you with a finished product you didn't really accomplish yourself.

I found myself becoming complacent with these tutorials and not wanting to take the extra step to make something of my own. It's super gratifying to have a finished product that looks nice so you can show it off to your friends/family. I think this is a problem we see a lot on this board or other forums. I liked the analogy of a lego set, you can put together something that looks very complex and feel good about yourself, but in reality you didn't do much on your own and instead just followed very simple instructions.
I think the important thing is to see the tutorials as a means to an end. Rather than a way to have a bunch of "projects" to do.
I usually always have something I'm working on, and 90% of the time, it will incorporate something that I've never done before, even after years of 3d. These are the times I find helpful to look at tutorials and forums and stuff. Like I said, not as a project to copy, but as some extra insight into a problem and a potential way to solve it while bringing my own experience to the table.

Which also kind of brings up a point on how a lot of people doing tuts tend to waste your time. A lot of times I'll be looking for something fairly advanced and niche, which isn't too hard to find info for, yet time and again the tutorials waste 30 mins doing basic shit and going over how to work the program from the position of an absolute beginner.
That, or they won't get into more advanced usage and instead do the most barebones basic implementation of what it is your looking for. Which tends to suggest they don't know jack shit about what it is they're talking about. Which means the entire tutorial was a waste of time.

Maybe I should just start making tutorials that don't waste people's time. Could be a decent way to rake in that Patreon money.
Eventually you hit a point where a tutorial, or a lecture, or a video series, or a book teaches you one new thing you didn't know, but that new thing is a thing that'll have you saying "Fuck I wish I'd know that six months ago, I could have saved A LOT of time".

That's just the nature of gitting gud. If you aren't learning ANYTHING, you aren't picking hard enough tutorials, or you need to move on to more abstract / broader concepts (what is called "Theory") wherein your objective is to understand some large thing (like how light works) and then implement your own application or semi-innovation based on your understanding of the topic and the work of others in the field.
This isn't just an art thing, it's an "human endeavor" thing.

You should try and make a tutorial so you can understand how teaching, video editing, writing / composing a video, public speaking, are all their own entire skillsets as difficult to do well as being a CGIfag.
Also 30 minutes, or even an hour, is "wasted" in a tutorial then you are watching very short tutorials, try some tutorial series that are 20 or 30 or 40 hours long and have you make an entire huge project.
Even if a lot of it is stuff you already know, you're going to pick up tons of "oh shit, there's a shortcut for that? wish I'd know that" stuff along the way
A lot of the stuff I want to teach is mainly theory anyway. There's a ton of tutorials that go over mechanics and shit like that, but nothing that actually teaches artistic shit. I imagine that's why there's so much trash now anyway. Good skills, shit art skills. I've at least had the added benefit of going to school for art, so that'll help for credibility at least.
I think it's important to have those skills, but also it gives me an excuse if I'm not teaching some technique that's industry standard.

But yeah, I'm mainly looking for shit on theory anyway when I'm looking for tutorials. I'm not specifically looking for tutorials, just mainly that I'd have a problem, and I need it solved. I understand a good bit of theory and stuff, especially strong on the art side of things. So theory stuff would mainly be relegated to shit like learning unwrapping better or better topology. Like I said, those tutorials are bare bones as all hell and just go over how on an extremely basic sense.

I'm not going to do 30-40 hour long tutorials because that's basically unpaid work (sounds douchey but I'm pretty busy), . Even if I'm learning something, I usually have enough on my plate that my free time is nonexistent. That free time is better spent imo, working on personal shit that I can sell later for passive income.
Not to mention a lot of times, the "oh shit moments" usually apply to some small thing that is useful, but so niche it's forgettable, and probably doesn't even apply to things I'm doing now.
Luckily there are neither good tutorials or good information off of google, so no matter what you do you're screwed into several hundred hours of accomplishing absolutely nothing.
File: 1559705059380.png (105 KB, 238x164)
105 KB
105 KB PNG
new into this, any tips bros?
Arrimus 3D have like 700 videos for just 3ds max and workflow as a whole u can find something useful there
Protip: It depends on your personality/how you learn skills, and you generally have to do both.

Trying to Google everything will often make you feel lost and say "oh god how the fuck do people model a house from start to finish, this is impossible, just show me" - which then results in you watching a tutorial and receiving answers to the questions you already had AS A RESULT OF experimenting (how do I make sure the camera doesn't clip into the walls, how do I combine two meshes together, how do I place five windows on a wall with even distances between them, etc.), and common workflows/tricks that will stick much better due to you actually having a direct, immediate WANT for them. Kind of like following a tutorial for some medical procedure while you're literally in the middle of bleeding out. And a lot of the time they're questions you can't even properly put into words, but once you see somebody using the standard way of solving a problem, it's an immediate "oh SHIT" lightbulb moment which you remember for life.

Conversely, just reading a book or following along with a tutorial will make you bored and "unengaged", because all you're doing is copying the steps to reproduce something, or even worse, simply being told what those steps are while you fall asleep in front of the monitor. Then once you try and model something yourself from start to finish, you realize that you still have to go back and Google 90% of the shit you want to do, because you forgot all of it due to having no personal "investment".

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.