:)

@@tyler_puryear Absolutely amazing, I'm a complete noob and this helped me so much!

Hey, really glad it helped!

@@tyler_puryear Question: How do you turn a high poly object and into a low poly duplicate of it. And for the materials, do I give every separate object a separate material or do I have every object combined together and give them different materials?

what appears clear is that it's quite 4 operations which could be done in one package as it's just repetitivfe as helle , and in human scale, this tuto applied to a building will become a trash of 3x the objects and 4x the operations: hey ! just tiring the hell of a process which could certainly be compressed in one : 1 chose the high poly (part of a complete bigger model) 2- chose the textures (in magazine and example of textures/matters): point on the image your needs 3- bake .. it's finished !! = low created for far viewing, but hidden the cage - - i'll wait till this process of simplifying the operations (and even have it easy to interven for few modification), but no way to use it to get my "houses" painted part by part as an old painting ! - simplify it please ! 12 operations are to be one package (and sure it's possible).

Plenty more where that came from!

Of course! Had to show how someone can do this for free!

@@SVKU7 Thus is the trade off of what Blender currently offers, and we wanted to show how to do it without the need of "adding" add-ons. I know there are some out there.

Hopefully this was in-depth enough to help!

:)

:) Agreed!

@@tyler_puryear you made it easy to follow and this was not a simple topic. thats an art as well in my opinion. cheers!

Me too, after that I think I can switch from substance painter to mixer ;)

@Bertram Ocasio bot

@Tanner Musa another bot

Is this feature coming?

@@antronero5970 seems not the case. the software is being ignored too. you can look into another texturing software

:)

Bro 20 minutes for at most a 5 minute job in substance

And the price, the PRICE and also Adobe onwns it

I know this is old, but, apart from baking time, that heavily relies on your GPU power, Blender is "fine" for baking. It's better if you have an addon to bake, but apart from that, you can still do it fast if you use those addons. Yes, it's not like painter, but it's free...

There’s probably loads of C4D tutorials out there, if not, check some forums, they’re always helpful

this is so much more powerful than C4D bake Object tag (it uses CUDA) but at least in C4D you bake all maps with one click

Thank you!

Tyler Puryear Literally every video makes me a stronger game dev i hope they never stop

If you don't have normal map you don't have to import it. It should work.

The normal map captures the geometric differences between two models and imprints that into an image, so doing it without a low-poly model won't show any difference. The normal map doesn't matter if you don't do hi/low-poly meshes. I'm also just baking using a single mesh (For nanite) without using a normal map. I only experienced problems with noisy/grainy curvature bakes, but I think that's possibly my own bad setup, idk yet though. The video to me also seems to imply that the .fbx imports the textures in some way, which I don't think is possible. I just save them instead and load them into the project using the "Setup" tab.

@@frostydelusions3066 Wow, thats a massive mistake and will cost them. They could legit work their way and compete to become the industry standard with a bake feature. Theyre holding themselves back. This statement alone has ensured I will stick with Substance over Mixer.

I successfully backed normals with Substance painter on the first try, so after watching a third of this video, I’m like « nope ».

Soul crushing plus vote.

Yes you can, if you use them with Unreal Engine it's totally free until you get 1 million dollars, after that you pay 5% to Epic. With other engines/softwares you have to buy the assest you want and then you can use them commercially.

if you export assets to work on, you will need to reimport them, theres two options I know of 1/ if you change the asset a lot do a totally new import 2/ if the model in more or less the same right click the asset in UE4 and select reimport, it will either pull the asset updates straight in OR, pop a dialog box to browse to the asset to import, it often pops a dialog to showing the asset changes, if I remember rightly the fix option updates the asset in UE4 with your changes

To have a baker you need a render engine. Mixer is free. Great chance that if they add a render engine to it, it won't be free anymore.

@@Keilnoth True that you need a render engine, false that it won't be free anymore, plenty of apps with rendering engines are free. Also they have Epic money is not like they don't have resources.

The treads are actually one of the separate model parts by itself; it's not a duplication of any of the other parts of the stairs. There aren't any vertex groups for this particular blend file, though you could set those up for the Material IDs if you wanted OR just selected a group of mesh faces in Edit Mode and "Assign" a material to those faces from the Material Properties panel which is the way this particular blend file was set up.

Tyler Puryear yeah I started to notice that towards the curvature part of the video. It’s a little unclear how he’s baking all the maps included the all in one material ids from just selecting the Treads collection. It was explained at the uncheck clear box part of the video but I suppose many steps were skipped to shorten the length of the video. I’ve noticed in other videos most multi-part models need to get joined together before being exported to fbx. Just trying to understand the best approach for baking the high to low blender workflow. I dread to think about the reset, rinse and repeat when having to make a major change.

