OTOY Forums

face_off wrote:I will take a look at this when doing the next release. I suspect that given the architecture of the plugin, it will be difficult to implement this, but I will review it again.

I see. I can understand it's not so easy to change/implements new features in this plugin, but well, I really hope to get this feature!

face_off wrote: On your Cuda 719 error - this was caused by the displacement on the light sabre. Otoy have fixed this bug in the next release of Octane.

This is an awesome news. Thanks a lot!

Do you know the reasons behind this problem ?
Right now I'm starting to use only tif files for the displacements and I didn't run in any trouble so far ... (and the renders looks way more clean)

Do you know the reasons behind this problem ?

There are certain situations where Octane is hanging when rendering displacement maps - and your scene has triggered that situation. Hopefully the next release of Octane is be available shortly, so the problem will be resolved then.

Paul

face_off wrote:

Do you know the reasons behind this problem ?

There are certain situations where Octane is hanging when rendering displacement maps - and your scene has triggered that situation. Hopefully the next release of Octane is be available shortly, so the problem will be resolved then.

Paul

Thank you for this information. I have been having the same issue as AlfaseeD with certain things, and figured it had to be the displacement cause when I took the maps off the scene would render fine. Glad to know this has hopefully been fixed.

I have updated the links at the top of this thread with:

3.3.4.25
- Compiled with Octane 3.03.4
- Fixed issue where the Beauty pass could not be re-selected after selected another render pass

I have spent a huge amount of time trying to implement loading of custom defaults for rendersettings, however a pre-existing bug has prevented this being released in this latest version. If you import a Rendersetting (in any version of the plugin), the Imager settings are fine, however the Kernel settings that were imported are not applied to the UI widgets, and changing any of the Kernel settings does not result in the changes being applied to the Octane scene.

I have also merged the STABLE thread into this thread.

Paul

Hi Paul, thanks for the effort!

However about my crash problems, since I started to use only TIF files for the displacement I never get any crashes !

Did something change about specular materials? I opened a file I was working on yesterday which looked fine, and I downloaded and installed the latest standalone and test release and now the skin is rendering like...gray/black >_>

I switched back to 3.2.0.23 and my skin shader renders fine now. Will do some renders to show what I mean.

Here are the differences I mentioned. All settings are the same for each picture, just the versions of the plugin are different.

Ok I see what has happened. Before if you didn't want absorption you could just leave it at none, but now it HAS to have a color or else...you get the results I was getting.

Ok I see what has happened. Before if you didn't want absorption you could just leave it at none, but now it HAS to have a color or else...you get the results I was getting.

Yes, I found the same - you need an absorption in order to get SSS working.

Paul

face_off wrote:I have updated the links at the top of this thread with:

3.3.4.25
- Compiled with Octane 3.03.4
- Fixed issue where the Beauty pass could not be re-selected after selected another render pass
Paul

Thanks, Paul! Seems to work fine now.