OTOY Forums

I'm getting a Daz crash on Octane Export.

Can you send me a simple scene which crashes on export pls?

Thanks

Paul

face_off wrote:

I can see that you have not fixed the resize issue --> still increase geometry memory even the textures memory decrease, so at the final, the scene takes more VRAM than if not resized !

On which panel is the memory being incorrectly reported? The Textures panel or the System panel?

Paul

Hi Paul,

Sorry, I spoke too soon. I have in fact just test with a scene with nearly 3GB VRAM (just the limit of 780Ti).
Just retest with a single V7 and resized work --> decrease of texture OK, little change on geometry.
With bigger scene, something goes wrong and despite texture decrease, the geometry seems to get bigger. So after resized texture of my scene, I have CUDA failed as VRAM exceeded 780Ti.
I found a work around for this. After resized texture, close DAZ without save and restart DAZ and reload the scene. The texture remain resized (so the resized texture are NOT saved with the duf, but stay resized for all other scenes !).

Just load and render (no texture resized) resize texture : --> system pane geometry VRAM ??? Close DAZ and restart and reload the scene and check : Gain : 700MB on texture / Lost : 150MB Geometry for this scene. Good point !

Thank you for the 3.0.4.10 update.
Special thanks for updating the tab name to Octane.
It is great to now have more space to add tabs in the DAZ Studio user interface.

In this version and recent. After changing the render size it doesn't seem to change in render view.
3.0.4.10

As with previous versions...
When you change the "Max. samples (1/256000)" to say 10000 with either Path Tracing or Direct Lighting set for Kernel type, the OctaneRender viewport does not update with the correct number of samples.
The only way to fix this is to change from path tracing to direct lighting and back again or vice versa so that the view port updates.
Is this normal perhaps and suppose to happen like this?

After changing the render size it doesn't seem to change in render view.

You have not stated how you are changing the render size. Can you pls give me an exact set of steps to reproduce this problem.

When you change the "Max. samples (1/256000)" to say 10000 with either Path Tracing or Direct Lighting set for Kernel type, the OctaneRender viewport does not update with the correct number of samples.

I cannot reproduce this problem. I start DS, load hair prop, open the Octane Main window, open the Viewport (max samples are 500, kernel = DL), click the Rendersettings tab, change max samples to 750, and max samples in the Viewport panel now correctly update to 750. Is it possible you have Final Rendering clicked?

Paul

RGUS wrote:As with previous versions...
When you change the "Max. samples (1/256000)" to say 10000 with either Path Tracing or Direct Lighting set for Kernel type, the OctaneRender viewport does not update with the correct number of samples.
The only way to fix this is to change from path tracing to direct lighting and back again or vice versa so that the view port updates.
Is this normal perhaps and suppose to happen like this?

I got the resolution to change on this end by changing from Direct lighting or any other setting to another for it to update the resolution view.
Thank you for this temporary fix.
I have noticed the drag and drop of materials from presets taking more of a delay than in the other versions.

Sorry, I spoke too soon. I have in fact just test with a scene with nearly 3GB VRAM (just the limit of 780Ti).
Just retest with a single V7 and resized work --> decrease of texture OK, little change on geometry.
With bigger scene, something goes wrong and despite texture decrease, the geometry seems to get bigger. So after resized texture of my scene, I have CUDA failed as VRAM exceeded 780Ti.
I found a work around for this. After resized texture, close DAZ without save and restart DAZ and reload the scene. The texture remain resized (so the resized texture are NOT saved with the duf, but stay resized for all other scenes !).

I'm sorry - but I cannot reproduce this problem. There must be a setting or something specific in your scene which is triggering this issue. If you send me a scene with all it's assets, I can take a look.

Paul

Notiusweb wrote: Hi itou31, are you seeing that scenes that froze upon using OcDS 3.1 - 3.3 are now not freezing on 3.4? I actually am testing now more myself, and I am finding that there are freezes whenever the scene has any resolution-challenging elements, namely hair, at high res rendering. This is an anecdotal statement, I realize, however I am in a nutshell still seeing the freezing. It is not relegated to camera baking on standalone, it involves high res renders across the board. I am interested to what degree you feel you are are seeing less. For example, you had a scene that repeatedly froze on 3.1 - 3.3, but never on 3.4. Maybe I could share a freeze-scene with you via PM (ocs or orbx) and you could run and see if freezes?

Hi Notiusweb,
I cannot say that one scene or other never freeze on alpha4, at least I try to not test for the freeze. But I noticed that the freeze comes less often (I render often at 2000 x 2000 but not to higher).
However, just restest some scene with higher resolution (3000 x 4000) or playing with camera ---> freeze instantly.
So waiting for next release of V3, until then, disable most of my GPU that could affect the freeze.

, just restest some scene with higher resolution (3000 x 4000) or playing with camera ---> freeze instantly.

Yes, yes...I noticed that too. If I tried manipulating a scene during render it was provoking a freeze (1920 x 1080, high hair texture, so by default it had a slower render, maybe more demanding on GPU). Thanks for letting me know. I sent Abstrax a test scene that was causing freezes (and he confirmed he got it), so keep our fingers crossed!