Hi,
I have a question concerning texture-baking.
The problem I'm facing is to get the baking from one-UV-set to an other.
explanation: I've got a plane with regular UV-mapping. After baking this one out, the result is a stretched texture.
So I tried to "unwrap" this plane and get a non distorted UV-Layout, which messes up the texture itself... as it doesn't fit anymore.
Now I wanted to make use of the UV-set-feature inside the Camera-tag where I tried to bake the texture from first UV-layout onto the second UV-layout...
but the result is the same... is this a bug or do I miss the point of this feature and have a wrong understanding of it.
How do I even know the numeration of the UV-sets... where can I see (if there are 2 or 3), which one's the first, second or third... or is C4d just looking how they are arranged.
I'm using C4D R19 and Octane 3.08.
Many thanks in advance!
Baking Problems with different UV Channels
Moderators: ChrisHekman, aoktar
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
- Attachments
-
- Cinema4DUV-set-example.zip
- (168.38 KiB) Downloaded 194 times
Hi,
since in c4d you cannot define the UV set, like you can do in other apps, you need to change the order of the uv tags in the Object manager: the first uv tag encountered is taken into account: You could use the Take system to automate the process.
ciao Beppe
since in c4d you cannot define the UV set, like you can do in other apps, you need to change the order of the uv tags in the Object manager: the first uv tag encountered is taken into account: You could use the Take system to automate the process.
ciao Beppe
Thanks for clearing this out for me.
Now my real problem is...
while the shadow gets compressed to the new UV-Set, why doesn't this happen to the actual texture itself, which is what I tried to achieve.
At the moment the texture just gets cut away.
Now my real problem is...
while the shadow gets compressed to the new UV-Set, why doesn't this happen to the actual texture itself, which is what I tried to achieve.
At the moment the texture just gets cut away.
Hi,
that's what you are actually doing, the texture is cutted, instead of been used completely, it's the same also in Viewport.
What is exactly your goal?
Have you seen this document about Baking, and in particular, how to bake multiple objects?
Texture Baking
ciao Beppe
that's what you are actually doing, the texture is cutted, instead of been used completely, it's the same also in Viewport.
What is exactly your goal?
Have you seen this document about Baking, and in particular, how to bake multiple objects?
Texture Baking
ciao Beppe
Ok, but do you want to obtain something similar to this at the end?

ciao Beppe

ciao Beppe