OTOY Forums

For me motion blur with particles works, but crashes if I drag the timeline too far from the emitter death. Just tested it with SuperSpray though.
M.

Will realflow not updating during rendering be fixed in the next release. I used scanline render and it works fine updating realflow bin mesh but with octane it is static during rendering but works fin in octane viewport

Thanks

bicket wrote:Thank you Karba

I hope we could have a render passes selector inside octane viewport.

This would be awesome!!!!!!!!!

- oh crap - I only realised now that I should use render elements to extract render passes - yes viewport selector would be very very much appreciated - for testing purposes at least

I will add more passes soon.

wastzzz wrote:For me motion blur with particles works, but crashes if I drag the timeline too far from the emitter death. Just tested it with SuperSpray though.
M.

I can reproduce the issue, will fix it.

vfxman83 wrote:Hi Karba;

How to export multi octane cameras export to the stand alone? The tool export only selected wievport camera.

ı saw a script over the internet but i don't try

Will you fix this next release ?

and when the final octane render is produce ?

we have a lot of problems everyday.

Unfortunately multiple cameras export is not easy to implement.

oguzbir wrote:Do you all achieve MB in Particle Flow using vertex blur or object blur.
Vertex blur sometimes works with me. But it's painfuly slow.

Shouldn't it be right to work with object blur?

What would your advice be Karba? I must use vertex blur for PF?

PF requires vertex motion blur.

Philipp1980 wrote:Hey everyone,

as soon as I install the v2.13, nothing is rendering anymore. Not in the material libraries and not in the render viewport. When opening the material editor, 3ds max crashes. As soon as I go back to the previous version it works again. Is there anyone else with this problem?

Greetings

Have you installed required video drivers?

Karantir wrote:error rendering at all kernels: Started logging on 22.11.14 09:10:36

OctaneRender version 2.13 (2130000)

No interface with that address found. -> Not changing current daemon scan interface.

You can ignore this message. This message is logged when an invalid sub-net is set for scanning. In your case, you probably never touched the network render settings and with that the preferences store the default value which is 0 (i.e. 0.0.0.0) and invalid. The daemon scanner will fall back to the first valid sub-net it can find.