Your Potato Computer Can RENDER ANYTHING (w/ Optimization)!

[Music] all right so blender has been sucking the soul out of your computer every time you open it to try and make something cool your endake ages your viewport is choppy as hell you constantly keep running out of GPU memory and the worst of it all you are afraid of unintentionally turning into an IED when your computer finally decides to give in and just blow up on you so I here to try and prevent that from happening to the best of my ability I've been using blender for over 8 years now 90% of what was

spent on really below average laptops that struggle to render even a single frame but I still somehow managed to make at least in my opinion more than good enough ambitious even in some cases renders with them so I let you know everything I know about optimization in blender I'll take you through all the settings and preferences you should change in blender in order to get the best performance out of it not just check check Boxes by the way blindly without understanding what they actually do so you can actually learn something we'll also check out some

useful add-ons and extensions that might help you with with this whole optimization thing and at the end I will even sprinkle in some laptop and computer recommendations if you're about to buy a new computer anytime soon or looking for an upgrade to your current workstation make you understand what you should be looking for when buying a computer if you're looking to get into this blender 3D CGI hobby seriously all right there's a lot of ground to cover so let's not waste any more time and just get into it make use of the chapter marks if

you think you know a certain tip and trick while I'm covering it so you can save even more time and yeah talking of saving time let's not waste any time on on obvious things like obviously you have to change to Cuda mode if you have a non-rtx Nvidia GPU and Optics mode if you have an RTX Nvidia GPU and of course you should switch to GPU compute from CPU here in the render properties if your device has a GPU cuz gpus are just faster than CPUs they are the rabbits in the turtle and rabbit race

only they're not stupid and cocky like the rabbit from that story watch this video by Adam Savage if you still need some convincing and also obviously you should always use the latest version of blender 2 cuz the development team is always improving things in it just recently they introduced GPU based D noising for the open image D noiser and GPU based compositing in blender 4.2 that has been revolutionary to overall rendering performance at least in my case so why wouldn't you keep blender updated and why wouldn't you use a d noiser either and yeah while

we are talking about D noers what I've also noticed is if you don't have a good fast new GPU it is always better to change this start sample here in the viewport section to something higher like 35 or so so weaker gpus is rendering the scene and den noising it at the same time right from the first sample can be a little taxing so keeping it at a higher number can take some load off of the computer and does improve your overall viewport performance yeah that's it let's now move on to more important things these

were just general things that anyone and everyone using blender should be aware of before they even touch a key and start making anything within the software so I thought I would get it out of the way right at the beginning all right let's now get to the Crux of the most foundational problems your 3D scene might have that might be causing a performance hit and probably to no one's surprise it's either the poly count or the the texture resolutions you're using in your scene you can't just download a bunch of models from sketch Fab apply

4K materials on them and use 4K hdris in the scene and use a bunch of procedural materials and geometry nose generators in them with millions of vegetation assets spread around and expect nothing problematic to happen that's stupid you got to do some housekeeping at the least like for example a ground photo scan like this with around 60,000 faces which in my opinion is fine most modern computers should be able to handle that kind of geometry but look what happens when I use a decimate modifier on it a ratio of .5 slashes the poly count by

exactly half and you barely lose any visual fertility in the model even the ratio of 0.1 looks fine to me from a distance so it would be really stupid to not use the decimate modifier even when your computer can handle it same goes for the merge by distance shortcut if you are downloading a third party model from the internet chances are it was not modeled in blender and has a ton of overlapping geometry that you can't actually see with your naked eye but try the shortcut m in the edit mode of the model and select

the merge by distance option from the drop down that pops up and watch how many vertices get removed with this method the weld modifier also works in a similar way so you can use that too if you want a non-destructive workflow there's also the unsubdivided function that you can use by right clicking the mesh when in edit mode which does exactly what it says it just un subdivides a mesh and all three of these methods are great automated ways to slash down your polyc count so yeah you have no more excuses get your polyc count

