OctaneRender 3 for DAZ Studio [TEST and STABLE]

Forums: OctaneRender 3 for DAZ Studio [TEST and STABLE]
DAZ Studio Integrated Plugin (Integrated Plugin maintained by OTOY)

Moderator: BK

Forum rules
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.

Re: OctaneRender 3 for DAZ Studio [TEST and STABLE]

Postby birdovous » Sat Apr 28, 2018 5:48 am

birdovous Sat Apr 28, 2018 5:48 am
face_off wrote:
Personally I would like to see the OSL texture and LUT support implemented instead of all the toon stuff which for me is pretty useless. However, it is still progress.
I have looked at how to implement OSL textures and LUT support - and unfortunately the current architecture of the DAZStudio plugin makes this quite difficult. So I don't think it is something you will see in the plugin in the near future - sorry.

Paul

Understood. Once can always hope, right? :)
Birdovous
Master: Core i7 2600K, 32GB RAM, 2x EVGA GTX Titan X (SC)
Slave 1: Core i5 4460, 16GB RAM, 2x EVGA GTX 1080 Ti SC2
Slave 2: Core i7 9700K, 64GB RAM, 2x ASUS RTX 2080 Ti
User avatar
birdovous
Licensed Customer
Licensed Customer
 
Posts: 155
Joined: Tue Jul 23, 2013 5:33 pm

Re: OctaneRender 3 for DAZ Studio [TEST and STABLE]

Postby jibbles10 » Sat Apr 28, 2018 7:22 am

jibbles10 Sat Apr 28, 2018 7:22 am
face_off wrote:I have updated the TEST installer at the top of this thread with:

3.8.0.38
- Compiled with Octane 3.08 (see viewtopic.php?f=33&t=63219 for details)
- Added Toon, Toon Ramp and Metallic materials
- Toon shading only works in Camera Light toon lighting mode, and the Toon Ramp is not working correctly, so Toon Shading has limited value at this time
- Added BRDF Model, Anisotropy and Rotation to Glossy and Specular Materials
- OSL Textures have not been implemented
- Custom LUT has not been implemented
- Fixed crash when cancelling an animation which has a small Max Samples setting

If no issues are reported in the next week, I will migrate this to the STABLE build.

Paul


Fantastic work Paul! I have been testing it today and so far it seems fairly stable when rendering and adjusting parameters for stills.
jibbles10
Licensed Customer
Licensed Customer
 
Posts: 49
Joined: Thu Jan 09, 2014 8:43 pm

Re: OctaneRender 3 for DAZ Studio [TEST and STABLE]

Postby OctaneDay » Mon May 07, 2018 8:03 pm

OctaneDay Mon May 07, 2018 8:03 pm
-
Last edited by OctaneDay on Sat Apr 24, 2021 7:36 pm, edited 1 time in total.
OctaneDay
Licensed Customer
Licensed Customer
 
Posts: 1
Joined: Sat Mar 31, 2018 2:24 am

Re: OctaneRender 3 for DAZ Studio [TEST and STABLE]

Postby Witpapier » Thu May 10, 2018 8:24 pm

Witpapier Thu May 10, 2018 8:24 pm
Thanx Big "P" You're the man.!!
RedSpec TGX for Poser / OctaneRender - OUT NOW visit http://redspec-sss.com/
Witpapier
Licensed Customer
Licensed Customer
 
Posts: 366
Joined: Sat Nov 24, 2012 2:13 pm

Re: OctaneRender 3 for DAZ Studio [TEST and STABLE]

Postby rajib » Fri May 11, 2018 5:34 am

rajib Fri May 11, 2018 5:34 am
face_off wrote:
Personally I would like to see the OSL texture and LUT support implemented instead of all the toon stuff which for me is pretty useless. However, it is still progress.
I have looked at how to implement OSL textures and LUT support - and unfortunately the current architecture of the DAZStudio plugin makes this quite difficult. So I don't think it is something you will see in the plugin in the near future - sorry.

Paul


Thanks for the 3.08 build Paul :). Finally got to download it today. About to test with it. Btw. I do hope you have been re-building the plugin from scratch on the side. Otherwise we will always be in this situation where you find it difficult to add features to the existing plugin.
Windows 10 Pro i9-9980XE 128GB RAM|4 x Titan RTX
Houdini 18.5(2020.2.1.2)|Cinema C4D R26|Daz Studio Pro 4.21.0.5(Octane 2021.1.6.83)
NVIDIA 460.89 Studio Standard
User avatar
rajib
Licensed Customer
Licensed Customer
 
Posts: 401
Joined: Sun Sep 28, 2014 4:57 am

Re: OctaneRender 3 for DAZ Studio [TEST and STABLE]

Postby rajib » Fri May 11, 2018 4:18 pm

rajib Fri May 11, 2018 4:18 pm
HI Paul,

I have been testing the 3.08 build. Getting render failures on the scene which rendered without problem before (with 3.07). This generally seem to happen when I have changing textures in the NGE while the render is going on. I have 128GB RAM in my render PC and I have allocated 55488MB of Out-of-Core Memory and 1024MB Ooc GPU Headroom.

