Dear all,
It seems opacity values setup into Sketchup are not loaded by Octane.
Do you know if it will be changed in a future release ?
Thanks
Pascal
SU export - Octane opacity support
This is probably the same issue as here: http://render.otoy.com/forum/viewtopic. ... 6&p=110248
The problem may not be limited to sketchup. If not then it should be solved in coming releases.
Are you using 1.00 RC3?
Cheers
Chris.
The problem may not be limited to sketchup. If not then it should be solved in coming releases.
Are you using 1.00 RC3?
Cheers
Chris.
The current version still fails to read and then apply the 'd' opacity values for materials from the OBJ file's MTL file.
This is not directly connected to SketchUp.
ANY OBJ/MTL file that defines a 'plain' material uses its RGB values but ignores its opacity 'd' [or 'Tr'] value - always using '1'.
If a material has a texture image specified then this is used: if that image is a PNG and it that transparency then this IS used.
Since you can specify a 'plain' material in the OCS and adjust its 'opacity' settings, then it shouldn't be that awkward to automate this on an import...
Until this oversight is resolved... it IS readily fixed manually... open the MTL file in a plain text editor.
It has a block of text for each material.
Read down and find the 'd' value for each material in the file.
If it's not set to be 1 then look down the OCS node's material list and find the equivalent named material... in its 'opacity' setting add the equivalent 'd' number from the MTL.
If you subsequently save the OCS the current opacities are remembered across sessions...
This is a long standing issue that ought to have been resolved ages ago...
This is not directly connected to SketchUp.
ANY OBJ/MTL file that defines a 'plain' material uses its RGB values but ignores its opacity 'd' [or 'Tr'] value - always using '1'.
If a material has a texture image specified then this is used: if that image is a PNG and it that transparency then this IS used.
Since you can specify a 'plain' material in the OCS and adjust its 'opacity' settings, then it shouldn't be that awkward to automate this on an import...
Until this oversight is resolved... it IS readily fixed manually... open the MTL file in a plain text editor.
It has a block of text for each material.
Read down and find the 'd' value for each material in the file.
If it's not set to be 1 then look down the OCS node's material list and find the equivalent named material... in its 'opacity' setting add the equivalent 'd' number from the MTL.
If you subsequently save the OCS the current opacities are remembered across sessions...
This is a long standing issue that ought to have been resolved ages ago...
TIG