OTOY Forums

Hi, I'm curious if we can expect an early version of 2021 with full ACES support in the near future?

Sportler wrote:Hi, I'm curious if we can expect an early version of 2021 with full ACES support in the near future?

What do u mean by "full support"? I been checking it few days now and it works great.
Is there something missing? I checked other engines work the same way with same results.

thanulee wrote:

Sportler wrote:Hi, I'm curious if we can expect an early version of 2021 with full ACES support in the near future?

What do u mean by "full support"? I been checking it few days now and it works great.
Is there something missing? I checked other engines work the same way with same results.

Probably saying to have OCIO color space settings for Images.

Hi, Aoktar
Thank you for the R7 update. The LV is much smoother now! I really appreciate that.
Do you have an ETA for 2021.1 for C4D?
Regards,

Kalua wrote:Hi, Aoktar
Thank you for the R7 update. The LV is much smoother now! I really appreciate that.
Do you have an ETA for 2021.1 for C4D?
Regards,

Thanks you to for feedbacks! It's very important.
For 2021, It's mostly ready for previewing but waiting for next SDK for fixes. Then I'll make it available, surely it depends how much extra work is required.

aoktar wrote:

thanulee wrote:

Sportler wrote:Hi, I'm curious if we can expect an early version of 2021 with full ACES support in the near future?

What do u mean by "full support"? I been checking it few days now and it works great.
Is there something missing? I checked other engines work the same way with same results.

Probably saying to have OCIO color space settings for Images.

Yes, that's exactly what I meant!

aoktar wrote:

Kalua wrote:Hi, Aoktar
Thank you for the R7 update. The LV is much smoother now! I really appreciate that.
Do you have an ETA for 2021.1 for C4D?
Regards,

Thanks you to for feedbacks! It's very important.
For 2021, It's mostly ready for previewing but waiting for next SDK for fixes. Then I'll make it available, surely it depends how much extra work is required.

Amazing, thanks for your great work!

Sportler wrote: Yes, that's exactly what I meant!

If we are talking for the same thing, I checked with Karl (the guy that works on the standalone on aces) and he said that there is no need to do image conversions in octane due to the spectral nature of the engine.

source

Thanks Tom!

Just installed latest plugin and standalone, same problem.

OctaneRender Enterprise 2020.2.4 (10021600)

CUDA error 702 on device 3: the launch timed out and was terminated
-> failed to wait for event
device 3: path tracing kernel failed
CUDA error 702 on device 1: the launch timed out and was terminated
-> failed to wait for event
device 1: path tracing kernel failed
CUDA error 702 on device 3: the launch timed out and was terminated
-> failed to load symbol data to the device(deep_data)
device 3: failed to upload the deep params
CUDA error 702 on device 1: the launch timed out and was terminated
-> failed to load symbol data to the device(deep_data)
device 1: failed to upload the deep params
CUDA error 702 on device 2: the launch timed out and was terminated
-> failed to load symbol data to the device(deep_data)
device 2: failed to upload the deep params
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to wait for event
device 0: path tracing kernel failed
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to load symbol data to the device(deep_data)
device 0: failed to upload the deep params

RizonParein wrote:Thanks Tom!

Just installed latest plugin and standalone, same problem.

OctaneRender Enterprise 2020.2.4 (10021600)

CUDA error 702 on device 3: the launch timed out and was terminated
-> failed to wait for event
device 3: path tracing kernel failed
CUDA error 702 on device 1: the launch timed out and was terminated
-> failed to wait for event
device 1: path tracing kernel failed
CUDA error 702 on device 3: the launch timed out and was terminated
-> failed to load symbol data to the device(deep_data)
device 3: failed to upload the deep params
CUDA error 702 on device 1: the launch timed out and was terminated
-> failed to load symbol data to the device(deep_data)
device 1: failed to upload the deep params
CUDA error 702 on device 2: the launch timed out and was terminated
-> failed to load symbol data to the device(deep_data)
device 2: failed to upload the deep params
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to wait for event
device 0: path tracing kernel failed
CUDA error 702 on device 0: the launch timed out and was terminated
-> failed to load symbol data to the device(deep_data)
device 0: failed to upload the deep params

Hi RizonParein,

Could you share the driver version as well as the HW you are using?

If you can reproduce this with a scene you can share (or a simplified version of it) please send a PM and will look into it.

Thank you.