OTOY Forums

Win7
32GB RAM
2x GTX Titan
Driver: 358.5
DS 4.8
OcDS 3.0.0.6
Turning on any of the info passes under Render Passes in the viewport seems to crash/stop renderer from working. Their "tabs" are also greyed out and unclickable, beauty and light passes seem to be working fine.
I've used both wireframe and AO in the past and they worked fine.
To get rendering working again I have to either start a new scene in DS or restart DS.
I also got the following errors:

Turning on wireframe: Turning off wireframe:

face_off wrote:

(Infos : Using DazStudio 4.8 Official (not the 4.9 beta))

- Problem to set manualy a focus to a point (the hand in the exemple)

- Sometime, i have to rebuild the scene or he do not restart the render

Ye - it looks like Focus Picking is not working at the moment. This appears to be related to when you export a scene to ORBX, the Octane camera focal distance, etc is not set correctly in the ORBX. I am working on it - but it will take some time to fix.

Paul

I'm testing 3.0.0.6 right now with G2 and G3, don't have this problem though... focus picking both manual and auto are working fine for me.

The overall performance boost is very welcome, I've gotten as much as 4x faster render speed than V2.xxx on my system, even when I was streaming video on my second monitor just to test. DAZ Studio used to lag for me in 2.xxx when OCDS viewport is open, now it doesn't. Response for both DAZ and OCDS viewports are instantaneous now, even with SLI on.

Older scenes also open just fine, I found no need to tweak anything at all. They render faster and if anything, their looks seem to be improved in 3.0 compared to in 2.xxx.

However, closing OCDS viewport in mid-render and reopening it causes OCDS to stop rendering as if it's in pause mode (verified and reproducible). Reloading the scene will fix this though.

Also getting random occurrences related to scene updates, particularly those that have to do with body morphs aren't translated to OCDS viewport live, but reloading/rebuilding scene or restarting DS will fix it. I'll try to pinpoint what causes it and report back.

" Ye - it looks like Focus Picking is not working at the moment. This appears to be related to when you export a scene to ORBX, the Octane camera focal distance, etc is not set correctly in the ORBX. I am working on it - but it will take some time to fix.

Paul "

Thank you for your answer Paul.
After all you do for the Poser Plugin, to know you working now for the DazStudio plugin is a very good news for us.

Sincerly,

C.O

Hi,
there was a bug with info channels passes in Alpha 1 and it's already solved in the next SDK.
So it's better to wait to work with multipass untill the next release
ciao beppe

SiliconAya wrote:Win7
32GB RAM
2x GTX Titan
Driver: 358.5
DS 4.8
OcDS 3.0.0.6
Turning on any of the info passes under Render Passes in the viewport seems to crash/stop renderer from working. Their "tabs" are also greyed out and unclickable, beauty and light passes seem to be working fine.
I've used both wireframe and AO in the past and they worked fine.
To get rendering working again I have to either start a new scene in DS or restart DS.
I also got the following errors:

Turning on wireframe:

Code: Select all

2015-12-18 12:20:23.514	22032	b2.24.2.5	CUDA error 700 on device 1: Kernel tried to load or store to an invalid memory address. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
2015-12-18 12:20:23.517	22032	b2.24.2.5	    -> kernel execution failed (wfCam)
2015-12-18 12:20:23.519	22032	b2.24.2.5	device 1: wireframe kernel failed
2015-12-18 12:20:23.625	22800	b2.24.2.5	CUDA error 700 on device 0: Kernel tried to load or store to an invalid memory address. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
2015-12-18 12:20:23.628	22800	b2.24.2.5	    -> kernel execution failed (wfCam)
2015-12-18 12:20:23.630	22800	b2.24.2.5	device 0: wireframe kernel failed

Turning off wireframe:

Code: Select all

2015-12-18 12:20:28.272	22800	b2.24.2.5	CUDA error 700 on device 0: Kernel tried to load or store to an invalid memory address. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
2015-12-18 12:20:28.275	22800	b2.24.2.5	    -> failed to deallocate device memory
2015-12-18 12:20:28.277	22800	b2.24.2.5	CUDA error 700 on device 0: Kernel tried to load or store to an invalid memory address. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
2015-12-18 12:20:28.279	22800	b2.24.2.5	    -> could not get memory info
2015-12-18 12:20:28.282	22800	b2.24.2.5	CUDA error 700 on device 0: Kernel tried to load or store to an invalid memory address. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
2015-12-18 12:20:28.284	22800	b2.24.2.5	    -> failed to allocated device memory
2015-12-18 12:20:28.286	22032	b2.24.2.5	CUDA error 700 on device 1: Kernel tried to load or store to an invalid memory address. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
2015-12-18 12:20:28.288	22800	b2.24.2.5	device 0: failed to allocate film buffer
2015-12-18 12:20:28.291	22032	b2.24.2.5	    -> failed to deallocate device memory
2015-12-18 12:20:28.293	22032	b2.24.2.5	CUDA error 700 on device 1: Kernel tried to load or store to an invalid memory address. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
2015-12-18 12:20:28.295	22032	b2.24.2.5	    -> could not get memory info
2015-12-18 12:20:28.297	22032	b2.24.2.5	CUDA error 700 on device 1: Kernel tried to load or store to an invalid memory address. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
2015-12-18 12:20:28.299	22032	b2.24.2.5	    -> failed to allocated device memory
2015-12-18 12:20:28.301	22032	b2.24.2.5	device 1: failed to allocate film buffer

Thanks a lot for Daz Plugin! It would be great if you add a link for HDR Light Studio as you did for Poser

Thanks Paul ! Definitely runs faster. But I am getting a lot more fireflies on the same scene than that was rendered by 2.24.2.5. I guess it is probably the Octane V3 alpha kernel engine and things will improve as it gets to the final version. Just downloaded and started testing.

Ditto on the fireflies... but I'm sure it will improve in the next releases.

Few things I've found in the last few days using 3.0.0.6:

The performance throttle sliders under the system tab don't seem to be working for me any more.

Changing the deep pixel rendering settings when deep pixel rendering is turned off restarts your render. (Not sure if this is a bug or just how it works).



On another note, the medium settings under Environment seem to behave quite differently than when using a "fog cube", lighting doesn't seem to interact with it all that much and I was unable to get any kind of light shaft/godray, so ended up switching back to a traditional cube with specular fog material to get them. Is there something that has to be done differently when working with the new environment medium settings?

The performance throttle sliders under the system tab don't seem to be working for me any more.

Yes, Otoy have said that Octane3 does not currently support render priority or throttling.

On another note, the medium settings under Environment seem to behave quite differently than when using a "fog cube", lighting doesn't seem to interact with it all that much and I was unable to get any kind of light shaft/godray, so ended up switching back to a traditional cube with specular fog material to get them. Is there something that has to be done differently when working with the new environment medium settings?

Try a larger Medium Radius (20 for example). A few people have been posting their settings and results in the forum here - so worth checking those threads out.

Paul

Does anyone know how to hide the hdri environment in 3? In 2 it was in the kernal settings.

Thanks

PS. Using PT kernal