under control and chances are most of your problems might be fixed then and there also while we are talking about polyon based op optimization I hope you're already using the alt D shortcut to duplicate everything and not the shift d shortcut like altd creates an exact clone is not causing any performance it while Shifty creates a twin they might look the same but they are two different individuals sucking their own GPU and CPU resources respectively so yeah use all D for copy same goes for collection instances too if you need to copy a whole collection

just right click on it and go to instance to see and then use that instead of actual p class collections all right moving on if you have worked out your poly count and you've still got some issues maybe it's time to now check out the textures you've used in your SE I've seen a lot of beginners just download 4K textures and 4K hdris just cuz they think higher the resolution means better the quality in the final render but it's not a video quality drop down menu like on YouTube that will magically make your renders just

look good cuz you used high resolution assets your render looks like [ __ ] cuz it looks like [ __ ] not cuz you use low quality resolution textures for example look at the this render I rendered it with different texture resolutions by using the simplify panel and blender and from a distance I bet you can barely tell any difference between the renders yes the 128bit and the 256 bit resolutions look a bit more floofy for lack of a better word but the difference between the 4K texture one and the 2K texture one and even

the 1K texture one is negligible to my eye if I'm being honest with you so why would you want to bog down your computer with these super heavy texture files when you can get away with such low resolution texture files without any significant quality hit in your fin render so yeah use the simplify panel and clamp your textures and render out a few test results yourself if you don't trust me but stop using 4K dexes just blindly please same goes for procedure materials too I know they're fun to play around with and they're versatile as

hell but all that math and all that processing will add up and you'll definitely feel it in the viewport from time to time so I'm not saying don't use them use them but just know they are coming at a performance cost a better alternative would be to get a result you're happy with them and then just take those textures that's a much better way to make use of procedural textures on a weak computer if you ask me by the way while we are talking about texture optimization do Purge your blend files from time to time

too to get rid of any unused unnecessary texture files or object data that might be floating around in the background from some weird object that you imported long long time ago but aren't using anymore in the blend file purging them from this menu here in blender will ensure they don't bog down your system in any possible way in the background but yeah all these tips that I mentioned in this chapter were applicable more for people use a ton of third party assets from websites like sketchfab or quickel or CG Trader or fab.com that is releasing

very soon but if you do everything by yourself within blender like model and texture everything yourself as tedious as it sounds it will always perform better than most of your other scenes that you made using only third party assets cuz blender knows exactly what's going on there cuz everything was made inh house as stupid as this STP sounds doing everything yourself within blender might be the best optimization tip I can give you if I'm being honest just go easy on the subd modifier and don't bevel your model to Oblivion and you should be fine by

the way in the preferences you can turn on this GPU subdivision option as well if it's not already turned on by default this again just allows your GPU to handle the subdivision you see that's it but yeah these were some foundational tips let's now talk about some specific render settings you should be wary of starting off with this noise threshold check boox here in the render properties tab cuz Ive heard some absurd tips around this field it's it's so stupid because if I understand the explanation mentioned in the blender manual for this field it's literally

just a a and b option should the render hit the sample count first or the noise rest first which is just a way to measure the noise in a render that's it and I hate using the noise threshold field cuz I find it's always better to just mention the sample count this is what I do I put a big sample count in something like 1024 in this field and watch my scene get rendered and just make note of when my render starts looking cleaner to me like for this render here I can see after the

80th sample there's negligible difference in the noise that's getting result old so I set the sample count to somewhere close to 80 and that's it the rest of the noise I just leave it to the D noiser I rarely ever go above 200 samples with my renders cuz the D noises are so good these days they do all the work for you so why would you not make use of them so yeah that's what I do if I have misunderstood the noise threshold field please do enlighten me in the comment section below I would love

to learn more about how it works I don't want to be the source of misinformation here so please let me know and yeah by the way you're right if you're thinking won't the low sample count sometimes cause tempo Bal noise and moving animations you're right I've seen it too it happens a lot with my renders too especially the ones with a lot of glossy Reflections but more often than that in my observation higher sample counts also don't fix those temporal artifacts you'd have to go really really high in the sample count to resolve them I

