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

[Laticis]

Paul,

Why has the Smart Unfold been removed ??? Can you not disable features that we are so dependent on. Yes it is buggy but we still used it. Enable it back. it is not there even in the 2019.1.5.51. I can't roll back to 2020.1 earlier version. But at least managed to rollback back to 2109.1.5.49 to get it back.

Regards,
Rajib

LOL I just went to use DS / Octane for the first time in a while to run a quick skin test and thought I would upgrade first. Automatically during the process went to my go-to smart unfold, knowing full well it isn't perfect but still handy and faster, but to no avail

Also found, after Auto material ( inspected nodes in NGE ) then < Change Material Type for: to Glossy Material < Inspected under NGE and all the unused Nodes are still floating around, looks very messy.

[rajib]

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

2020.1.0.51
- Removed the setting of the Windows TDR Deley setting when the plugin starts up

Thanks

Paul

Hi Paul,

May I know if the code was commented out for the TDR Delay or some values reset to some defaults ? I have been experiencing VIDEO_TDR_DELAY BSOD (system crashes) since I had installed that release. I have never experienced that ever before. I have tried to re-install my graphics driver after running DDU driver removal in safe mode. But on and off am still facing it. I have not been able to go back to the earlier releases of 2020 as they give an error saying not supported during activation. I have finally uninstalled the 2020.x version. Also on the 2019.1.x side I have downgraded to before the TDR changes.

If you are doing some changes to the Windows registry, can you let us know what key and value is being / was changed / added / removed ? .

Regards,
Rajib

Hi Paul,

My VIDEO_TDR _DELAY BSOD might not be related to this. Looks like one of my cards was having problems. Unfortunately it kinda happened after the update I installed where the TDR was removed so it led me to assume it might have been related.

Mikmod did inform me that he had reported it as a bug as the TDR values manually set were getting overwritten. Maybe you can implement the logic in a slightly different way. Read the registry value if not found or less than 10, set it to 10. If the value is already greater than 10, leave it as is. That way, on PCs where it is the default 2 seconds and can cause BSOD, the higher 10 second value will be handy and those of us who have set it to higher won't have our values overwritten.

Regards,
Rajib

[face_off]

Maybe you can implement the logic in a slightly different way. Read the registry value if not found or less than 10, set it to 10. If the value is already greater than 10, leave it as is. That way, on PCs where it is the default 2 seconds and can cause BSOD, the higher 10 second value will be handy and those of us who have set it to higher won't have our values overwritten.

The plugin will no longer be setting the TDR Delay seettings in the registry. If you want to set these settings to the OTOY recommended values, install Octane Standalone (as the Standalone MSI installer sets these values).

Paul

[face_off]

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

2020.1.0.54
- Compiled with Octane 2020.1 RC3

Thanks

Paul

[Kanne]

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

2020.1.0.54
- Compiled with Octane 2020.1 RC3

Thanks

Paul

Thanks for the update paul, solves many issues regarding universal materials and random walk.

Lately i'am experiancing a lot of freezes of the octane viewer when adjusting materials or adjusting morphs. Not sure where it inheriats from, or what exactly it's causing it, but i will investigate further. It could have started when i started using a higher SubD level. Therefor, it maybe a ram, vram or ooc issue. If i have some facts i would approach you again, or the general forum, depending on what i find.

[Kanne]

Getting this a lot latly:

Code: Select all

2020-04-18 11:02:52.788	8276	b2020.1.0.53	++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2020-04-18 11:02:52.797	8276	b2020.1.0.53	+++++ Plugin started.


2020-04-18 11:02:59.506	8276	b2020.1.0.53	+++++ Plugin running.

