1
$\begingroup$

Blender enthusiasts!

I'm nearly done with Aidy Burrows' Game Asset Creation course and ran into weird baking behavior from Cycles while making my final textures for the game model.

Details of the mesh: all separate parts recently joined into one mesh; has one main UV map and two additional UV maps for two more detailed parts of the mesh; has a simple Cycles material that only uses a handful of image textures: baked and hand-painted textures combined with a normal map.

I have prepared an image for the final diffuse texture and another for final normal map to be used with the model in the game engine. Problems arise when I'm trying to do these final bakes. During baking normals Cycles decides to switch to the already existing AO image (named AmbientOcclusion in the screenshot below) and then bake the AO (not normals as I have requested) again on the final normal map that I have specified as the bake target image. Still following? This image might clarify things:

You can see through the few gaps left by two parts of the mesh with separate UV maps that the purple-ish image I prepared for the normals to be baked onto shines through the ambient occlusion bake that for whatever weird reason Cycles decided to bake instead of the normals.

And yes I do have two image nodes in my Node Editor ready for the corresponding final texture (diffuse map) and normal map.

Image mode with the image (that will be the normals bake) selected and node is active.

Can anyone help clarify if I am doing something awfully wrong or if Cycles is making me go crazy? I see no logic in it's behavior when I select 'Normal' in Bake Type, click Bake and end up with AO on top of my normal image canvas. I have restarted Blender and my computer to see if it was just a reference issue or something but alas, no luck.

EDIT: In fact, when I try to do the diffuse bake (with only color selected in bake settings) Cycles manages to bake on the right image even though the information displayed in the info bar is still wrong:

enter image description here

...because I'm baking diffuse on to a image named ConeHat_d.

What's going on?

$\endgroup$
0
$\begingroup$

Alright, after some hours of needless research I figured it out on my own.

My model was using 3 separate materials: one for main mesh, one for camera details (painted and baked textures) and one for cable ribbon details (also painted and baked textures). I had placed two image nodes - one for final diffuse texture and one for final normal map - only in the main material. I had to copy the two nodes also to the remaining two materials I used for detailing. Now baking worked as it should.

I imagine previously when I hadn't specified the bake targets for the remaining two materials Cycles was just picking a random texture node already present in the node tree and baking on top of that - and in this case it was my ambient occlusion map which was shared among all the three materials.

Hope this helps others struggling with trying to bake multiple materials into one final texture.

$\endgroup$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.