think so a better way to get around that would be to just set the sample count to something low like 50 or 100 and then just use the D noiser and resolve resolve is a great temporal denoiser that you can use for free by the way it's more approachable in the paid version cuz you can do everything in the color tab itself but the features there in the free version too you just got to put a little extra effort into it and do the noise reduction in the fusion tab rather than the color tab but

it's not too bad trust me it's super easy I'll link is super easy and super fast tutorial in the description below so do check it out but yeah in short sample count should be below 200 or even 100 in most cases I barely ever go above 35 to be honest so yeah dial down your sample count and let these modern D noises do all the work for you moving on another panel to pay attention to here is the light BS panel to explain it in short it just measures how many times a light will get

bounced around in your scene the more bounces you have obviously the more time the computer will take to calculate those bounces easy and again just look at your vport and observe if you see any difference in the render when you lower these numbers I in most cases rarely ever go above four light bounces and if you don't want to experiment with it all and put all this effort into it just go and select the fast or limited Global illumination preset here from the preset pan that's it also the type of lighting you use in your

scene can also affect render Times by the way based on my research the sunl lamp is known to be the most performant and then the rest of them Point lights a lights and spotlights are pretty close to each other even hdris aren't that bad but what's worst is mesh lighting as far as performance goes this doesn't mean you shouldn't use mesh lights at all and only use sunlights all the time these are the stps you should know just in case that's it all right let's move on move on to one of my favorite optimization tips

which is changing the tile size field here in the lower end of the render properties pan it just decides how big the size of the tile will be when you render something the size of this box right here and if not anything else in this video at the least please experiment with this field and see what yields you the best performance for my GP I found a value around 2048 or 4096 yields me the best results you can start from 64 and go up slowly bit by bit to see what is the best number for

your GPU you might just save a few seconds here and there but they will add up in the long run especially when making animations all right then comes the persistent data checkbox another important field that you should just turn on if you hover over it you will know it helps and faster reenders cuz it saves a bunch of information as cash right when you render for the first time and thus it doesn't have to calculate all of those things again and again for subsequent frames or subsequent renders but yeah that's all the render settings I

mess with usually when looking to optimize there are other things you could experiment with to here like using camera calling that processes only the data that's visible to the camera this feature can help out a lot when rendering say a lot of vegitation in your scene so maybe some of it maybe goes off camera or is too far away from the camera you don't need the them processed for your SE cuz they're not in the camera basically so it's definitely worth turning on actually this vegetation thing just reminded me if you have really heavy objects

in your scene like a really dense tree or a photo scan somewhere and you can clearly see that the sole reason why your viewport is lagging the best way to handle that is to just go to their object properties and set their viewport display as bounds do that and that will definitely help in overall viewport performance but yeah back to the point there are other settings here too that are worth exploring like the fast GI approximation panel which stands for fast Global illumination approximation panel if you hover over that checkbox the bubble clearly says it's

for a faster viewport experience and reduced final render quality if you're okay with that so turn it on and you will clearly see it makes everything a little flatter and a little dull but hey the bubble clearly said it's meant for faster viewport experiences so try it out for the viewport if your viewport is being really laggy in the rendered mode and when you're ready to finally render maybe turn it off and you can learn what these individual sliders do by the way by either just playing around with them or just hovering over them and

reading the information bubble actually I would recommend you hover over every field you see here in the render properties Tab and read the bubble and decide if it sounds interesting or not for your use case if it does right click on it and read the online blend a manual about it too and learn about it even more cuz that's how I learned all my optimization tips like say for example this light tree check boox it clearly states in the bubble it's for instances when you have a lot of light sources in your seat all you

had to do was read that to know that if you're making a scene with a lot of light sources it might be a good idea to turn this feature on that's how you learn new things you can't expect to to learn and grow all the time through just YouTube videos or some post somewhere you saw on social media that's all I'm trying to say and now I think would be the perfect moment to talk about the best optimization tip in blender in my opinion and finnally enough you can never find a good tutorial on it

