adamnerva wrote:the biggest issue with the Octane plugin for Unity right now. I am building out a render test scene, but every time I come back to it, all of my custom shaders are wiped.
And for me, the second biggest issue would be poor conversion of the Unity standard shader (no tiling, no detail textures, no gloss maps, etc), and so custom user shaders are an absolute necessity for every surface, not just special cases.
Good feedback. Converting standard shaders (or standard specular shaders) should work with detail textures (this specifically added in Octane to handle Unity assets). Gloss map is just an inverse roughness map and this too should work. We'll look into both of these issues ourselves, but any specific scene data you could share might help isolate what is going on more quickly.
Custom shaders created in Unity are still a WIP as we figure out where this goes in the spectrum from std. Unity material auto-conversion -> pure ORBX material importing. Even so, anything we expose as values the Unity Editor panels should work, so if that's broken it's a bug we should track and fix ASAP.