Slow aborting and image finalisation? Tweet

[Builtdown]

Hi,

Still I have problems with aborting rendering and render progress finalisation.
Any news about this issue?

I just rendered a large (5000x3000) picture with quite heavy scene. From 0%-98% render progress took about 1 hour rendertime but from 99% to 100% progress took about 30 minutes. That´s not cool.
And another case is when a large picture with a heavy scene takes 2 minutes to update on CPUs, then I render it for two minutes and see a thing I need to fix. I press Abort and have to wait 40 minutes for the render to abort. That´s not cool.

Both scenes have a composited background. That seems to affect especially the 99-100% render finalisation...

[vpii]

I was having trouble and went back to 3.05.3 since then printing large sizes works perfect.

[juanjgon]

The support of the LightWave compositing function is not a native Octane feature. It is done by the plugin on the CPU, and I agree that it must be completely refactored from the ground up. Now it is really slow.

I'll try to work on it for the next build, but meanwhile, if you are going to work in scenes at print resolution using the LW compositing feature, I recommend to render the scene with the preview window disabled (you have this option in the plugin options panel), or render the scene without the compositing and add the background in post.

Thanks,
-Juanjo

[juanjgon]

I have built a new set of functions to support the LW compositing feature that are almost 100x faster, so for the next plugin build all the problems related to rendering high-resolution images with the compositing functions enabled should be fixed, including the abort rendering, that now should be a matter of few seconds.

Thanks,
-Juanjo

[Builtdown]

Great!

[FrankPooleFloating]

Thanks so much J! You rock! Keep pumpin' the jam!.. especially if you are working with LW3DG in some capacity.. which is really my hope. If you aren't, you should be, as you are the most important LW plug dev...

[juanjgon]

The current production build has been updated to fix this issue:
viewtopic.php?f=36&t=61820&start=10

Thanks,
-Juanjo