/agdg/ - Amateur Game Development General

Just Like Make Game

(You probably don't need to) SAVE THIS FILE (any more): Anon.cafe Fallback File v1.1 (updated 2021-12-13)

Anon.cafe will shut down as of 00:00 UTC on 15 March 2024. Announcement here.

Max message length: 20000

Drag files to upload or
click here to select them

Maximum 5 files / Maximum size: 20.00 MB

Board Rules

(used to delete files and postings)

Open file (466.59 KB 1920x1081 ClipboardImage.png)
Open file (607.59 KB 1000x1000 well.png)
Open file (6.08 MB 2000x2000 spess111.png)
Open file (3.04 MB 1000x2000 11building.png)
Blender and CGI tools Thread yesdev 05/18/2023 (Thu) 15:59:01 No.642
There are few layers to learning Blender, but before learning, the Main Principle is to do as little as possible to get best possible result, by using tools which blender provides. You dont draw textures on everything by hand, you use procedural textures. You dont make rigs for generic humanoids(and some animals), you use rigging addon. Also, I would say that 12+16 gb ram is required for comfortable usage of blender. You can live with 4 gb, sure, but it will not be comfortable at all, and you might never be able to use sculpting(or using displacement in textures) or make proper renders. Also, nvidia cards work better, and if you have older radeon card, its not supported by newer blender, and 2.93 is the last blender version you can use. First one, is learning how to do anything, learning interface, hotkeys, etc. Most of it is very simple, and the more you use it, the faster you will do everything. At this point you should just watch a bunch of videos on youtube, I can recommend a few channels, which mention every single button press they do. And its pretty much the only way to learn it. I would say, you need to know how to do simple modelling, adding random primitives, installing generic must-have addons, such as node wrangler, basic understanding how to render something, and basic understanding of shading, aka materials in blender, how to use hdri and basic unwrapping. Additionally, for simple modelling you need to understand why you should use quad topology. At this point after watching videos, you should be able to make a simple house, or a chair, or anything similar, and make materials for it, place a camera. You dont need to understand what you are doing, just copying what you seed others do. You probably should watch a video or two on how to optimize rendering, to save your time, you dont need 256+ samples for test render, 32 will do just fine. I cant help you at this stage, because everything is just learning which buttons to press. Next is understanding how to do more advanced stuff, like using modifiers for objects, using advanced materials, or even geometry nodes. At this point you should start to understand what you are doing. You should probably start working on a stuff you want to make, however consider it practice, not something you will end up using. I think, you should understand how to make something what you want, instead of just copying some video. You should know what modelling terms mean, like subdivide, rotate, extrude, scale, cut, add object, install the "must have" addons (they ship with blender anyway). And for materials you should understand(just play around with it) what different coordinate systems do (object, generated(aka global), uv) what textures do voronoy, perlin/noise, waves, and what bump, roughness, and displacement means. I am probably forgetting something, but all of it will be adjacent anyway. At this point you should be able to make something like a snake, with proper scales, out of curves or modelled in a couple of minutes. Or maybe use an addon to add a cat rig, model cat around it, and cover it with hair, with procedural shading. (Or naked cat, if your pc cant handle fur). And maybe even animate it. You should use core principle of "do less" and use addon to get armature with premade animation, use automatic weights and make whole animation in just a minute or two. At this point you should notice parts which your pc cant handle. Mine for example cant render volumes anymore, due to "fuck radeon cards, their drivers suck", and some other stuff. There are often ways to sidestep it, but sometimes, if you dont have enough ram, for example, there is pretty much nothing you can do to sidestep it. I would say you should be able to at least render a model with 300k vertexes, a couple of materials with varied roughness, metallic parts, bump map, hdri + a couple of lamps. I would say it is the bare minimum of using blender for gamedev. You might consider translucent/transparent/glass materials, but honestly they are not important. Requirements are lower for eevee rendering engine, and it is faster, but you likely will need cycles. I would say you should be able to make "test" renders in a minute, with low sample rate, otherwise everything will take too much time. Anyway, at this point you should probably think about making something cool via tools you are provided. Probably something based on procedural textures. For example picrelated is a model for a well, and procedural texture for it, it might look complex at first glance, but in reality its quite simple, and only uses a couple of procedural textures and some math. And model is just a cylinder. And lamp uses same model as a bucket, just with a couple of modifiers. Same with orange galaxy-like splash. Its just some camera tricks, and a couple of procedural textures mixed. Doing something like this is really not necessary for gamedev, but it is fun and educational. At this point you should start thinking about making game-ready models and exporting them to your engine. Be it 2d sprites (with that I can help a lot) or 3d models with their textures (with that I can help a little). And you should look through cc0 websites with textures, models, etc, like https://polyhaven.com/ ). For example you can spend a day trying to model a tree, or you can use an addon to generate a tree in a minute. Cont...
Open file (2.45 MB 1920x1080 tree with shadow.png)
Open file (6.37 MB 1000x1000 flamewall2.gif)
Open file (766.53 KB 1000x500 paved ground orangish3.png)
If anyone is interested in youtube channels, I can recommend some of them. For general basic modelling, lowpoly modelling, general cgi/artistic side, general blender guides and quite advanced stuff like geometry nodes+ procedural materials. More about basic principles and some tricks. I will repeat "do less, and make blender do everything for you". Blender is old so almost every problem was solved before you, so looking up how to do something will likely result in someone doing the work for you. Like with tree generation addon. You can model a tree, make textures, etc. Or you can get free tree model from some library. The only point of making your own tree is training, if you actually need a tree, get a premade/generated one. Next is, dont worry about small details, which no one ever will notice. You can find a free texture for a tree leaf, apply translucency, add subsurface scattering, and make most realistic tree leaves ever. But each leaf will be 2x2 pixels, so no one ever will notice its details. So dont bother trying to add details for something so small, it will be invisible anyway. In picrelated tree leaves are just perlin noise multiplied by "layer weight-fresnel" to get leaves of different colors, clustered like its intentional. Just a couple of nodes and colors. For example, I tried to make "proper" asphalt texture, and it was fucking waste of time. In general, you dont want to overload anything with details. Its very important, dont render to mp4/webm or any other video format, unless you use eevee and rendering takes less than a couple of minutes, and you dont care about quality. Output gets really fucking compressed, if anything stops rendering you will have to start from beginning again. So just render into a bunch of png and stich them later. While using procedural textures is slower, than prebaking everything, you should consider, how long it will take you to bake a texture vs how much rendering time it will save. Personally I only prebake AO, and only because my fucking radeon card cant render it normally. Baking textures in blender is difficult, in general. I know how to do it, but it is not ideal. For start, I dont think even latest versions of blender support hdri for baking, and you need to use lamps instead. If you are making something like lowpoly models for a game, with simple textures, without bump maps, its perfectly fine. But if you want to bake normal map into lowpoly mesh, from highpoly sculpt + prebake diffuse color, it might be very difficult, if not impossible without excessive trial. Personally I tried it a few times, and it seems to be very slow and very annoying process. Pics related is the stuff I consider myself t be good at, so if you have any questions about it, or in general, feel free to ask.
>>644 >If anyone is interested in youtube channels, I can recommend some of them. Please do, along with any other educational resources you think are useful.
Open file (2.08 MB 1920x1080 censor.png)
>>645 In general, some guides might be old, but still relevant. Dont worry if video is 10 years old, if interface looks the same as modern blender, likely nothing changed. Also, some of it is "industry standard", so its applies to a lot of other 3d software. Also a lot of them plug their commercials "here is my website where you can download all the textures and models I use", dont worry about it, man gotta eat. This guy makes guide series about blender, from the beginning. Kind of default option to start learning. He also talks about art in general, like "rules of art", "rules of animation". https://www.youtube.com/@blenderguru This guy makes lowpoly models in just a few minutes. https://www.youtube.com/@Imphenzia/videos This guy makes guides about modelling, while some of them are old, he does mention every button press, and how to do every single thing, so its a good starting point. There are a few channels similar to this, just a guy narrating every button press and what they do. https://www.youtube.com/@AlimayoArango This guy makes advanced advanced tutorials, about motion tracking, geometry nodes, shading, etc. If you want to learn how to make cool procedural materials, or procedural models, this is very good channel. Other than the very basic stuff, I mostly learned from him. https://www.youtube.com/@DefaultCube Random channels I watched, some of them are the same channel, split into a few, some of them are just professionals showing off. Worth to look at. https://www.youtube.com/@cgboost/videos https://www.youtube.com/@DECODEDVFX/videos https://www.youtube.com/@KevBinge/videos https://www.youtube.com/@cg_cookie https://www.youtube.com/@IanHubert2/videos https://www.youtube.com/@Iridesium/videos https://www.youtube.com/@TheDucky3D A shitload of cc0 models. Almost 3k scans of historically important objects. https://sketchfab.com/nebulousflynn/collections/cc0-9e9b8c5442ab4b59ba16b6fa5e43b8da Random cc0 stuff. HDRI, models, textures. https://polyhaven.com/ https://ambientcg.com/ Useful tool to pick colors for your stuff. https://paletton.com/ Also, to add to "general rules", dont use 100% saturated and 100% bright colors. They are rarely look good on a model. Like 255,0,0 red color. A lot of cheap looking models use it, and it looks bad. Also, what color you see in editor, and what color you will get in render, are often very different.
>>646 PS. Stuff about geometry nodes becomes outdated the moment you watch it. They change them a lot, since its basically experimental feature. Its more stable now, but most videos are probably outdated.
>>646 That's a handy list, thanks anon.
Open file (440.52 KB 1920x1047 dust1.png)
Open file (1.11 MB 1920x1049 dust2.png)
Open file (271.20 KB 1920x1046 dust3.png)
Anyone ever try modeling with Dust3D? I just got it and started playing around with it today. It looks like a nice little tool to knock out low-poly models in a hurry. You model by placing and resizing circles in the front and side views, which control the underlying model. You can apply different modifiers to smooth or change the profile of the otherwise cubic model, mirror modifier, paint vertex colors, etc. Just have to get some reference images whipped up in GIMP or whatever. Nice if you need some low-poly props for a background or a pre-render or something, or want to export the model to blender for further refinement, animation, sculpting, whatever. Has native windows and linux builds. Some caveats, however. For some reason, it seems like versions 1.0.0-rc.7 and 1.0.0-rc.8 (the latest fucking ones) are weirdly broken; they don't seem to have any of the advanced features you see in tutorials and such, and frankly, are unusable. Luckily, though, I was able to get the next older version on sourceforge: ht tps://sourceforge.net/projects/dust3d.mirror/files/1.0.0-rc.6/ that is feature-complete and usable. Has example projects you can open up and look at if you want to see how shit's done. Also, tutorials and documentation is slim. I was able to find these two: ht tps://yewtu.be/watch?v=MytN8t4guuM ht tps://styly.cc/tips/dust3d-modeling/ Give em a look. I'll try to see if I can't model something in it this week if I get the time.
>>786 You can do the same with blender + curves or skin modifier. That picture with bike looks atrocious, its like a hundred of points, way more than you need for a fucking curcle. Check this video, it shows way better way of doing it specifically for a bike. https://youtu.be/G9BlyiMVefU Here is fast modelling from reference. https://youtu.be/lpIonmH90-k However, there is often a fester way, of using built in into blender addons. Cat, panther, horse, human are all built in into blender rigify addon. And I think new blender has addons with direct access to free libraries, including library of cc0 models. If you want to get model for something fast and easy, you can just find free model, if you want to make something yourself, there are fast ways to do it in blender.
>>788 Yeah, it's ass. Nothing you can't do with hap-hazard loop cuts and face extrusions on boxes in Blender. Can also get proper cylinders/torii and shit if you were trying to do something like that bike or another vehicle.
Open file (851.32 KB 1355x1015 ClipboardImage.png)
Simple setup for pixelized image, if anyone needs it. The lower "value" on the left is, the heavier pixelization becomes. Its just multiplication+ rounding+ dividing each directional vector.
Open file (932.58 KB 128x128 ezgif-2-269630b1da.gif)
Open file (649.35 KB 470x843 a.png)
I try to post here while we have that backupgate over there. So I checked out this tutorial: https://yewtu.be/watch?v=0TzjpR3pdpk One thing this guy does is that he selects a random face, Shift-D, RMB, P to make a duplicate into a separate object and work from there. But this way he ends up with a bunch of (partly) duplicate faces, and he only deletes a few of them. Isn't that a bad idea? (Also the first time I made the building it was too low, normally I'd just go to edit mode, Alt-Z, box select the upper part, G Z and make it taller, but since this model was composed of 8 or so objects I couldn't do that (I don't think I can be in edit mode for more than one object at a time), so in the end I just scaled the whole shit along the z axis.) Also, in the meantime I modelled a door. Baby steps. And I've managed to produce the worst looking procedural wood texture, I'll try to do something about that tomorrow. But my real question is, I want that door to look old and not exactly in a good shape. It should have paint, but that came off at various places (that's why I need the wood texture) (something like this, but with wood instead of metal, and probably without texture painting: https://yewtu.be/watch?v=bR4HtqxA9tk). I'll play around with my materials, but I think I should also need to add some deformation to the mesh itself, right? It looks too regular now, tree can expand or shrink as it gets moisture, etc. Or would it be enough to just add some random value to the normal's height input? And I'd need multiple instances of this door in a scene, but it would be better if they weren't exactly the same. Is there some easy way to do this, other than duplicating the materials and giving each door exactly the same setup but with a different seed value? (Also killing object linking in the process)
>>1001 >One thing this guy does is that he selects a random face, Shift-D, RMB, P to make a duplicate into a separate object and work from there. But this way he ends up with a bunch of (partly) duplicate faces, and he only deletes a few of them. Isn't that a bad idea? It just how he does things, I suppose. Its possible he just extrudes them afterwards, so its not duplicate faces, but multiple fully complete objects. And adding them together is quite easy. Its also possible that he does it because its fast for demonstrational purposes. >(Also the first time I made the building it was too low, normally I'd just go to edit mode, Alt-Z, box select the upper part, G Z and make it taller, but since this model was composed of 8 or so objects I couldn't do that (I don't think I can be in edit mode for more than one object at a time), so in the end I just scaled the whole shit along the z axis.) You can edit multiple objects at the same time, just select all needed objects and move them. You can also do parenting, it all depends on what feels easier/faster to do. >painting texture I would just use noise texture or noise + geometry>pointiness / AO texture as a mask. The problem with your wood material is values of various modifiers of texture. Most obvious is bump node, you need to lower its value. And it needs ramp node to "clamp" values, so they are not in 0-1 range, but something like 0-0.5 range, so top surface looks smoother. And play with roughness a bit, you might need to switch to "rendered" viewport so you can see what you doing, and on radeon cards it might crash. Also I would make it a bit darker, since darker things looks less shitty and more fancy. And dont forget to use hdri instead of lamp light. >defomation to the mesh Personally I just use very low scaling deformation modifier with random noise texture. The point is to make it imperfect, and it does well. You will need to add more geometry via subdivision modifier, and sometimes "perfect door" is fine, because who gives a shit, its a door.

Report/Delete/Moderation Forms

no cookies?