Відео

There is a trade-off to be considered. Super Bump is only for Eevee. It will add some extra geometry and uses transparency but it will give you the best results and cast shadows. POMegranate is ideally used on flat surfaces and does not cast shadows but doesn't depend on transparency and works in Eevee and Cycles.

Hi there and thank you for picking up bFur. Please contact me at the email address on your Gumroad receipt so I can help you directly. Thanks again.

Thanks Louis! Good to hear. 😊

You're welcome. Enjoy the series.

Thank you very much!

Thanks P. I appreciate it.

It does indeed. You only need to turn on Transparent Shadows in the Material's settings. I'll be updating the addon to correctly prepare materials for 4.2 by tomorrow.

Hi there. Thank you. I'm not sure what's going wrong. Could the displacement be too strong?

Exactly, this is shell texturing. You can see the layers if you zoom in close to the model but they can be hidden either by simply adding more so they are more tightly packed, or with the "spread" control which biases the concentration of layers towards either the top or bottom of the shell. With dense fur you usually can't see the roots of the hairs so you can bias the layers towards the top to get a fuller look with fewer layers. Have a look at the tip of Finnick's tail at 00:27 and you can see the layered effect.

@@nodesandnoodles Ohh!! You're right! I watched the video twice but I hadn't noticed the tail thing, I think because I got distracted by the ears or the movement camouflaged it enough, or because I was viewing the video in thumbnail form instead of full screen, or all three XD

Thank you, and thanks for watching.

Hi Michal. Super Bump shouldn't have much of an impact on the CPU. Are you using Eevee, and are you rendering with the GPU?

@@nodesandnoodles I adding 2k rock texture with 65 layers, it's very lagy. I use 4.2 and GPU [14 cores] / metal ... I do not have any lags when I use normal maps with subdivision / displacement and bump, better results and without any lags.

I'm not familiar with the M1 Pro but I see online that its GPU is comparable to a GTX 1650. I have tested Super Bump with a GTX 1660 and get good results. Perhaps the M1's GPU doesn't handle transparency very well but I have no way of testing that here.

@@nodesandnoodles That's why I just add a comment for M1 PRO users, I see on video that this works super, but is little non sense spend $ for this who got M1 Pro like me. :)

I'll put out a message to Super Bump customers to see if other Mac users have had similar issues and if I find a solution, I'll let you know, and if I don't, I'll add a message to the product page to inform potential customers. Sorry it didn't work out but thanks for letting me know.

Hi there and thanks for picking up Super Bump. Drop me an email at the address on your Gumroad receipt with a screenshot of your Blender and the version you're currently running and I can help you out directly.

Hi there. Have a look at this tutorial by CG Geek on using Google Maps data to create 3D models in Blender: ua-cam.com/video/Mj7Z1P2hUWk/v-deo.htmlsi=sElj9U_cXlJa6lG5

Hi Florian. Nothing perfect, I'm afraid. Those artefacts are inherent to the technique of displacing flat geometry. The closest thing to a solution is to add more subdivision until the stretched triangles can't be seen any more.

@@nodesandnoodles okay ! Thank you , Aldo wondering , is there any downfall to using adaptative subdivision on this type of mesh ?

@@FLORIANSPITERI-g3n nothing other than memory consumption and render times increasing a little. It should help a lot with the artefacts.

@@nodesandnoodles actually I did the whole tuto with it , could n t make it working without . And there is still a lot. Maybe changing the scale of the plan ?

The scale of the plane should only affect the height of the displacement. I usually use a plane subdivided by 10 cuts in Edit mode and a Subdivision Modifier with 4 levels for building the materials and then I turn on adaptive for the final render or just to see more detail.

The POM node needs a height texture to work, so you could bake any procedural height to an image texture and use that. It works like, for example, a UV Map node. It's a texture coordinates node. You can use it for procedural materials but it is best used with image texture arrangements.

@@nodesandnoodles ok good serr !

It depends how you want to mix the textures. The POMegranate node doesn't do any mixing but you can have more than one POM node in a material so you could have one for each texture and then mix the textures with a Color Mix node. If you want to mix the Height textures, you'd have to create a mixed version of the height maps beforehand and then use that as the Height map for a POM node.

