Offline Mode please. It's useless to me without this & I'm not the only one.
3.07 had it so why has it stopped ?
OctaneRender™ Standalone 3.08.2
viewtopic.php?f=24&t=68091#p341483andrefry wrote:Offline Mode please. It's useless to me without this & I'm not the only one.
3.07 had it so why has it stopped ?
ciao Beppe
Fingers crossed.abstrax wrote:This version doesn't have an offline mode yet. We are currently finishing a new system which unfortunately didn't make it into this version yet, but we hope to have something available very soon (I am talking of a couple of weeks not months). Again, apologies for the delay.Dmi3ryd wrote:Thanks for update.
I can't find offline license. Where is it?
Asus Sabertooth X79, i7-4930K, Corsair 32GB, 1080 TI Hybrid, 2070 Super hybrid,
Win 10, C4D R19.068, Octane 4.05-R7
Win 10, C4D R19.068, Octane 4.05-R7
Sorry I don't have a confident ETA yet, but the next release will most likely by in the next couple of weeks. We are trying to wrap up 3.08 as quickly as possible.niestudio wrote:Thanks for the update. Any ETA on that? Really looking forward to using the metallic shader properly.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
I'm seeing info channel issues in 3.08.1 & 3.08.2 (they were not present in 3.08).
renders properly in 3.08. 3.08.2 renders blank There are several other info channels that render strange as well.
renders properly in 3.08. 3.08.2 renders blank There are several other info channels that render strange as well.
You do not have the required permissions to view the files attached to this post.
OSX 10.12.4 | Intel 12 core @ 3.33 ghz | 128 gb ram | NVIDIA GeForce GTX 1080TI | Ubuntu Linux slave with 3x 1080ti
Thanks for the bug report. It seems that negative values in the normal vectors are clamped at zero. -> The back side of the cube is rendered grey (which is why it looks invisible). It only seems to happen if the info channel kernel is used. Info channel passes seem to be fine. -> We will fix it with the next version.niestudio wrote:I'm seeing info channel issues in 3.08.1 & 3.08.2 (they were not present in 3.08).
renders properly in 3.08. 3.08.2 renders blank There are several other info channels that render strange as well.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
I have made a Start.orbx to start projects a little faster. But every time I load it and ungroup it, it keeps adding (2) to the Render Targets name. If I group it again and ungroup it I now have (2) (2) added to the Render Targets. Is there a way to prevent this or is this a bug?
You do not have the required permissions to view the files attached to this post.
Win 11 Pro | i5 12600K | 32GB ram | 2x GTX 1080Ti + 3080Ti - studio driver 560.94| Modo/Blender/ZBrush/Daz/Poser
That it doesn't properly increase the count but appends "(2)" every time is a bug.Zay wrote:I have made a Start.orbx to start projects a little faster. But every time I load it and ungroup it, it keeps adding (2) to the Render Targets name. If I group it again and ungroup it I now have (2) (2) added to the Render Targets. Is there a way to prevent this or is this a bug?
We did this incremental count initially because of ORC (to make sure that render target nodes have a unique name), but with some changes in ORC we could disable it and we are planning to do that in a future build.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Changing near clipping distance of the camera affects the functionality of the focus picker tool - the resulting focal depth value.
If near clip depth was set to 2.000, focal depth became, say 5.661; if it reset to 0.000 value, the focal depth became 3.663 (which is proper value for getting desired object in focus).
Not tested on all scenes, just found it on current one.
If near clip depth was set to 2.000, focal depth became, say 5.661; if it reset to 0.000 value, the focal depth became 3.663 (which is proper value for getting desired object in focus).
Not tested on all scenes, just found it on current one.
AMD R7-2700/64Gb/RTX2080Ti 11Gb + RTX2080 8Gb/Win10 Pro x64/nV driver 451.67/Poser10, DS4.12, Blender2.79, Octane 4.05 Standalone
> Using RAM Disk with Octane <
> Using RAM Disk with Octane <
