Cinema 4D version 2019.1.1-R3 (Stable) 09.10.2019 Tweet

[bloomis2]

Hello! I'm having scaling issues with Octane for the first time ever, and it happened right when I installed this 2019.1.1 version + C4D R21. It seems like it's unable to work with windows 150% scaling of my 4K monitor. Even the buttons seem pixelated. Windows is updated, Nvidia drivers too (I tried both Studio and Game-ready drivers). Is there something I'm missing? I'm sorry, I've been looking everywhere before posting here.

[aoktar]

Hello! I'm having scaling issues with Octane for the first time ever, and it happened right when I installed this 2019.1.1 version + C4D R21. It seems like it's unable to work with windows 150% scaling of my 4K monitor. Even the buttons seem pixelated. Windows is updated, Nvidia drivers too (I tried both Studio and Game-ready drivers). Is there something I'm missing? I'm sorry, I've been looking everywhere before posting here.

Sorry! What you do? Are you scaling C4D from nvidia control panel? We don't have any highDPI support for 4k monitors

[bloomis2]

I'm sorry, English isn't my first language I'm not scaling anything, or touching any parameter in Nvidia or C4D. I just have windows display settings scaling the resolution at 150%, so that everything isn't super small on my computer. I had this for years with no troubles, even with Octane. But then with R21 and this octane version, I get this issue. I know you don't have any High DPI version of Octane, and it didn't matter until this happened. If it was only the UI it wouldn't matter. But the image is affected too.

[aoktar]

I'm sorry, English isn't my first language I'm not scaling anything, or touching any parameter in Nvidia or C4D. I just have windows display settings scaling the resolution at 150%, so that everything isn't super small on my computer. I had this for years with no troubles, even with Octane. But then with R21 and this octane version, I get this issue. I know you don't have any High DPI version of Octane, and it didn't matter until this happened. If it was only the UI it wouldn't matter. But the image is affected too.

So it's not an issue with related Octane. You need a customizable Octane gui/fonts for 4K

[Kalua]

New build available with a few fixes, enjoy it!

So far is working great!
One general question: Does the Live DB save Octane Composite/Blend shaders correctly? I ask this because I was downloading some of my older assets and they seems to have lost 99% of it's settings.
Cheers!

[aoktar]

New build available with a few fixes, enjoy it!

So far is working great!
One general question: Does the Live DB save Octane Composite/Blend shaders correctly? I ask this because I was downloading some of my older assets and they seems to have lost 99% of it's settings.
Cheers!

I'm working on livedb part right now! You may be correct, let me test it after completing demo builds.

[Kalua]

New build available with a few fixes, enjoy it!

So far is working great!
One general question: Does the Live DB save Octane Composite/Blend shaders correctly? I ask this because I was downloading some of my older assets and they seems to have lost 99% of it's settings.
Cheers!

I'm working on livedb part right now! You may be correct, let me test it after completing demo builds.

Thank you, Aoktar! Great news!

I have been reshading some assets with some better practices and I noticed this bug that persits since V2. It's not critical but I let you know just in case.
So here you go:
A MIX shader with 2 materials that use same textures for diffuse, bump, etc (all duplicated). I decided to unify the textures in order to make it more efficient. Here is when this small bug takes place:
The renoded shader doesn't recognize the new node in it's preview window - although the final MIX preview works fine and the Live view renders just fine. To fix it you must create a new node and relink both materials inputs.
Like I said before, it's not critical but it comes a long way it persists - even though I don't use MIX shaders anymore ,with some exceptions.
Thanks for the great work!

[bloomis2]

I'm sorry, English isn't my first language I'm not scaling anything, or touching any parameter in Nvidia or C4D. I just have windows display settings scaling the resolution at 150%, so that everything isn't super small on my computer. I had this for years with no troubles, even with Octane. But then with R21 and this octane version, I get this issue. I know you don't have any High DPI version of Octane, and it didn't matter until this happened. If it was only the UI it wouldn't matter. But the image is affected too.

So it's not an issue with related Octane. You need a customizable Octane gui/fonts for 4K

No, I'm not talking about the gui / fonts. I'm talking about the image in the live viewer. It is pixelated, even when the resolution is locked.

Pixelated live viewer

It should be like this : (image rendered)

Clean render

The image is 1280x720. I never had this issue before, in R20, so maybe it is due to the new C4D 4K resolution. There is a conflict there.

[CrusaderArts]

Hi,

Seems like Toon Materials have a problem with this release.

I keep getting these errors when making a toon material:

Code: Select all

Started logging on 08.10.19 13:17:07

OctaneRender Enterprise 2019.1.1 (6000101)

CUDA error 700 on device 0: an illegal memory access was encountered
  -> kernel synchronization failed
device 0: preview failed
CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to deallocate device memory
CUDA error 700 on device 0: an illegal memory access was encountered
  -> could not get memory info
CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to deallocate device memory
CUDA error 700 on device 0: an illegal memory access was encountered
  -> could not get memory info
CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to deallocate device memory
CUDA error 700 on device 0: an illegal memory access was encountered
  -> could not get memory info
CUDA error 700 on device 1: an illegal memory access was encountered
  -> failed to unload module
CUDA error 700 on device 1: an illegal memory access was encountered
  -> failed to create link

Is this a known issue?

[frankmci]

I think I had a conversation with Ahmet a few years ago about a related issue. As I recall, he told me it is an internal limitation with the way C4D thinks about materials and their sub-components. Essentially, C4D assumes each node in the shader only has one "true" parent material and makes some assumptions and shortcuts based on that. While you can connect nodes to multiple "parent" materials, it's often only the first material that will be properly updated when a shared child node is changed. Things generally still render properly, but you may not get the feedback you expect without forcing a refresh.

Maybe once Octane's and C4D's new node based shaders are more tightly integrated, this issue can be resolved.