@@tomoprime217 Well I cover the process of the multiple parts baking down onto the same texture map in the normal map part of the video. When I was explaining the Material IDs, AO, and Curvature, the baking process itself is all the exact same, so yeah, it would have been a repetitive process. As long as you have the "clear image" checkbox "unchecked" AND all the low poly models share the same UV Layout, then you can bake them all to one texture. You just have to do each model separately to get the cleanest bake. You CAN merge all the low poly models together and do one single bake, but "depending" on your model's complexity, you can see some unsavory results. Which is why I show them all separate. When it comes to exporting the low poly FBX, you do not have to merge them all together, you can, but you don't "have" to. Just make sure the you have all the low poly's selected like I show and choose "Selected Only" when in the export window.

Tyler Puryear I find it gets especially tricky if you don’t merge the models for character fbx export. I found this free plugin handy for generating material ids though it requires joining your models as one to get different vertex colors. See “Set Connected Vertex Colors” m.kzfaq.info/get/bejne/oNiAgaabu9nYaIU.html

@@tomoprime217 Yeah, it all depends on your model. I can see why character models could be a tricky animal on their own.

Have not used the new ADOBEsubstance3d thingy, but on 21, its waaay easier. You just open a baking menu, assign the high-poly mesh and click bake. Baking menu also includes settings for various things like baking depth and whatnot. Everything is then set up correctly, and you dont need to mess around with assigning any textures. The actual baking process generally takes longer than the set-up process. Also, the baked maps are all already imported into substance, as opposed to needing to manually transfer them if you bake in blender. btw, you can still buy a permanent licence for Substance Painter 2021. Its 120$, but thats about half of what an annual subscription of Painter3D costs. I hate Adobe, but compared to doing this in Blender, its a day and night difference. 2-5 min vs 20+ min. Highly recommend just watching a tutorial for Substance and seeing for yourself.

For cycles to know which texture to bake to, you just have to make sure the "Image Texture" node you want to bake to, is "selected/highlighted" in the Shader Editor of the LOW POLY model. It's always a good idea to have this same "Image Texture" show up on the UV Editor Window, but that is just only so you can visually see the bake results. What truly matters is that you have the node in the Shader Editor selected. You do not have to worry about linking any nodes together for the bake.

Cycles bakes onto the texture (image texture) node selected in the node editor or shader editor. so the process goes like this: assuming you have 1 UVmap and not multiple.. all you have to do is add an image texture node, click new, create your texture (name and resolution) keep it selected as a node, dont select anything else.. then go to the render tab, set the bake to whatever you want to bake (diffuse, glossy, normal, emit) and then hit bake.. the texture will be baked onto the image texture that you just created because you have it selected.. it can even overwrite other textures that are already there in the shader editor so you need to be careful which image texture you have selected before hitting bake.. also if you have multiple materials in 1 object you have to do the same process of adding an image texture onto both materials, keep it selected in the shader editor and then bake once, it will bake both materials on that single texture.. sorry for the text wall but i wanted to explain in detail (:

@@arenaward8984 Thank you for the detailed answer!

@@tyler_puryear Thank you! Got it :) It's all about selected texture node. Edit: Oh, are you THE Tyler ? The narrator in the video ?) If so, you're awesome! :)

@@Kerlykchan I am indeed the one! And you're welcome! :)

In the next release!

@@teddygbg they do now :D

Marmoset's baking features are indeed superior and faster, but we wanted to showcase the free alternative as everyone doesn't want to pay for toolbag.

@@tyler_puryear 100% understand! The price tag is what brought me to blender in the first place :)

Nvm, had it set to AO!

Its probably to do with the normal map, depending on the renderer used, the normals will be flipped if the YUP isn`t correct, Blender and Unity use OpenGL which is y+ and DirectX and Unreal use Y- normal maps, You need to find out what mixer and Arnold use as the renderer api and bake accordingly, you might even need to conevrt between mixer and Arnold if they are using different api.

@@gower1973 thx bro, now i go learn blender))

bc He talked very clearly and slow

The order of selection is wrong. High to low poly. If u go low to high poly u will have a blank square

Right, once you get the workflow down pat, it's quite quick to do.

isn't it only for static meshes?

Yeah, its such a sore-spot in Blender. I hope that they will eventually take some notes for how substance is doing this and make it less painful.

Well if you bake in substance painter, it will be much faster

Many of those details could have been easily painted in Painter/Mixer. No need to model or bake. You can check information about the Alien isolation pipeline

Can someone explain why baking is so painful? I design products in CAD and I want to render them in Quixel - not for games - but for product marketing but it never works because they never bake correctly and of course then Quixel does me no good

@@JulianMerghart Quixel is NOT a render engine. Its a tool that allow you to create PBR texture by blending titble textures with baked texture from your creation giving good resemblence look between low and high poly. This tool have feature that allow you to preview the result of your imported unwrapped models with blending texture al together. Like you mentioned. This tool never worked or bake correctly for you... Question is, have you unwrap your CAD model before you could import it in Quixel? Based on my experience as product designer in past, I'd suggest you, retopologize your CAD model and unwrap it. Or use render engine procedual materials and UV planes.

You can use Substance Designer. It's pretty automatic but it has many options to tweak, it lets you bake in batch, and has very good performance. It's a lot better than Painter, even if they use the same engine, because in Painter you are very limited.