@@nodesandnoodles Thanks for the fast reply back..

I have no special addons, this is just vanilla Blender. I use a plane sized 1x1 to match the sizes of the UV map whereas Blender's default Plane is sized 2x2. Scale your plane by 0.5 either in Edit mode or in Object mode but remember to Apply the scale if you use Object mode. This will be the reason for which your displacement height is half that of the plane in the video. I'm not sure what could be causing the jagged blocky problem. For plane displacement, I recommend subdividing the plane in Edit mode with 10 cuts, and then add a Sub Div modifier with 4 levels. Make sure your plane is set to Smooth shading and it should look exactly like mine. Let me know if this works out for you.

@@nodesandnoodles scaling it down (on x and y only) was able to fix the height.👍 but the jagged edges remain still. i have the same number of loop cuts as you use in the video. so i really have no idea why its doing this 🤔 honestly its been this way for every tutorial ive ever followed using displacements. so im wondering if its a preference somewhere that i changed ages ago that is messing it up lol.

Cool. Glad to hear the scaling worked. Do you perhaps have Simplify enabled under the Render tab of the Properties panel? This would globally limit the number of levels for all Subdivision modifiers. Also, you should ignore the loop cuts I use in this video when using a square plane. I made those subdivisions to suit a scaled plane for displaying a 1920*1080 video. Your geometry should be squares as much as possible.

@@nodesandnoodles unfortunately no, simplified is turned off. Although its good to know that option exists 😅

Could you show me a screenshot of the bad displacement? Are you on Twitter/X?

Hi Jon. I'm afraid I can't offer product support here. Please drop me a line at the address on your Gumroad receipt and I'll explain the deal with the layer limit and how it could be changed. Thanks.

@@nodesandnoodles My bad - great update!

I'm getting the files ready to post right now. Won't be long.

It is indeed! I create all my add-ons in 3.6 and then adapt them for 4 and above.

​@@nodesandnoodles nice one

Hi Julia. Blender's built-in exporters can't handle procedural materials so POMegranate can't be exported. Unreal and Unity have their own POM nodes so you could simply use the same height map and not need to export anything.

It does indeed. It works in both Cycles and Eevee but is best in Eevee. Cycles is limited in texture reads.

@@nodesandnoodles I am also wondering where did you get the crystal material, because I would love to use it in my latest project.

I got the crystal PBR set from Textures.com www.textures.com/download/PBR0579/138828 Unfortunately, it's not available for free so you'll need a subscription to get it.

@@nodesandnoodles i wish i could get it so bad...

Hi there and thank you for picking up the nodes! You need to import the nodes to your Blender project to use them in the shader editor. Follow the steps at the top of the documentation page: blendermarket.com/products/uv-grid-materials-pack/docs

You could export the shell mesh, bake the height map and export that as a texture, and use those in Unreal but this would require custom nodes like the ones I made for my Super Bump tool. In fact, bFur uses the same tech as Super Bump so I could port the nodes. Good idea! I will include this in the next update to bFur.

@@nodesandnoodles Yesss, I want to use this in Unreal Too

I'm afraid not. None of the exporters bundled with Blender can export procedural materials. You could arrange the sizes and offset so that you export a seamless tiling texture and use that with your random uv approach.

The shortcuts I use appear on screen in the bottom right as icons and text.

No, Super Bump is for Eevee as a replacement for Cycles's material displacement. If you're working exclusively with Cycles, you should just use material displacement.

Thank you! Glad you like it. 😄

Thanks Jim! I hope you enjoy the rest of the channel. Do you already have PBR Layers? If not, you'll find it on my Gumroad page. Thanks again for watching.

bFur uses "shell texturing" which involves creating many stacked layers and using transparency to trim out everything below any given layer. This works very well in Eevee but in Cycles requires a very high number of Transparent bounces (possibly hundreds) which causes render time to skyrocket and works the processor VERY hard.

