abstrax wrote:I just tried it in the Standalone and there it doesn't happen. I assume you are using one of the plugins? In that case it's probably best to report to the plugin developer since the materials are usually managed outside of the Octane render core (which is due to the fact that each host application has its own totally different material system).boeing727223 wrote:I apologize if this has already been posted and I missed the post. I notice that RC 5 (and RC 4) automatically changes the Opacity channel from a Greyscale image (that I originally assigned) to an Alpha image after I saved and relaunched the scene. If I load a Greyscale image in the Opacity channel, save the scene, close it and then re-launch the scene it should remain as a Greyscale image not default to an Alpha image.
Hi abstrax,
I did some more testing using the Standalone. When I export an .obj figure out of DAZ studio (includes hair with Grayscale transparency maps) and import into Octane 4 RC5, RC6, or RC7 the opacity maps default to Alpha image instead of Grayscale image. I must change each opacity channel to Grayscale images and load the transparency map Grayscale image. When all opacity map channels have been corrected and saved, I get no further issues with that specific .obj. If I import a new .obj figure in the whole process starts over with the new figure. Previous versions did not have this happen. Octane recognized the Grayscale transparency maps as Grayscale images. The issue is the initial import of an .Obj into Standalone. I have only tested DAZ studio .obj exports.