on YouTube so let me try and give it a shot I'm obviously talking about render L and I Know It confuses you it confused me too when I was a beginner but it is very simple once you get the hang of it so let me try and take you through it step one neatly organize everything that's there in your scene into collections you could do midr foreground background you could do top Center bottom or you could do head dick and feet it doesn't matter just put the objects in meaningful collections that's it do what I

do I just put everything that's relevant to each other into separate collections the more the better actually the point is to separate the most demanding objects in you see like in this scene the Rika the sidewalk the people on the sidewalk the buildings on the side the volumetrics are all in separate Collections and now step two is to make the render layers you do that by coming here in the top right press this little thing and selecting copy settings and that's it you've made a new render layer do that at least three four times the

weaker your computer the more layers you should have ideally cuz the point is to render every part of the scene separately so your computer doesn't choke cuz it's trying to do too many things at once you separate them into different layers and now your computer has to use lesser resources to render these separate individual layers you know that GPU has run out of memory error that keeps popping up when you try to render something which by the way you can keep track of by going to the bottom right part of blender and right clicking and

checking this video memory and system memory check box which is for GPU and RAM respectively you can expect that error when you see your vram closing into its full capacity and Randle layers in my opinion are the best way to get rid of that out of memory issue so yeah you make multiple layers and name them too if you want but now comes the important part in step three you have to go to the first layer click on this little filter icon here and enable this hold out icon thing you see here once you do

that you should now see that same icon here on the right in the outliner beside every collection now all you got to do is keep that first collection as is don't touch that at all but for the rest of them just enable this hold out icon when you do that you'll see only the contents of the first collection are now visible in the viewboard while the rest of them have this checkered Alpha mask thing on them if you don't see the alpha mask and just see like a gray color come into the render properties Tab

and enable transparent under the film panel here and then you should be able to see it and now all you have to do is go to the next layer once there all you have to do is not touch the second collection this time and do that hold out thing all over again for all the rest of the collections including the first one so now you got the second collection visible in the viewport but all the rest of them are transparent and that is it now you just got to repeat that process for the rest of

the layers for the third layer do it for the third collection for the fourth layer do it for the fourth collection and so on and so forth don't go crazy and make like 100 Collections and 100 layers that would be counterproductive but I would suggest is to stay under 10 and that should be good enough for most use cases now the elements of your scene are nicely separated in all these layers your computer isn't choking anymore cuz it has to render fewer elements at a single Moment In Time rather than doing all of it all

together but we still got to put all of them together at the end when the final image file is generated and we do that in the compositor tab all you have to do here is bring up the render layer node select your first layer bring up another render node and select your second layer another one for third another one for fourth and so on and so forth then we need the alpha over node we bring it in close to the first two render layer nodes and we join the first two render layer nodes like this

then we join the third Ren layer node to another Alpha node like this and then we join the fourth layer and then we join the fifth layer and so on and so forth until you have the last Alpha over node which we connect to the composite node here like this and then we're done you press render you'll see all your different layers getting rendered one by one and then getting mixed all together right at the end mission successful at least for my end I'm sure 90% of you are still confused as hell if you are

uh just ping me on Instagram or something and I'll help you out there I know this is complicated if you've never done this before but again trust me you want to learn optimization this is the most fundamental thing you need to get good at so take your time but learn it it's going to save you a lot of hair pulling in the future trust me o that was a lot right so let's just step back a little bit and finish this video off with some general optimization tips like render resolution there is no shame in

rendering a shot in 720p or even lower than that if your computer's taking too long to render 1080P or 4K resolutions the point is to finish a project and not let these tiny performance hindrances get in the way of you finishing your projects nowadays I just see people rendering in 720p or 480p and just using AI upscales in post to bring them to traditional high quality resolutions that to me sounds smart as hell cuz resolution at the end of it all is what finally decides how long a render is going to take so if you

