I'm trying to have 1 UV tag that is being used to map a texture onto geometry, and the baking camera bake this out to 2nd UV tag on the same geometry's UVs.
UV Set setting in Baking Camera
Moderators: ChrisHekman, aoktar
I know the UV set field does not function inside of materials, the help file says as much. But according to the help file, the UV Set in the octane camera tag baking camera section should be able to set which UV to bake to. When I change UV set in the tag, the render output just goes black. Is this UV set functional?
I'm trying to have 1 UV tag that is being used to map a texture onto geometry, and the baking camera bake this out to 2nd UV tag on the same geometry's UVs.
I'm trying to have 1 UV tag that is being used to map a texture onto geometry, and the baking camera bake this out to 2nd UV tag on the same geometry's UVs.
-
jayroth2020
- Posts: 488
- Joined: Mon May 04, 2020 7:30 pm
A corresponding UV set needs to be present in the object. How are you defining your UV sets?
Puget Systems / Intel Core Z790 ATX / RTX 4090 / Cinema 4D
-
jayroth2020
- Posts: 488
- Joined: Mon May 04, 2020 7:30 pm
That is what Octane expects, so I recommend you submit a ticket and we will take a look: [email protected] Make sure you do a File > Save Project with Assets... archive the results and send it in.
Puget Systems / Intel Core Z790 ATX / RTX 4090 / Cinema 4D
There might be some confusion because this sentence is confusing to me: "the baking camera bake this out to 2nd UV tag on the same geometry's UVs", and the fact that you used UV set = 1 and Baking group ID = 2 makes me think there is maybe something misunderstood.
The baking camera creates a texture. To create that texture it needs to map the geometry to the camera pixels, as if the camera was a texture. This mapping uses the "UV set" parameter. So if you want the baking camera to use the second UV set you should set it here UV set = 2. This implies that when you use the result of this baking somewhere else you will have to use that second UV set to map the texture created onto the geometry.
The baking group ID is completely different and makes sense if you also have an object layer attached to the geometry with the corresponding value in its Baking group ID field. It lets you bake a very specific object if you have several in the scene. If you don't have any object with baking group ID = 2 you will get a black picture.
Note that the mapping of UV to camera is the inverse operation as typical texture mapping (it goes from a given UV on the output image to the corresponding polygon) and so it can only work if you have non-overlapping triangles in your UV map. If your UVs have coordinates outside the unit square you also need to specify it here in UV region.
The baking camera creates a texture. To create that texture it needs to map the geometry to the camera pixels, as if the camera was a texture. This mapping uses the "UV set" parameter. So if you want the baking camera to use the second UV set you should set it here UV set = 2. This implies that when you use the result of this baking somewhere else you will have to use that second UV set to map the texture created onto the geometry.
The baking group ID is completely different and makes sense if you also have an object layer attached to the geometry with the corresponding value in its Baking group ID field. It lets you bake a very specific object if you have several in the scene. If you don't have any object with baking group ID = 2 you will get a black picture.
Note that the mapping of UV to camera is the inverse operation as typical texture mapping (it goes from a given UV on the output image to the corresponding polygon) and so it can only work if you have non-overlapping triangles in your UV map. If your UVs have coordinates outside the unit square you also need to specify it here in UV region.
Sorry for the confusion. I'm using the baking group id for a different function than my question. The file is baking 5 different UV sets out from 5 different pieces of geometry, in 5 different takes, hence the Baking Group ID to differentiate.jobigoud wrote:There might be some confusion because this sentence is confusing to me: "the baking camera bake this out to 2nd UV tag on the same geometry's UVs", and the fact that you used UV set = 1 and Baking group ID = 2 makes me think there is maybe something misunderstood.
The baking camera creates a texture. To create that texture it needs to map the geometry to the camera pixels, as if the camera was a texture. This mapping uses the "UV set" parameter. So if you want the baking camera to use the second UV set you should set it here UV set = 2. This implies that when you use the result of this baking somewhere else you will have to use that second UV set to map the texture created onto the geometry.
The baking group ID is completely different and makes sense if you also have an object layer attached to the geometry with the corresponding value in its Baking group ID field. It lets you bake a very specific object if you have several in the scene. If you don't have any object with baking group ID = 2 you will get a black picture.
Note that the mapping of UV to camera is the inverse operation as typical texture mapping (it goes from a given UV on the output image to the corresponding polygon) and so it can only work if you have non-overlapping triangles in your UV map. If your UVs have coordinates outside the unit square you also need to specify it here in UV region.
Simply put, I want to texture an object using UV tag 1, and baking-camera render that texture out to UV tag 2. My final output UV texture layout needs to stay constant, but I want to use a different UV tags for texturing to allow for different mapping.
I've submitted a ticket with a simplified example c4d project highlighting the issue. Appreciate the help!jayroth2020 wrote:That is what Octane expects, so I recommend you submit a ticket and we will take a look: [email protected] Make sure you do a File > Save Project with Assets... archive the results and send it in.