OctaneRender™ 2019.1 XB2

[calus]

Thin Film doesn't seem to work for me - tried a couple of scenes and no luck - can somebody else confirm this please.

I can confirm thin film Layer is broken for legacy Glossy Material in this release, but works fine for other materials.

[calus]

In most cases our design decisions balance finely between speed and usability. We had layers more separated before, but this presented a few problems: things become more complicated; you hit the limit of how many layers you can have much more quickly, and thirdly you pay dearly in VRAM.

I see, sorry I was pushy about that, it seems I'm way too late in the design discussion.
And the feature is already there: I mean if I need a consistent Thin Film Layer as a layer node I can just use a Specular layer node with same IOR for specular and thin film,
this was just about simplifying the layers.

[funk]

This scene has a layered material with a diffuse mat as a base material. Octane is not updating when I change the rounded edge radius

1. Select the render target to start rendering
2. select the test nodegraph > round edges node and change radius

Nothing happens. You have to stop the render and restart it to see the change

[funk]

A weird layer related bug. Both meshes have the same material, which uses a material layer. One renders purple while the other is black

NOTE: If I set this up using a layered material, it works OK. I'm using a base material with specular layer plugged into the material layer pin and this seems to be causing the bug.

[haze]

I am getting GPU orange and red crashes when I use up-sampling. Octane does not like me turning it on and off and modifying in an active scene.

I haven't been able to reproduce this problem. Can you tell me how exactly you were doing that? Does it happen on any scene and any resolution?

[haze]

Hi guys,
AI up-sampler crashes using Titan X (Maxwell) and Windows 7, not using window 10. Pascal works fine.
Regards
Paride

Would you be able to reproduce that and send us the log? Please put cudaAlwaysSync in octane_log_flags.txt as well

[funk]

CUDA crash toggling shadow catcher pin on and off

1. Load the orbx and select the render target to start rendering
2. Select the mat1 nodegraph > diffuse material
3. Toggle shadow catcher on/off a few times

Code: Select all

Started logging on 17.06.19 10:05:27

OctaneRender Enterprise 2019.1 XB2 (6000001)

CUDA error 719 on device 0: unspecified launch failure
  -> failed to wait for event
device 0: path tracing kernel failed

[Notiusweb]

I am getting GPU orange and red crashes when I use up-sampling. Octane does not like me turning it on and off and modifying in an active scene.

I haven't been able to reproduce this problem. Can you tell me how exactly you were doing that? Does it happen on any scene and any resolution?

Happens on any scene at any resolution. Try 1080p, use upsampling, then switch to no-sampling, in my case GPUs sometimes, not always, go orange. I have to hit stop and the reload the render when it does.
Also, I have now found that if I am using upsampling and select a render pass, such as Object Layer or Render Layer Mask, it will also cause GPU readout to go orange, where I must stop and restart render.
It is like the modes themselves will work, but XB2 doesn't like me switching from Up-sampling to Sub-sampling/No-sampling, without stopping first.

I have noted that this never occurs when I just straight use up-sampling without shifting sampling modes, or if I use just regular sub-sampling straight on without ever shifting sampling modes.

[Notiusweb]

Have found saving any type EXR also crashes XB2 on any scene.

[Notiusweb]

XB2 shows Build Expires 5Weeks 6Days, but then shows my license expiring in 1 week.
(I have then Enterprise All-Access)