OctaneRender™ Standalone 3.06 TEST 3

[vijay]

Accidentally posted this is TEST 2:

Found a bug:
When using a batch render job it no longer saves out leading zeros with %f and it also adds ".0" to each filename.
We found this out when rendering an animation that we had previously run in 5.01 and it had the leading zeros and no ".0" in the filename.

This is fixed. will not happen in next release

Vijay

On the same note, if you save your render passes and use %p in your file name when using the batch script (Only tried this with the old script, not the new render jobs) it wont skip existing. It will just restart from frame 1 even if you have some frames rendered out in that folder.

Hi kavorka,

Did a quick test in the latest code and I couldn't reproduce this bug. This bug could be related to the frame number naming bug which is recently fixed. Hope this will not happen from next release.

Thanks
vijay

[JavierVerdugo]

Hello,

how to use the triplanar node? I don't see any information in the manual.

Thanks

[JavierVerdugo]

Today I was working with the last version, I put some hair, pause the live editor, delete the hair, add custom guides to the hair, modelling the hairs to get a proper flow, edit some of them to be less tall, change the generate tab of the hair to create flat hairs, and change the thickness of the hair material.. Then I add a octane material to it.... Upgrade live editor, cinema 4d crashes

I have to replicate the steps and get again the crash, but I don't get it so I guess it was some kind of random stuff?

The thing is bug report are not being generated because the software crashes in another way (usually I get Octanedll plugin has crashed blablabla), now only shows a message saying "Cinema 4d aplication has crashed"