Below is the log that I see when the render fails:

22:57:21.548: +++++ Plugin running.
00:08:46.728: CUDA error 719 on device 2: unspecified launch failure
00:08:46.729: CUDA error 719 on device 1: unspecified launch failure
00:08:46.731: -> kernel execution failed(kernel25)
00:08:46.732: -> kernel execution failed(kernel25)
00:08:46.733: CUDA error 719 on device 2: unspecified launch failure
00:08:46.734: CUDA error 719 on device 1: unspecified launch failure
00:08:46.735: -> failed to launch kernel(kernel34)
00:08:46.737: -> failed to launch kernel(kernel34)
00:08:46.738: device 2: path tracing kernel failed
00:08:46.740: device 1: path tracing kernel failed
00:08:46.740: Render engine failure occured! (WARNING)
00:08:46.742: CUDA error 719 on device 0: unspecified launch failure
00:08:46.743: -> kernel execution failed(kernel25)
00:08:46.744: CUDA error 719 on device 0: unspecified launch failure
00:08:46.745: -> failed to launch kernel(kernel34)
00:08:46.746: device 0: path tracing kernel failed
00:08:46.771: Failed to free page-locked memory
00:08:46.772: Failed to free page-locked memory
:
:
00:08:47.053: Failed to free page-locked memory
00:08:47.054: Failed to free page-locked memory
00:08:47.055: Failed to free page-locked memory
00:08:47.056: Failed to free page-locked memory
00:08:47.058: Failed to free page-locked memory
00:08:47.059: Failed to free page-locked memory
00:08:47.060: Failed to free page-locked memory
00:08:47.061: Failed to free page-locked memory
00:08:47.062: Failed to free page-locked memory
00:08:47.063: Failed to free page-locked memory
00:08:47.064: Failed to free page-locked memory
00:08:47.065: Failed to free page-locked memory
00:08:47.067: Failed to free page-locked memory
00:08:47.068: Failed to free page-locked memory
00:08:47.069: Failed to free page-locked memory
00:08:47.070: Failed to free page-locked memory
00:08:47.071: Failed to free page-locked memory
00:08:47.072: Failed to free page-locked memory
00:08:47.073: Failed to free page-locked memory
00:08:47.075: Failed to free page-locked memory
00:08:47.076: CUDA error 719 on device 3: unspecified launch failure
00:08:47.077: -> could not get memory info
00:08:47.078: Failed to free page-locked memory
00:08:47.079: CUDA error 719 on device 3: unspecified launch failure
00:08:47.080: -> could not get memory info
00:08:47.082: Failed to allocate page-locked memory
00:08:47.083: CUDA error 719 on device 3: unspecified launch failure
00:08:47.084: -> failed to copy memory to device.
00:08:47.085: device 3: failed to upload data texture 23 of context 1
00:08:47.086: CUDA error 719 on device 3: unspecified launch failure
00:08:47.087: -> failed to deallocate device memory
00:08:47.088: CUDA error 719 on device 3: unspecified launch failure
00:08:47.089: -> could not get memory info
00:08:47.121: CUDA error 719 on device 3: unspecified launch failure
00:08:47.121: -> failed to set texture format(__data24__)
00:08:47.121: CUDA error 719 on device 3: unspecified launch failure
00:08:47.121: -> failed to set texture format(__data26__)
00:08:47.121: CUDA error 719 on device 3: unspecified launch failure
00:08:47.121: -> failed to set texture format(__data29__)
00:08:47.121: CUDA error 719 on device 3: unspecified launch failure
00:08:47.121: -> failed to deallocate device memory
00:08:47.122: CUDA error 719 on device 3: unspecified launch failure
00:08:47.122: -> could not get memory info
00:08:47.122: CUDA error 719 on device 3: unspecified launch failure
00:08:47.122: -> failed to deallocate device memory
00:08:47.122: CUDA error 719 on device 3: unspecified launch failure
00:08:47.122: -> could not get memory info
00:08:47.122: Failed to free page-locked memory
00:08:48.726: CUDA error 719 on device 3: unspecified launch failure
00:08:48.726: -> failed to unload module
00:08:48.726: CUDA error 719 on device 3: unspecified launch failure
00:08:48.726: -> failed to create link
00:08:48.726: device 3: failed to create OSL compile context:
00:08:48.726: device 3: failed to compile module 1
00:08:49.739: Render engine failure occured! (WARNING)
00:08:52.739: Render engine failure occured! (WARNING)
00:09:02.231: CUDA error 719 on device 3: unspecified launch failure
00:09:02.231: -> failed to load symbol data to the device(const11)
00:09:02.231: device 3: failed to upload imager params
00:09:02.322: 3 render engine failures within a minute - giving up! (CRITICAL)

