That seems to fix that problem.
Normal should be set at disconnect if not used, not at 0.0
Thanks!
Moderator: face_off
FYI - I have reported this to Otoy, so hopefully there will be a fix in the next Octane 3.06 release. I think that the 0, 0, 0 value in the normal map might be an invalid normal vector, so perhaps having a 0 Greyscale texture in the Normal pin should have have worked.Now I have no idea how that happened, as I hardly use Normal maps, but matter of fact is, when actually disconnecting them, the materials are rendering correctly again. As far as I can tell.
wimvdb wrote:The Cuda 700 error seems to occur when you have the viewport open and rendering and you then change materials (in my case loading a white leather materials from LiveDB)
Render stops and cuda errors appear and you have to restart Poser
I could not reproduce this issue at all. I loaded a bunch of LiveDb materials and none exhibited this issue. Can you pls tell me a LiveDb material name which causes this issue? Can you also post you OctaneDefaults.py file and a screenshot of your plugin configuration/setup screen.It's kind of interesting, that even the oldest, or randomly loaded materials I have stored locally, or load from the LiveDB, now all have the Normal pin with a Greyscale Color set to 0.0 attached to them, when applying them to a mesh.
So in between all the betas, test builds and whatnot, this must have sneaked in totally unnoticed
face_off wrote:I could not reproduce this issue at all. I loaded a bunch of LiveDb materials and none exhibited this issue. Can you pls tell me a LiveDb material name which causes this issue? Can you also post you OctaneDefaults.py file and a screenshot of your plugin configuration/setup screen.It's kind of interesting, that even the oldest, or randomly loaded materials I have stored locally, or load from the LiveDB, now all have the Normal pin with a Greyscale Color set to 0.0 attached to them, when applying them to a mesh.
So in between all the betas, test builds and whatnot, this must have sneaked in totally unnoticed
Thanks
Paul
Bump channels are not a problem. They can be 0 instead of Not Connected. It's only Normal pins where it is an issue.I could reproduce the same issue with the Bump channel as well.
I do not get a 0 Normal value if I load Amethyst Marble. I get the following.Then very 1st LiveDB mat "amethyst marble" (some pink-ish stone mat.) "LiveDB - Organic - Stone - amethyst marble"
What does the last sentance mean pls? When was "before"? Which plugin version pls?Loading the material "Red Brick", "LiveDB - Absolute Textures - Brick - Red Brick", puts a Greyscale into the Bump channel at 0.0. It was disconnected before.
Users browsing this forum: No registered users and 30 guests