(solved sorry) odd Octane UV issue
Posted: Tue Dec 09, 2014 3:26 am
this still might prove to be usefull info to others
if you edit stuff like surfaces exporting and obj and re-importing as a new UV set may be also needed for Octane.
I modified the DAZ supersuit heavily combining surfaces and deleting polygons and saving as a new support asset.
I dd so largely with Octane in mind as it had so many surfaces.
it renders fine in 3Delight still and an exported FBX on a figure retains its UV mapping in iClone but for some reason it is all messed up in Octane? I am wondering how the UV mapping can change in Octane?
I see this often with geografts but those do that in carrara and iClone too and prob any other third party export, is due to shared polygons I presume, I only deleted polygons and did not add any or change the vertex count on remaining ones and just deleting has never affected UV mapping though it can rigging but in DAZ with polygon editor this has never been an issue so long as I retain the grouping.
if you edit stuff like surfaces exporting and obj and re-importing as a new UV set may be also needed for Octane.
I modified the DAZ supersuit heavily combining surfaces and deleting polygons and saving as a new support asset.
I dd so largely with Octane in mind as it had so many surfaces.
it renders fine in 3Delight still and an exported FBX on a figure retains its UV mapping in iClone but for some reason it is all messed up in Octane? I am wondering how the UV mapping can change in Octane?
I see this often with geografts but those do that in carrara and iClone too and prob any other third party export, is due to shared polygons I presume, I only deleted polygons and did not add any or change the vertex count on remaining ones and just deleting has never affected UV mapping though it can rigging but in DAZ with polygon editor this has never been an issue so long as I retain the grouping.