Yeah, I see what the problem is.
Obviously, the normal map node channel behavior was changed with the most recent update, and now Octane shows this weird surface, when there is s Normal node with a value of "0".
A quick fix for now would be to set every single Normal channel node to "1" instead of "0", that fixes the problem.
We'll release an update to fix this issue in the near future.
W10 64 bit | i7 3770K | MSI Geforce RTX 2080 (8GB) + GTX Titan Black (6GB) | 32 GB DDR3 RAMREALISTIC HUMAN SKIN SHADING - REDEFINEDRedSpec TGX Hair for Poser / DAZ Studio OctaneRender - OUT NOW