OctaneRender™ 2019.1 RC1 Tweet

[funk]

Autobump bug:

1. Load ocs and select the composite material to render it
2. Select material 1 and change the IOR

The autobump on the displacement stops rendering. You have to restart the render to see it

[funk]

The composite material node "Material 1 Mask" pin does nothing.

I mentioned this in the XB2 thread too. Why is it there?

It should work as an opacity modulator for the first material. I'll look into this myself.

Thanks Jules

[funk]

Coating layer bug:

Reflections are too dim at roughness of 0

[pegot]

I too was having problems getting Mask 1 to work on composite node but just figured I was using it wrong...

[Zay]

Whenever I had those in my situation, I always try to see if any of the following make a difference, by seeing if other users with a similar arrangement are experiencing the same thing or not:
Win 7 vs Win 10
Nvidia Driver
Gpu arrangement and settings

As a reference, i am using
-Win 10,
-Nvidia 425.31,
-and am not using my main mobo GPU for rendering, only my external 7 Pascal Titan X. I only have one of these set to use Denoising and Tonemapping, all the rest are just active, with no other boxes checked.

One other thing to try is just the mobo GPU by itself to see if it works when using just the 1 card. And then, test 2 or more cards, to see if it makes a difference in any way.

After a loooong day of testing hardware/software I found out it works on Win 10. Unfortunately I can't use win 10

[Notiusweb]

Whenever I had those in my situation, I always try to see if any of the following make a difference, by seeing if other users with a similar arrangement are experiencing the same thing or not:
Win 7 vs Win 10
Nvidia Driver
Gpu arrangement and settings

As a reference, i am using
-Win 10,
-Nvidia 425.31,
-and am not using my main mobo GPU for rendering, only my external 7 Pascal Titan X. I only have one of these set to use Denoising and Tonemapping, all the rest are just active, with no other boxes checked.

One other thing to try is just the mobo GPU by itself to see if it works when using just the 1 card. And then, test 2 or more cards, to see if it makes a difference in any way.

After a loooong day of testing hardware/software I found out it works on Win 10. Unfortunately I can't use win 10

How were you able to test? If another machine you may have introduced whole number of other variables.
Anyway, I was there myself not too long ago, I cloned my win 7 drive and updated a copy. Never went back to the 7, too many other apps now using its feature set.

[funk]

Universal / coating / transmission bug:

I have made specular red to make it obvious. Coating color greater than 0 (black) makes the red specular vanish

[Notiusweb]

Could we get a render viewport icon just for the Upsampling?
...would be nice to be able to select the modes using an icon from the viewport toolbar.
THX

[Jolbertoquini]

Hi Guys,

me again, I can explain more in details the bug, for examples Maya has two types of Instances, one is the "instancer and instance" they are two different types when we get this alembic has also different types, until 3.06 it was supported the instances and instancers but after from 4.05 is only support instancers not the commun instance when using alembic for mesh of course.

I will set a scene and add here for download test.

Best,
JO

UPDATE:

Scenes attached here. Please also pay a close attention on memory usage at the same scene? 3.06 uses close to 285mb, 4.05 uses 495mb and 2019RC1 uses 616mb ? there is a huge increase and this is the one with the instancing working.

Hi Dev team,

Any news about this fixes on the alembic? would be great to know if you Guys will look at?

Best,
JO

[Jolbertoquini]

Hi Guys,

Congratulations for the update, I tested aswell with a lot scenes here please check this posts:

https://render.otoy.com/forum/viewtopic.php?f=33&t=72084&p=365551#p365551
https://render.otoy.com/forum/viewtopic.php?f=24&t=71916&p=365548#p365548

Hi There,

After using this version for a while I find a interesting bug problem, compare to Octane 3.06 and the 4.05 there is a clear slowdown on the sampling at 3.06 I have "25ms/sec" I have in 10 seconds close to "400s/px" and at 4.05 I have "0.020ms/sec" sometimes lower like "0.01ms/sec" and get "1s/px" after 25 seconds which is crazy slow after one minute I still get 4 samples, I also tried on 2019XB2 for test is compiling the scenes really slow but the samples is better getting more close to the "25ms/sec" of the 3.06 but freezes at begging and after is getting unstable sampling, between "0.020ms/sec" to "10ms/sec".

I tested same scene with a 1080ti windows 10, also with sets on windows 7 and different GPU 700's and 900's series same results.

I could share the scene but I need on private for security and private reasons.

Please let me know.

Best,
JO

I think there is a sampling problem also scene consistency between versions in look I will post here images aswell but look are different and "ms/sec"

Best,
JO

Hi Dev Team,

per my comment here, I know one issue is the alembic but there is a inconsistency on look of shaders on this scene compare to 4.05 and 2019's version to who should I send this scene on private to check the problems?
I have send the scene on this chat for the Alembic issue but not the shading because we can't share this scene, but I'm happy to share in private.

Best,
JO