can get away with a 720p render and some AI upscaling at the end of it all you have just saved a [ __ ] ton of time my friend believe me actually you know what skipping Cycles as a render Ranger Al together is not a bad idea either the EV render engine or the EV next render engine now is shockingly close to Cycles sometimes and much much faster in all almost all cases so it would be stupid not to delve into this Venture sometime for a project or two and see if that is easier for

your computer the resolution of the render the sample count and all of that crap will just go for a toss if you opt for the EV render engine and on similar Lin sometimes when I just have to check the animation or the flow of the overall scene I render the animation in the viewport more directly cuz that's all you need sometimes you don't need to render a full scene from scratch to just check if the fan is swinging at the right speed or not or if the legs of a character are moving at a realistic

Pace or not you can make all those deductions with just a viewport render same goes for step rendering as well you don't always have to render each and every frame for every scene you can enter two or three here in the step frames field and Skip every second or third frame just to see how the overall scene is looking before you go fullblown 100% render mode honesty some people just render half the frames and then use AI tools like flow frames or Optical flow frame interpolation tools to generate the in between frames later on and

post this works great for animations that don't have any crazy motion or animation going on in them so you can save 50% of your rendering time right there which is absurd it's beyond optimization at this point it's just a smart thing to do I think actually another smart thing that pops up in my head is to use the control B shortcut to box select the region you want to see rendered cuz that's all you want to look at in that moment like maybe I just want to see how the hair on the cat is looking

in this shot so I'll just restrict the rendering region to be around that cat and that's it I didn't have to render the whole thing just so I could look at the cat that's saving a bunch of time simple things like these will save you a [ __ ] ton of time I can't tell you how many times I've just put a whole scene to render overnight for 12 hours or so thinking everything will be just fine when I wake up and then I wake up in the morning and I look at the render and

see these teeny tiny mistakes here and there which were completely avoidable if I had just followed the last three tips that I just mentioned but I didn't cuz I'm lazy and negligent so don't be like me be smart and remember these tips another thing to remember would be to always render an exr cuz it's easier for your computer to save exr files than say compared to a PNG file so yeah keep that in mind too and now on a slightly disappointing note you should maybe sometimes disable super demanding effects like motion blur which I know

sucks cuz you really want that motion blur sometimes but that's a really heavy effect and it definitely adds up to your overall render time but disable it in blender and add the motion blur in post if you want it won't look perfect but you will save a ton of rendering and processing time that could be used otherwise actually and it doesn't even look that bad if you ask me the same thing goes for volumetrics as well I know they make your ugly scene look 10 times better instantly without any effort but sometimes it's just not

worth it time wise so if you can let these extra effects go please do similar things like super demanding particle systems in your scene or crazy simulations in your scene or crazy displacements or any other heavy stuff in your scene is going to clog your computer's resources and you know that so you got to pull back sometimes in fact this next advice will sting a little bit but you have to know this that there's no shame in making something smaller something simpler or even stylistic for that matter that is less demanding on your computer like

I only made isometric rooms for the longest time cuz that's all my computer could handle I wanted to make super high detailed photo realistic scenes but I just couldn't cuz my laptop just couldn't handle it so I made what I could and got better at blender that way and eventually my skills grew and I made some money and upgraded my laptop and then I made the shot films with simple scenes and close-up shots cuz that's all my new computer could handle I still wanted to make super high quality Hollywood level VFX but even if I

wanted to or had the skill for it I couldn't cuz my computer just didn't have that kind of performance bandwidth so in short all I'm trying to say is pull back your vision a little bit sometimes make simpler things if you can at first get good at that and level up gradually Simplicity is the ultimate form of sophistication I bet you've heard that before so dial it back don't be a dummy don't let your potato laptop tell you what to do instead you adapt and tell it what to do you be the alpha in this

