OctaneRender 3 for DAZ Studio [TEST and STABLE] [OBSOLETE]

[face_off]

Paul, any roadmap for when the Daz plugin might have the functionally implemented 'Visible Environment' like you were able to give the Poser, Modo, and Rhinoceros plugins? (IE next couple months, later 2017)

I'm sorry - but I'm not sure when this will happen. The architecture of the DAZStudio plugin makes it hard to implement this feature, so it is something which will require a lot of effort to code, so I have put it on the back-burner.

I've found some strange problems with "3.6.2.32 PRE-RELEASE"; maybe it's because I'm using the redspec-shaders on my G3 but when I try to re-render a scene (HDRI, pathtracing) there are some strange/weird colours in my renderings so I've re-installed the old version immediately. Tried a few old scenes without any changes. The renderings looked like 8-bit BMPs, there were no smooth but very hard shadows (contrast). Am I the only one having problems like these?
After re-installing 3_5_3_31 octane is running without any problems.

This is a know issue with Octane 3.06 TEST 2 and 3, and is caused by having a Float Texture with a value of 0 plugged into a Normal pin. I am hopeful that it will be resolved in the next Octane release.

Paul

[TRRazor]

Okay, I see what you're talking about. The blocky shadows are appearing when you are trying to use the shaders with the "Normal Map" preset on a character, that doesn't have Normal Map applied to her.
Please always make sure to check in the DAZ Studio surfaces tab BEFORE applying RedSpec shaders, if t he character has any Normal Maps applied or not. if not, please use the Bump Maps only preset, this will solve the problem.

This is NOT a problem of the most recent test release but has been something which has been present in any of the previous releases of the plug-in as well.

[face_off]

Following is a pre-release built with Octane 3.06 TEST 4. This version will hopefully resolve the Normal mapping issue people have had with the previous 3.06 builds.

3.6.3.32 pre-release
- Compiled with Octane 3.06 TEST 4 (includes Adaptive Sampling, new Bokeh pins, new Pano Camera DOF pins, new Add/Subtract/Comparison/Triplanar texture nodes, and Normal and Displacement mapping enhancements
- Renamed the Camera->OctaneRender->Bokeh sharpness parameter to Aperture Edge
- Added Camera Visibility to the OctaneRender parameters group (for meshes)

https://render.otoy.com/customerdownloa ... _Win64.exe

Paul

[Laticis]

Excellent...thank you for the update, look forward to testing.

[Leonides02]

Oooh, Adaptive Sampling. Thanks, Paul!

[Laticis]

Hi Paul,

I have been having some major issues with my PC for a while now and it all started after a Windows 10 Update and a Nvidia Driver Update
Since then been having heaps of BSOD mainly while using DAZ with Iray. Been sending them log files but nothing really showing up. Octane was running 90 % of the time.
I then updated Nidia driver when a new release came out and things went great for a week till a new Win10 System Update.

That's the long story...short story.

Today I installed DS Octane 3_6_3_32_Win64 + OctaneRender_3_05_3_win + 378.92-desktop-win10-64bit-international-whql and I got instatnt freeze with DS Octane and a Crash with Octane Standalone.

I am running 2 x Titan Z ( Not in SLI )

After researching I found this: http://www.pcauthority.com.au/News/4178 ... iasco.aspx

So I ran DDU to clean the system, installed an old NVidia Driver 355.60-desktop-win10-64bit-international-whql.
Octane Standlaone runs fine now no crashing bet when I run DS / Octane
Octane Render Error / No Supported GPU device(s) found / Ocatane Render for DAZ Studio can't be activated.

I have disabled the Octane Plugin and open DS with Iray no probs at all.

Any suggestions or thoughts?

EDIT: Iray not rendering either so issue is certainly driver related.

Cheers Ady

[Leonides02]

Hi Paul,

I have been having some major issues with my PC for a while now and it all started after a Windows 10 Update and a Nvidia Driver Update
Since then been having heaps of BSOD mainly while using DAZ with Iray. Been sending them log files but nothing really showing up. Octane was running 90 % of the time.
I then updated Nidia driver when a new release came out and things went great for a week till a new Win10 System Update.

That's the long story...short story.

Today I installed DS Octane 3_6_3_32_Win64 + OctaneRender_3_05_3_win + 378.92-desktop-win10-64bit-international-whql and I got instatnt freeze with DS Octane and a Crash with Octane Standalone.

I am running 2 x Titan Z ( Not in SLI )

After researching I found this: http://www.pcauthority.com.au/News/4178 ... iasco.aspx

So I ran DDU to clean the system, installed an old NVidia Driver 355.60-desktop-win10-64bit-international-whql.
Octane Standlaone runs fine now no crashing bet when I run DS / Octane
Octane Render Error / No Supported GPU device(s) found / Ocatane Render for DAZ Studio can't be activated.

I have disabled the Octane Plugin and open DS with Iray no probs at all.

Any suggestions or thoughts?

EDIT: Iray not rendering either so issue is certainly driver related.

Cheers Ady

I'm afraid I'm no help, but thanks for the info. I have a new PC on the way. I'd better avoid those automatic updates for awhile.

[Laticis]

I'm afraid I'm no help, but thanks for the info. I have a new PC on the way. I'd better avoid those automatic updates for awhile.

It could just be my PC, more so related to the Titan Z's part that's what sucks, I just can't find the root cause, only crashes.
Originally I thought it was the DAZ Studio update.

Installed 378.66-desktop-win10-64bit-international - Iray is now working but instant BSOD when opening up Octane standalone.

This is the error: VIDEO-TDR-FAILURE (nvlddmkm.sys)

[rajib]

Following is a pre-release built with Octane 3.06 TEST 4. This version will hopefully resolve the Normal mapping issue people have had with the previous 3.06 builds.

3.6.3.32 pre-release
- Compiled with Octane 3.06 TEST 4 (includes Adaptive Sampling, new Bokeh pins, new Pano Camera DOF pins, new Add/Subtract/Comparison/Triplanar texture nodes, and Normal and Displacement mapping enhancements
- Renamed the Camera->OctaneRender->Bokeh sharpness parameter to Aperture Edge
- Added Camera Visibility to the OctaneRender parameters group (for meshes)

https://render.otoy.com/customerdownloa ... _Win64.exe

Paul

Thanks Paul. Will try this out. I was having the issue with the normal mapping with the previous one.

[Notiusweb]

I'm afraid I'm no help, but thanks for the info. I have a new PC on the way. I'd better avoid those automatic updates for awhile.

It could just be my PC, more so related to the Titan Z's part that's what sucks, I just can't find the root cause, only crashes.
Originally I thought it was the DAZ Studio update.

Installed 378.66-desktop-win10-64bit-international - Iray is now working but instant BSOD when opening up Octane standalone.

This is the error: VIDEO-TDR-FAILURE (nvlddmkm.sys)

We should probably touch base with developer of Main build, I have Titan Z and experienced crashes with latest version of Octane and latest Nvidia drivers. Once I rolled back to 372.90, no crashes, but anything after crashes BSOD on Daz with OcDS plugin and standalone. I am using Win 7 and only had the crashing when I had my rig going with all 6 Titan Z cards powered on (If I had 3, for example, no issue...and any Titan X's aren't a problem either. And it happens at app startup). But the fact that it works with some drivers and not others tells me that the CUDA 8 implementation is involved somehow (think it came after 372.90.) Have you touched base with Abstrax in the main standalone build forum?