subdiv changes in V3 causing UV stretching

[aoktar]

Well please compare image. As you can see same mesh works different on standalones. As i said there is not any changes in plugin about issue. My advice to don't use Octane subdiv for this kind of situations. Go with C4D subdivision object.

[Studiolocal]

thanks for the look-in.
Aoktar I've mentioned this a few times in this thread, but i cant use this with-in the c4d sub-div object as it crashes c4d about 35 % of the time. which is alot.
Also when it does render it is 30 seconds slower per frame to use the c4d object, this is likely because via the octane object tag the mesh is subdivided by the GPU.
anyway regardless of crashes and speed per frame, it works fine in V2 to but wont work in V3
so can you please let me know if this is being logged as a bug somewhere ? either with you in the c4d bridge or with the main o-toy dev team ?

please dont advise me to use the c4d subdiv object again, its not an option.
i really need to know the answer if this problem is being looked at as it will affect what render engine i use for this project,
as you can imagine there is little point developing shots and scenes that will only ever work for octane render engine 2.0.

hopefully all the above is clear , i have tried to write it as straight forward as possible but let me know if i can help in any other way to get this sorted out.

thanks

Pete

[aoktar]

thanks for the look-in.
Aoktar I've mentioned this a few times in this thread, but i cant use this with-in the c4d sub-div object as it crashes c4d about 35 % of the time. which is alot.
Also when it does render it is 30 seconds slower per frame to use the c4d object, this is likely because via the octane object tag the mesh is subdivided by the GPU.
anyway regardless of crashes and speed per frame, it works fine in V2 to but wont work in V3
so can you please let me know if this is being logged as a bug somewhere ? either with you in the c4d bridge or with the main o-toy dev team ?

please dont advise me to use the c4d subdiv object again, its not an option.
i really need to know the answer if this problem is being looked at as it will affect what render engine i use for this project,
as you can imagine there is little point developing shots and scenes that will only ever work for octane render engine 2.0.

hopefully all the above is clear , i have tried to write it as straight forward as possible but let me know if i can help in any other way to get this sorted out.

thanks

Pete

What kind of crash? You can investigate why it's crashing when you use C4D subdivision. There is not real advantages to use octane subdivision as you said.
Very similar export times if you set same subdivision. Similar triangles counts. I suppose you're doing a mistake here.
Propably due different values for editor vs. render parameter in subdivision. See: viewtopic.php?f=86&t=54590#p278145

Also there is not any bug, but you can call it as BUG if you wish. Truth is that appearently some requirement has been changed in subdivision part of renderer and i just heard this.

As my final words, i can't change anythings in codes just for revision of V3. This is serious revision for me and i can't throw anythings to risk about stability of plugin.
At least in a short time period. I hope that's clear about situation.

[Studiolocal]

Hi

its not a mistake in the render/editor parameters. I am very familiar with these basic settings. So no its not that.
possibly its a problem with this character in that there is many many parts to it. Being a robot that is unavoidable in this case.
or perhaps from this rather obscure comment its because of some changes in V3 ?

Also there is not any bug, but you can call it as BUG if you wish. Truth is that apparently some requirement has been changed in subdivision part of renderer and i just heard this.

so there seems to be something different in V3 . . but is not a bug.
look i feel like this thread is rather pointless for both of us. I'll try and log this problem directly with O-toy.

thanks

Pete

[milanm]

Hi Pete

Good news! This is fixed in Octane 3.02.

viewtopic.php?p=279570#p279570

Regards
Milan