Version 3.08-test6.1 (TEST VERSION) updated on 8.12.2017

Sub forum for plugin releases

Moderators: ChrisHekman, aoktar

Locked
bododge
Licensed Customer
Posts: 24
Joined: Thu Jun 11, 2015 2:20 pm

What about? About problems with OVDMmesher? What's that?
He means the Open VDB Mesher in X-particles 4.
User avatar
bepeg4d
Octane Guru
Posts: 10326
Joined: Wed Jun 02, 2010 6:02 am
Location: Italy
Contact:

benjaminxo wrote:Hi there,
It looks like the beta version doesn't work with the Vr subscription?
It shows "Could not find the required license".

Is this normal ?

Thanks !
Hi,
please, have a look a couple of page before in this thread:
viewtopic.php?f=85&t=64382&start=70#p327966
ciao beppe
PHM
Licensed Customer
Posts: 21
Joined: Wed Feb 24, 2016 10:38 am

rodross wrote:Looks like there's a bug with mixtextures. Try putting a mixtexture into the diffuse, put it on an object, and send over with an octane sky (no need for hdr). It does some weird stuff especially when you toss in a dirt shader as the mix amount. Renders half and/or quarters of the image wrong.
I think I can add to this: doing some testing it looks like mix materials in 3.08 break if they've got textures in and you are using slaves.

On 3.07, with no slaves:
2017-12-12 11_35_59-Live Viewer 3.07-R2.png
On 3.07, with slaves:
2017-12-12 11_35_59-Live Viewer 3.07-R2.png
On 3.08, with no slaves:
2017-12-12 11_37_35-Live Viewer 3.08-Test6.0.png
On 3.08, with slaves:
2017-12-12 11_42_06-Live Viewer 3.08-Test6.0.png
Here is the material, we have been using it since 3.0:
2017-12-12 12_00_37-Octane Node Editor.png
I haven't had time to try and convert it to an Uber material, but I'm guessing this change has something to do with it?

EDIT: Looks like it is happening in standalone too
viewtopic.php?f=33&t=64362&p=328272#p328267
Attachments
2017-12-12 11_44_17-Live Viewer 3.07-R2.png
Octane 3.07.R2 | Cinema 4D 18.057
Windows 7 64bit | 64GB RAM | 8x Geforce GTX 1080ti/8x Asus Strix GTX980ti
Studio21
Licensed Customer
Posts: 212
Joined: Wed Nov 16, 2016 11:14 am

Hi Ahmet,

There is a problem with the Xparticles instance ID color in the latest release:
xparticles instance id color problem.png
Some particles flicker\colored black as u can see using the instance ID node on the xpemitter. same scene works as expected with 3.07

Using XP4 and the latest r18 version

Best,
Guy
User avatar
aoktar
Octane Plugin Developer
Posts: 16063
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye
Contact:

Studio21 wrote:Hi Ahmet,

There is a problem with the Xparticles instance ID color in the latest release:
xparticles instance id color problem.png
Some particles flicker\colored black as u can see using the instance ID node on the xpemitter. same scene works as expected with 3.07

Using XP4 and the latest r18 version

Best,
Guy
Instance color has problem with indexing in this sdk. Also netrender has some problems.
Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
zinogino
Licensed Customer
Posts: 119
Joined: Wed Dec 02, 2015 3:50 am
Location: Malaysia

Noticed getting constant crashes when using the node editor on metal materials.
Tweaking the specular channel and specular map crashes from time to time.
Timelinedenmark
Licensed Customer
Posts: 8
Joined: Fri May 20, 2016 4:22 pm

Would still love to know how OTOY expect us to use N & K Values in the new metal material. To my knowledge, every single piece of reference is based on separated RGB channels, and not a single value.

For example Copper:

Red channel (0.65 µm): N - 0.27 / K - 3.60
Green Channel (0.55 µm): N - 0.67 / K - 2.62
Blue Channel (0.45 µm): N - 1.31 / K - 2.29

In octane, we have a single N & K value, not 3. It´s the same thing in Standalone version, so not plugin "only" related.
rodross
Licensed Customer
Posts: 135
Joined: Fri Jun 27, 2014 3:01 pm

Timelinedenmark wrote:Would still love to know how OTOY expect us to use N & K Values in the new metal material. To my knowledge, every single piece of reference is based on separated RGB channels, and not a single value.
https://refractiveindex.info/

This site is what I use for it.
rodross
Licensed Customer
Posts: 135
Joined: Fri Jun 27, 2014 3:01 pm

PHM wrote:
rodross wrote:Looks like there's a bug with mixtextures. Try putting a mixtexture into the diffuse, put it on an object, and send over with an octane sky (no need for hdr). It does some weird stuff especially when you toss in a dirt shader as the mix amount. Renders half and/or quarters of the image wrong.
I think I can add to this: doing some testing it looks like mix materials in 3.08 break if they've got textures in and you are using slaves.
Yea we had to drop back to 3.07 for now because of this bug. We run 7 slaves. I never thought about it being a netrender issue.
Timelinedenmark
Licensed Customer
Posts: 8
Joined: Fri May 20, 2016 4:22 pm

rodross wrote:
Timelinedenmark wrote:Would still love to know how OTOY expect us to use N & K Values in the new metal material. To my knowledge, every single piece of reference is based on separated RGB channels, and not a single value.
https://refractiveindex.info/

This site is what I use for it.

You do know, that in order to use above link correct (refractiveindex), you have to input the wavelengths for Red, Green and blue right? Otherwise it´s just an IOR.

Try Google "Complex IOR". Every source out there is based on 3 x n & k values. One n & k value for each channel.

How it should look like:
https://support.solidangle.com/display/ ... omplex+IOR
https://docs.chaosgroup.com/display/OSL ... nel+shader
Last edited by Timelinedenmark on Wed Dec 13, 2017 6:55 pm, edited 1 time in total.
Locked

Return to “Releases”