OTOY Forums

aoktar wrote:Hi,
I've updated builds as 3.08-test6.1. There's some fixes mostly for uber material and osl interface.

thanks for the accelerated development!

aoktar wrote:Hi,
I've updated builds as 3.08-test6.1. There's some fixes mostly for uber material and osl interface.

Thanks a lot, Ahmet!
Live Viewer shows version as 3.08-6est6.0 - is that correct or should it be a different version number?

Goldorak wrote:Test releases aren’t for production, we’re using these releases to help quickly iron out bugs so all uses get a stable release ASAP this month. You will soon have a new subscription option for up to 20 GPUs.

Woot! Btw now there is only the 2 gpu subscription right? This new 20 can be used as node? thanks a lot

ps. Thanks Ahmet for the updates! keep em rolling!

Hey Ahmet, fantastic work on this update! I just wanted to let you know about an issue I ran into with 3.08-test6

I recently updated my graphics driver through Nvidia to version 388.59 (December 7, 2017).
After having done this, the C4D plugin for Octane would render fine in the live viewer but in the picture viewer it would hang on a black screen until it froze my machine and BSOD with DPC Watchdog Violation error.
This happened consistently. I tried it about five times. Each time I tried disabling/switching gpus, changing render resolution, etc. It kept happening. If it didn't lock up and BSOD, which rarely occurred, it would freeze C4D and I would have to end the process and relaunch to try again, which would usually lead back to lockup and BSOD.

The only thing that solved it for me was reinstalling the previous graphics driver: 388.43 (November 30, 2017). So, I imagine there’s something with the new driver that’s causing an issue.
For anyone else experiencing this, I would suggest grabbing the previous graphics driver as a quick fix. I don't know if 3.08test6.1 will fix this... I don't want to keep having to reinstall drivers.
So I'll try out 6.1 but I'll hang out on the previous graphics driver. It's working at the moment.

My scene consisted of C4D hair with glossy shader and some other elements with toon shaders applied, with both area and toon lighting in the scene, if that could contribute to any errors.
Currently, the same scene is working fine with the older driver.

My rig specs are in my signature. Hopefully, no one else is experiencing this issue.
Let me know if there's any other info I can supply regarding this issue.

Again, fantastic updates, Ahmet, I'm loving the toon shader and other new features. Thanks for all your hard work!

UPDATE:
Looks like I'm still running into crashes

Hiya!

I have noticed an issue when plugging in a texture into a gradient node before it goes into bump. For some reason it makes all the white values of the bump map turn the material black:
I noticed that if I move the far right gradient node to the left a little bit it seems to correct the issue so it's not that big a deal but thought it worth reporting. For reference, my material should look like this (it's only an example - don't judge me ):
While on the subject, in some other engines, I can very easily control the amount of bump being applied and also the depth by using a curve ramp like this:
I find this to be a much more elegant solution for controlling texture luma values as using a gradient is a bit of a nightmare trying to get it right. Is there any chance we can get something like this into Octane as it would be so much nicer to be able to dial in proper values as well as being able to control the actual response of the curves with bezier points. I know I've asked about this in the past but it's something I'd personally really appreciate as a new feature

Also I've noticed that in the new Uber Shader (which is AMAZING by the way!), that I can't control specular colour and intensity seperately. It seems that there is only one input for specular wheras it would be nice to have a specular colour value and then a separate intensity input for a texture map or float value etc like with the regular Octane material.

Loving the latest release anyway - toon shader is super fun, Uber Shader is amazing and I'm so happy that I now have GGX and Beckman. You've really knocked it out the park so far with 3.08!

Thanks

zeigg wrote:Hey Ahmet, fantastic work on this update! I just wanted to let you know about an issue I ran into with 3.08-test6

I recently updated my graphics driver through Nvidia to version 388.59 (December 7, 2017).
After having done this, the C4D plugin for Octane would render fine in the live viewer but in the picture viewer it would hang on a black screen until it froze my machine and BSOD with DPC Watchdog Violation error.
This happened consistently. I tried it about five times. Each time I tried disabling/switching gpus, changing render resolution, etc. It kept happening. If it didn't lock up and BSOD, which rarely occurred, it would freeze C4D and I would have to end the process and relaunch to try again, which would usually lead back to lockup and BSOD.

The only thing that solved it for me was reinstalling the previous graphics driver: 388.43 (November 30, 2017). So, I imagine there’s something with the new driver that’s causing an issue.
For anyone else experiencing this, I would suggest grabbing the previous graphics driver as a quick fix. I don't know if 3.08test6.1 will fix this... I don't want to keep having to reinstall drivers.
So I'll try out 6.1 but I'll hang out on the previous graphics driver. It's working at the moment.

My scene consisted of C4D hair with glossy shader and some other elements with toon shaders applied, with both area and toon lighting in the scene, if that could contribute to any errors.
Currently, the same scene is working fine with the older driver.

My rig specs are in my signature. Hopefully, no one else is experiencing this issue.
Let me know if there's any other info I can supply regarding this issue.

Again, fantastic updates, Ahmet, I'm loving the toon shader and other new features. Thanks for all your hard work!

UPDATE:
Looks like I'm still running into crashes

Other System Testing.....

R19 + Nvidia Driver 388.13 + Octane 3.08 T6.1

error : Unable to load library 'nvptxJitCompiler.dll'
CUDA error 221 on device 1: PTX JIT compiler library not found
-> failed to create link
device 1: failed to create OSL compile context:
error : Unable to load library 'nvptxJitCompiler.dll'


R18 + Nvidia Driver 388.13 + Octane 3.08 T6.1
OK...........

Since updating to 3.08-test6.1 from 3.07 R2, I've noticed that shaders using the triplanar mapping nodes have slowed down dramatically (from 2.5 minutes a frame to 8 minutes a frame, with no change to the shader other than verisons).

I've isolated the slowdown to triplanar, mainly because when I change projection types and remove the nodes, speeds are as expected. I've tried rebuilding shaders and I've still had the slowdown.

Thanks for development.

-Alex

Ahmet,

3.07 and 3.08 don't play well with the OVDMmesher in XP4 (or vice versa). If the Octance C4D plugin isn't present all is fine. With the Octane plugin installed under OSX and R19, OVDBmesher causes a hard crash with a machine reset.

There's a lot of blaming on Octance in R19 under OSX... Are you aware of the problem?

fpajonk wrote:Ahmet,

3.07 and 3.08 don't play well with the OVDMmesher in XP4 (or vice versa). If the Octance C4D plugin isn't present all is fine. With the Octane plugin installed under OSX and R19, OVDBmesher causes a hard crash with a machine reset.

There's a lot of blaming on Octance in R19 under OSX... Are you aware of the problem?

What about? About problems with OVDMmesher? What's that?

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 !