relationship yeah but anyway if these tips mean nothing to you you don't want to pull back and just want to render this awesome thing you made with no cutbacks whatsoever but you just can't render it cuz blender keeps showing this GPU out of memory error again and again all you can do now is switch to the CPU mode from the GPU compute mode this will most probably get rid of that GPU out of memory error but the random times will just increase like crazy cuz as mentioned before you have now switched to the turtle from

the rabbit so get ready for that slow and steady pace so while that render is running in the background for an eternity I will move on and state some more obvious facts facts like of course you can't have thousands of tabs open in Chrome when you're about to render a heavy seene and of course you should never be in the rendered View mode or the material view note in the viewport while you're starting a render in the foreground that too can clog up important GPU and CPU resource that make or break a rendering situation sometimes

so be in the solid View mode or even better in The wireframe View mode whenever you're rendering something actually there are methods where you can render a scene by using command line prompt so blender doesn't even have to be open while rendering it might sound absurd but again when it's a heavy scene and all you have to work with this 4GB of vram these little things can add up and help out a lot sometimes so I link how to do this command line thing in the description below so you can check that out actually you

can directly use the flamco tool that is made by the official blender Studio team it's a render manager tool basically that's completely free by the way but that same tool allows you to do this command line thing intrinsically where you can queue up renders and they will render without ever you having to even open blender up I link a guide to that in the description too you can check that out as well and even the command line thing out whatever floats your Bo but yeah getting back to the obvious points you of course have to

do the basic housekeeping stuff that keeps a computer generally healthy like cleaning your cash and uninstalling unnecessary heavy apps or disabling startup apps that you never use and staying away from fishy malware infected sites stuff like that that will hinder the performance of anything you do on the computer also other basic things like you should always be in the performance mode of your computer when rendering things same with your GPU you got to be in the performance mode and not in the quality mode or somewhere in between if you want quicker results and yeah it's

not just about software level optimizations all the time if you want effective performance from your computer month after month and year after year you got to take care of it from the outside as well you have no idea how much cleaning the fans of your gep puu and CPU can enhance the performance of your computer actually I always have a temperature widget switched on on my computer taskbar that measures the GPU and CPU temperature all the time cuz every few months I see it Rising little by little and that's when I open up my CPU

case of the back side of my laptop and just get rid of all the dust and filth there and that alone sometimes improves the performance by 30 or 40% no kidding so keep everything clean inside and outside and yeah also be prepared to keep your computer on for long long hours if you want to do this CGI VFX 3D thing you're going to have to torture your device a little bit 3D renders take a lot of time usually more than 12 hours at the stretch so if you are too sensitive about your little computer being

overworked maybe you should find another hobby cuz this is Hardcore stuff you got to keep that thing on forever and ever and ever if you want to get anything done so be ready to have a barue every time you start to render a project basically and you know what break your renders into pieces if you think they're taking way too long that's what I do I render the first 50 frames the first night and the next 50 frames the other and then the next 50 the other until I am done this little deer render that

you see here took 7 minutes per frame to render on my older laptop I had it running for 2 days straight until it was finished rendering so yeah you might burn your laptop along the way but hey you got the render done finally cheers I think now would be the perfect time to move on to the next section which is laptop and computer recommendations and no I'm not going to give you exact recommendations I'm not going to tell you buy this laptop or this GPU specifically I'll instead tell you what you should be looking for

when buying a computer from a 3D artist perspective so you should first of all try and get an Nvidia RTX GPU if you can I know AMD gpus are great and I know apple and MacBooks are great but the truth of the matter is NVIDIA and windows and blender just go well together and Nvidia is at the Forefront of all these new Ai and D noising technologies that it would be kind of stupid to ignore them now this might change in the future but for now if you want the least friction in your workstation you

got to go with Nvidia and if you can't afford it go for an RTX card doesn't matter which one get the the cheapest most affordable RTX card but go for an RTX card otherwise all these advancements I'm talking about will never come to your graphic card if you choose an old GTX based Nvidia graphic card the GTX cards are not bad especially for beginners I think you can actually look at my channel and you'll see what kind of things you can make with them but what I would suggest is spend a little Xtra if you

