Version 3.00 - R1.1 (25.05.2016)

[aoktar]

Is that ok if during working LV, in Octane Tag i switch to use 3rd party shaders and choosing Tempreture instead of Density for Abs/sct. channel, Octane goes to Render Failure (Cuda error 719) and addicionaly this failure takes down all used GPUs in LV (downgrade clocks to minimal) so i need to restart computer to "refresh" GPUs.
I found this on every TFD Sample scenes provided.

Using this option is slow due TFD's shader sampling function. It's working much slower to calculate voxel values. Don't know why cuda errors happened. Can you post a output from logs?

[aoktar]

Here is a test build for before doing a release. I'll need some information about stability. This is first working version with material stacking. I wrote the limitations.

R17-Win: https://render.otoy.com/customerdownloa ... -test3.rar
R17-Mac: https://render.otoy.com/customerdownloa ... Macosx.zip


Changes of V3.01-test3
- Fix: ignored range parameter in animated sequences
- Fix: Not visible volume/scatter objects on first frame renders
- Experimental material stacking feature
- Fix: enabled partial-alpha parameter for old scenes.

MATERIAL STACKING LIMITATIONS
-limitations: only works with c4d materials and octane materials and will not work with mix materials in any combination
-works with flat/cube/cylindrical/spherical projection types. Doesn't account the current tag's UVW mapping coordinates. It takes it from previous material which has not alpha/opacity.
-Can work with selection assignments. But it's still limited on complex selection sets
-go with mix material setups for advanced usages

[brasco]

Hi Ahmet,

Thanks for the build, I'm just getting a black Live Viewer with "Updating" just counting up and nothing happens:



cheers
brasc

[aoktar]

Checked but it's looking fine to me. Do you see these output in console?

[brasco]

Thanks Ahmet,

Yes, I get that output in the console:


I just tried going back to 3.00 r1.1 and it's now doing the same thing, it was working just before I tried this new test build.

I can also run Octane Standalone fine and it renders things.

cheers
brasc

[aoktar]

I just tried going back to 3.00 r1.1 and it's now doing the same thing, it was working just before I tried this new test build.
I can also run Octane Standalone fine and it renders things.
cheers
brasc

Make a sign out from standalone+plugin and sign in. Check outputs in log window and licences page. It's working on a few guys here.

[mrom]

oh, material stacking - right, when I need it. thank you aoktar, gonna try this now.

[brasco]

I just tried going back to 3.00 r1.1 and it's now doing the same thing, it was working just before I tried this new test build.
I can also run Octane Standalone fine and it renders things.
cheers
brasc

Make a sign out from standalone+plugin and sign in. Check outputs in log window and licences page. It's working on a few guys here.

Hi Ahmet,

Sorry, it looks like it was an issue with one of my GPUs... If I try and start rendering with my Monitor GPU I get that issue ("Updating..." and no render), if I start with one of my other GPUs first, it renders fine and I can even add the Monitor card back in during rendering and then it works. It's probably related to that problem I posted a few weeks ago in the Bug Reports forum. I will do some more testing see if I can work out what's causing it.

cheers
brasc

[Ron]

Hi Ahmet,

the Test3 version is working well with me. Stacked 3 materials - one C4d with two octane.

Another try ...

Thanks - your imrovements are always awesome!

Ron

[Improdu]

Hello Ahmet,

Just to notify you about a crash with the Daylight Tag.
In the medium tab, when you already added a medium, and then you click the "Add Fog" button, it causes a crash of c4d.

Windows 10, R17, Octane V3 1.1

Clement