Regards,
Rajib
Windows 10 Pro i9-9980XE 128GB RAM|4 x Titan RTX
Houdini 18.5(2020.2.1.2)|Cinema C4D R26|Daz Studio Pro 4.21.0.5(Octane 2021.1.6.83)
NVIDIA 460.89 Studio Standard
User avatar
rajib
Licensed Customer
Licensed Customer
 
Posts: 401
Joined: Sun Sep 28, 2014 4:57 am

Re: OctaneRender 3 for DAZ Studio [TEST and STABLE]

Postby rajib » Fri May 11, 2018 4:49 pm

rajib Fri May 11, 2018 4:49 pm
Hi Paul,

I would like report another issue with 3.08 build. Like I mentioned in my previous post I have 128GB of RAM on my render PC and when I start Daz Studio and go to the Octane -> System tab, using the Out-of-Core Memory slider I cannot allocate more than 6336 MB of memory. And I cannot increase the allocation until I start to render a scene and then it allows me to allocate more. But the problem is if I load a heavy scene, I am unable to go beyond 6336 MB of Out-of-Core memory and the heavy scene render immediately fails stating not enough Out-of-Core memory. Increasing Out-of-Core memory at that point does not work as after getting the failure message, I need to close and re-open Daz Studio. To work around this I need to load a lite scene, render it, and then set the Out-Of-Core memory and then load the heavy scene. But this is not ideal way of working. Also even after setting the Out-of-Core memory and saving the scene, when I reopen the scene the Out-of-Core memory setting does not retain what was set during the last save and goes back to default.

We should be able to set Out-of-Core memory to more than 6336 MB if the system we are running Octane on has more RAM available (without having to trigger a render first). Also when the scene is saved and reopened, the Out-of-Core setting should be set as per what was last saved. Or can a setting under Octane -> Preference can be put where we can specify upfront how much of Out-of-Core memory we want to allocate ? The plugin can check the available system RAM to set the upper limit.

Max_Out-of-Core_Before_Render.png
Max 6336MB can be selected before render


Max_Out-of-Core_After_Render.png
Allows to select more after the render is triggered


Hope you can fix this.

Regards,
Rajib
Windows 10 Pro i9-9980XE 128GB RAM|4 x Titan RTX
Houdini 18.5(2020.2.1.2)|Cinema C4D R26|Daz Studio Pro 4.21.0.5(Octane 2021.1.6.83)
NVIDIA 460.89 Studio Standard
User avatar
rajib
Licensed Customer
Licensed Customer
 
Posts: 401
Joined: Sun Sep 28, 2014 4:57 am

Re: OctaneRender 3 for DAZ Studio [TEST and STABLE]

Postby rajib » Fri May 11, 2018 5:40 pm

rajib Fri May 11, 2018 5:40 pm
Hi Paul,

Another issue. This is there in 3.07.x as well as the 3.08 build. If I use a TIFF image as e.g. a diffuse texture map / transparency map (RGBA Image), after saving the scene and closing and then reopening it, the diffuse texture map will be empty. The plugin is either not saving the TIFF texture map links or is not reading them back while opening the scene. Can you please fix this too ?

Regards,
Rajib
Windows 10 Pro i9-9980XE 128GB RAM|4 x Titan RTX
Houdini 18.5(2020.2.1.2)|Cinema C4D R26|Daz Studio Pro 4.21.0.5(Octane 2021.1.6.83)
NVIDIA 460.89 Studio Standard
User avatar
rajib
Licensed Customer
Licensed Customer
 
Posts: 401
Joined: Sun Sep 28, 2014 4:57 am

Re: OctaneRender 3 for DAZ Studio [TEST and STABLE]

Postby face_off » Sat May 12, 2018 9:03 am

face_off Sat May 12, 2018 9:03 am
00:08:47.083: CUDA error 719 on device 3: unspecified launch failure
Which Nvidia driver version have you got installed pls? Have you tried the latest (397?).

Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
User avatar
face_off
Octane Plugin Developer
Octane Plugin Developer
 
Posts: 15471
Joined: Fri May 25, 2012 10:52 am
Location: Adelaide, Australia

Re: OctaneRender 3 for DAZ Studio [TEST and STABLE]

Postby TRRazor » Wed May 16, 2018 1:49 pm

TRRazor Wed May 16, 2018 1:49 pm
@rajib this problem has been in every OR for DS-plug-in-version since the plug-in launched.
There seems to be some lock that prevents one from setting the OOC-memory higher than the 6336 MB of RAM BEFORE the OctaneRender viewport hasn't been opened at least once.

That seems to remove the lock and gives access to the full remaining amount of RAM on your system.
W10 64 bit | i7 3770K | MSI Geforce RTX 2080 (8GB) + GTX Titan Black (6GB) | 32 GB DDR3 RAM
User avatar
TRRazor
Licensed Customer
Licensed Customer
 
Posts: 684
Joined: Sun Nov 03, 2013 10:21 am
PreviousNext

Return to DAZ Studio


Who is online

Users browsing this forum: Google [Bot] and 7 guests

Thu Mar 28, 2024 6:00 pm [ UTC ]