can and get an RTX card at the least the second thing to focus on from there on would be the vram ram really doesn't matter here in the 3D World it matters but not as much as vram does so get as much vam as you can afford in your GPU 4GB is fine for beginners and early intermediate users 6 GB is great 8 GB is phenomenal and anything above that is just a blessing so yeah focus on vram cuz Ram is first of all cheap and also upgradeable get 8 GB Ram if you want and

you should be fine if it gets laggy in a year or two upgrade it to 60 and you'll be fine again it is not as important as vram just remember that and for processors get Intel get AMD it doesn't matter just decide which GPU you want and then Google which processor goes well with that GPU and you'll get your answers right away and finally don't get an HDD not in 2024 just don't get an SSD for the love of God you have no idea how much faster an SSD is just I don't care get an

SSD it's a huge upgrade for a fraction of the price to just get add an SSD no excuses and yeah if you want more insights into which GPU and which CPU performs the best with blender check out the blender benchmarks website directly that will answer all of your question in just a minute or two so do all your research and check the blender Benchmark website at the end and that decision making should become much much easier and let's now finally talk a little bit about optimization add-ons and I only got three suggestions for you I've

got simplify plus I've got M saver and I've got the two optimize add-on all three tools are great all three similar things like basically they help you identify which object or which texture or which modifier is causing a performance hit in your scene they're really really helpful but all three of them are paid add-ons and I know you hate paid add-ons cuz you are a cheap skate just like me but good things come at a cost so you choose you want a $30 add-on right now or you want to wait for like five or six

years and save up $1,000 and buy a laptop or a computer then it's all up to you same goes with render Farms it will cost you again upwards of $25 for every scene but again do you want to spend this $25 now or just wait for a few years before you can save up enough money to buy your new laptop or computer later on in future it's all up to you and your circumstances I'm not telling you what to do actually there are other free render Farm Alternatives out there too like Google collab and sheeper

render Farm but in my observation they're never as reliable as the paid options but definitely worth checking out if you're not stuck in a client project and only need help with some personal projects and I know it sucks to have to spend money need to get such facilities but hey again good things come at a price not everything awesome can be free like blender so I'll link all of these add-ons in the description below you can check them out there and while we are on the topic of add-ons you should disable the add-ons you don't

use they won't really affect rendering speeds per se at best they might just improve startup speeds when you first open up blender but honestly you never know when an add-on receives a weird little update and it screws up everything in the background and you won't even know what's going on and causing the chaos because it's all happening in the background it has happened to me in the past either the add-on gets updated or blender gets updated does making the add-on incompatible for that version and that can cause a host of performance issues if the add-on

isn't welld developed so the general advice I would give is only enable the add-ons you use most often the other ones you use them where you need them and then just disable them that's it and yeah I think that's it that's all the tips and tricks I had for you in this video but now finally in conclusion I am telling you if I see a single comment in the comment section where you're crying about your shitty computer I am going to flip out oh oh everybody has such great computers I have such a shitty computer

oh even The Flintstones had a better computer than me oh oh my life sucks I'm so unlucky and so poor and all these other shut the up shut the [ __ ] up yes I know you have a shitty computer I know it sucks but what are you going to do you're not going to win a lottery tomorrow and get a new computer right away if you care about this little passion you're exploring right now you got to do what you can with the things that you got but but don't no you don't get it

you say that because you have always had a great computer I have the worst computer ever in the history of mankind my computer doesn't even have GP so why did you get into this hobby if you didn't have have a GPU go find a new hobby and get back to it when you can afford a GPU what is all this crying going to achieve anyway nothing it sucks I know but again all you can do is the best with what you have there are so many people with so much worse computers are so much better

than you so the chances are it was never your computer or your GPU or your circumstances it was just you you were the problem not your computer not your skill set you look look at this black screen look look at your reflection in it you see yourself you you with the problem always so buck up shut up and get to work don't compare yourself and your circumstance to others cuz comparison kills creativity so just shut up and get to work oh but you shut the up