2020-04-18 11:06:26.165	8276	b2020.1.0.53	Tried to access null node
2020-04-18 11:06:26.174	8276	b2020.1.0.53	Tried to access pin via an invalid ID P_FILM_SETTINGS (311)
2020-04-18 11:06:26.181	8276	b2020.1.0.53	Tried to access null node pin
2020-04-18 11:06:26.189	8276	b2020.1.0.53	Tried to access null node
2020-04-18 11:06:26.198	8276	b2020.1.0.53	Tried to access pin via an invalid ID P_FILM_SETTINGS (311)
2020-04-18 11:06:26.206	8276	b2020.1.0.53	Tried to access null node pin
2020-04-18 11:31:42.782	11856	b2020.1.0.53	CUDA error 2 on device 1: out of memory
2020-04-18 11:31:42.788	11856	b2020.1.0.53	  -> failed to allocate device memory
2020-04-18 11:31:42.875	11856	b2020.1.0.53	CUDA error 700 on device 1: an illegal memory access was encountered
2020-04-18 11:31:42.884	11856	b2020.1.0.53	  -> kernel synchronization failed
2020-04-18 11:31:42.892	11856	b2020.1.0.53	CUDA error 700 on device 1: an illegal memory access was encountered
2020-04-18 11:31:42.902	11856	b2020.1.0.53	  -> failed to deallocate device memory
2020-04-18 11:31:42.906	11856	b2020.1.0.53	CUDA error 700 on device 1: an illegal memory access was encountered
2020-04-18 11:31:42.910	11856	b2020.1.0.53	  -> could not get memory info
2020-04-18 11:31:42.915	11856	b2020.1.0.53	CUDA error 700 on device 1: an illegal memory access was encountered
2020-04-18 11:31:42.918	11856	b2020.1.0.53	  -> failed to deallocate device memory
2020-04-18 11:31:42.922	12720	b2020.1.0.53	CUDA error 700 on device 0: an illegal memory access was encountered
<!-- Repeating -->
2020-04-18 11:31:43.243	12720	b2020.1.0.53	CUDA error 700 on device 0: an illegal memory access was encountered
2020-04-18 11:31:43.246	12720	b2020.1.0.53	  -> could not get memory info
2020-04-18 11:31:43.436	8276	b2020.1.0.53	Render engine failure occured! (WARNING)
2020-04-18 11:31:46.438	8276	b2020.1.0.53	Render engine failure occured! (WARNING)

- Using latest build of plugin
- Nvidea Treiber: 445.87
- Win 10
- 2* RTX 2070 (RTX acceleration enabled)
- 64GB RAM (Setup: 20GB OOC, 300MB Headroom)

Could this be plugin related or core engine related?

[face_off]

2020-04-18 11:31:42.782 11856 b2020.1.0.53 CUDA error 2 on device 1: out of memory

Looks like you are running out of VRAM.

2020-04-18 11:06:26.174 8276 b2020.1.0.53 Tried to access pin via an invalid ID P_FILM_SETTINGS (311)

This looks like an error associated with opening a very old scene - was that the case?

Paul

[RGUS]

Installed:
For users with a Prime/Free Tier license
- OctaneRender for DAZ Studio 2020.1.0.54 - updated 23-Mar-2020

But DAZ Studio reports version xxxx.53

[face_off]

Installed:
For users with a Prime/Free Tier license
- OctaneRender for DAZ Studio 2020.1.0.54 - updated 23-Mar-2020

But DAZ Studio reports version xxxx.53

I have updated the installers at the top of this thread to correct the wrong version number.

Thanks

Paul

[mikmod]

I noticed something weird with emissive material. Preview render shows bright light, and final render - totally no light at all... I used pathtracing. I also used that kind of emissive material. By the way, wattage if that light seems way out of range, in the preview this is about 6W bulb. But even 100W emission won't show anything on final render.

Second thing is the weird camera resolution behavior - where did Octane plugin get this 4 x 4 pixels resolution from? It's really hard to workaround (playing around with every parameter I outlined on screenshot), and it's usually coming back after a while, like just now...
Resolution problem seems to apply only to preview rendering, final rendering seems to take one of these camera parameters and use it. It seems to happen, when there's either camera with its own resolution, or because I first remade a couple of shaders in a scene (emissive surfaces aren't converted from Iray at all and there's still glass-water-like conversion issues, so that needed to be fixed by hand) and after that I pressed "Open viewport" button.