Ok, here's a list of everything I can think of that must be correct for displacement to work; 1. You must use Cycles. 2. The material's Surface - Displacement setting must be Displacement Only or Displacement and Bump. 3. The plane must be subdivided a lot. There must be enough vertices to represent the detail of your height map. 4. Your height map must be connected to the Height input of a Displacement node (not a Vector Displacement node) 5. The Displacement node's Scale input must not be 0. Ideally it will be 1. (I also change the Mid Level from 0.5 to 0) 6. The Displacement node's output must be connected to the Displacement input of the Material Output node. Check that all of those are correct for your setup.

Did you get it to work in the end?

@@nodesandnoodles I appreciate the trouble your going to through, but I'll have to try tomorrow when I have some free time. As someone who has no experience with blender other than a donut and these videos my guess is that I either fucked up following the instructions, incorrect blender settings, or I'm working at a scale that makes the effects so small I don't notice them. I'll go through your list of possible reasons tomorrow

@@nodesandnoodles Ok it seems to like its an issue with both scale and subdivision I had to bump up the subdivision by 2 and I had to play with the values cause the scale im working at is much smaller (mm). So the values you used weren't working because they're too large for me. My bad for bothering you with such a simple issue lol. Nonetheless, I appreciate the help you provided. I'll be heading to the chainmail tutorial next and hopefully that works perfectly and i can implement it into my ring!

Glad you got it sorted.

Hi there. It should work on a cylinder like it does for a plane. Is your cylinder UV unwrapped?

@@nodesandnoodles Yeah, I followed blender guru's guide on unwrapping an object. Adding a single crease line across the cylinder and unwrapped it. Unfortunately, it doesn't work

Have you tried the result of this tutorial on a plane to see if that works? I tested this node setup on a cylinder and it worked fine. Check if it works on a flat plane and if it doesn't, there must be an error somewhere in your network. What exactly isn't working? You say the height map isn't showing up. Do you mean the bump effect isn't working, or the height map outputs black?

@@nodesandnoodles Just applied everything from tutorial 5 to a plane and there's no bump effect. I'm seeing an output of my picture on both shapes (plane and cylinder) however, they're not popping out of the material like yours. Like in tutorial 3 and 4 you had spheres and then bricks sticking out of the object. Like inflated. I'll go back to the beginning and see if I missed a step I appreciate the trouble you're going through to answer my issues!

Ah! I get it now. To see the "inflation", you need to use Displacement, not just Bump. Have a look here: ua-cam.com/video/XnnP19bhn4A/v-deo.html

Great! Thank you for picking it up! Enjoy and happy blending!

@nodesandnoodles thanks, which version of Blender is preferable to use ?

@MENDA4X Super Bump will work for any version of Blender from 3.0 onward. Personally, I prefer 3.6.

@@nodesandnoodles Thanks, when I want to add the texture it does not allow me because I do not get the option of the folder icon, you have to add something else to the configuration ?

@@MENDA4X could you please email me a screenshot of your blender at the address on your Gumroad receipt?

Super Bump is designed to give a high-poly appearance to low-poly objects. I have never tried it with a 2 million face mesh but I would not expect it to work well. Since the mesh is so high-poly, I would render in Cycles and use material displacement. With Super Bump, I find that the most important factor for viewport FPS is how much of the screen is occupied by Super Bump objects, as well as how many Super Bump layers the objects have. IMPORTANT: Super Bump works by duplicating the mesh several times and expanding these duplicates outward. This means that if you use Super Bump on a mesh with 2 million faces, that's 2 million more faces for every layer and it's not uncommon to use 30 - 60 layers. When you say "too many nodes", I must assume you are referring to a procedural material. Procedural materials will almost always have more nodes than a Bitmap based material which uses only textures. The Procedural/Bitmap trade-off is this; Bitmap uses more memory but less processor. Procedural uses less memory but more processor. I wouldn't expect any procedural material to run "smoothly" on a model with 2 million faces, though "smoothly" is relative. In terms of viewport FPS, it's not useful to compare Eevee to Cycles because Eevee will try to draw the complete scene at high quality before moving on to the next frame whereas Cycles can move on after just 1 pass so, yes, FPS will be higher but the image will be unrefined and unusable.