Also don't compare yourself to others, the only measure of progress that counts is, do you know something today that you didn't yesterday? Can you do something better today than you did yesterday? The rest is bullshit. Your ability to see what looks goods will advance more quickly than your ability to actually do it. (If you are tempted to whip out your mobile phone right now, STOP, go and look up how to do screen shots eh?)ħ. Post a screenshot and include the whole Blender window - a picture speaks a thousand words. Tell us what you are doing, what you expected to happen, what did happen, what you did to try and fix it. No one minds helping those who are making an effort. Don't think about "making a project" that brings all kinds of expectations with it you don't need. Spend a part of your allocated daily time with blender just messing about with what you know so far. These are learning exercise, sketches, not finished masterpieces, don't get stuck obsessing over it at this stage as repetition of the basics is key and you won't get to do that by spending hours obsessing over one settings. Give each one your best shot, and move on. This is what forces you to not just get stuck with the tutorials.Ĥ. Instead of a donut, make a cupcake or something. Similar in that you don't need tools you haven't learned yet, but not the same so you have to start making your own choices. Now make something similar, but not the same. This is the challenge, how much can you remember?ģ. Makes notes on the bits that didn't stick the first time that you have to look up. This is the the monkey-see-monkey-do phase.Ģ. Make notes as you go, particularly of hot keys. Even if they don't teach you the specific thing you want, after doing the beginners tutorials you will at least have a feel for the program, understand the basic navigation controls and have the vocabulary to ask the right questions. Not only will this save you a great deal of time and frustration, but probably from rage quitting as well. ![]() Sheep it A free render farm through distributed computingīlender Stack Exchange for technical help with Blenderīlend4Web to export your blend to the webīlender Discord for live chats with other Blender usersĬC0 textures and additional contents and services to support - €9.90 / monthġ. P3D.in: share and view your Blender models New to Blender? Check out our Wiki of tutorials! I recommend Grant Abbitt’s tutorials they’re all concise, calm, well-designed, bite-sized (which means success is rapid, frequent, and that’s encouraging and motivating)./r/blender is a subreddit devoted to Blender, the amazing open-source software program for 3D modeling, animation, rendering and more! That really paid off after a few weeks of practice I am totally comfortable with the interface, remember all the most-used hotkeys, and can create not only blocky sheep but other baked goods entirely on my own ). I went from the donut to low poly tutorials next because I was overwhelmed by the donut and realized when starting on a non-tutorial cupcake I hadn’t actually retained much. This is super important at the start so that things become less confusing. Whatever you decide on next, do it soon, and if you can, do some of it daily, to better anchor the processes in your mind. I’m still putting that off myself until I’ve got a solid handle on modeling. You can make Eevee renders look amazing, and it can certainly handle the donut, but it takes knowing Eevee better. No eye-rolling here the donut is almost a right of passage for new Blender users.Īnd yours is very nice – I especially noticed the dough part, which often gets less attention, but yours is great. It’s been a brilliant place to start learning Blender. I know that “doing a doughnut” makes some people’s eyes roll, but for me it was completely engrossing and I learned so much. Eevee took 00:34 for 300 frames so around 0:06 per frame ![]() Out of interest, I also ran it with Eevee, which is much faster, although the output is noticeably less good than cycles. The final render tie with cycles took 05:45:00 for 300 frames so around 1:09 per frame - I let it run overnight. It’s obvious slower than newer more powerful computers, but not terrible. ![]() I rendered out in cycles, which works well. But once I figured out the tricks, I was into action. It took me a while to work things out on Mac with trackpad as all the documentation and online videos are using Windows and 3-button mouse. I had no idea if it would even work, but actually it is a buttery-smooth user experience. I had to use what I have which is a MacBook Pro 16-inch from 2019:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |