Version 2.24.2-R2 (22.01.2016) Tweet

[aoktar]

Archives has been updated. Two fixes done for Node editor bug.

[Rafael-Vallaperde]

GOD!

Pan in the Live viewer! this is awesome, thank you very much aoktar. appreciated.

Noticed the following:

Live viwer behaves better now, without so many resets. if i untoggle the updtades the render goes just fine, this is great.

Render region seems broekn when paning around, if i pan on full res to another area and try to use render region it offsets the arera i marked. is this a bug or limitation?

If i mark an area with render region and then mark another area render wont reset the whole scene, it will add samples and keep the ones achieved on the last selection made, that 's cool. There seems to be a bug though, if i render region, pause the render, uncheck render region and then resume the samples are still retained. it's a bit confusing to explain, but try to replicate it over there.

Something that made me a bit confused it that the passes were moved to the render settings, is this correct? now we have render passes and live viwer passes, why do we have two settings? is there an specific use?



Again, thank you so much for the dev on this. if you fix the render region offset while on final resultion panning my life will become 400% better.

Cheers
Raf

[dbalzer]

Hi Aoktar,

Thanks for putting all the hard work into making the Octane experience better each time. And thanks for giving the render layer mask its own little window within render settings

One thing I noticed since I've updated to today's version is that I am missing the render stats within LV even though They're all ticked on. I am running Windows 10 and C4D v17.048.

Maybe its just me?

Best
Dan

[aoktar]

@Rafael-Vallaperde:
What was the your previous version. For RR, yes i forgot to integrate that. It was not easy update for me. I had some hard times while making all last improvements/fixes.
I think you haven't followed the TEST version topic. We have removed and simplied the render pass usage. Now you can work from Render Settings and be sure about outputs. Settings->RenderPasses is gone.

@dbalzer: It's not just enough to see all stats. Also upper side of LV is a switcher for infos. Click to switch for different modes.

[alexmunteanu]

Hi, Aoktar,
The camera tag in stereo mode doesn't work in this latest release, not in LV nor in the PV.
I'm running R17.048.
The previous release works fine with stereo (2.24.2-test6).
Thank you!

[zoppo]

The Response (camera profile) setting in the CameraImager tab doesn't work anymore. Just doesn't do a thing.
It worked in Test6 if I remember correctly.

EDIT: Sorry, my bad. I found the settings in the camera tag. They seem to overwrite the settings in the render settings.

[aoktar]

Hi, Aoktar,
The camera tag in stereo mode doesn't work in this latest release, not in LV nor in the PV.
I'm running R17.048.
The previous release works fine with stereo (2.24.2-test6).
Thank you!

Yes. It seems that disabled by my mistake. I'll fix on monday.

[DigitalOven]

Hi Aoktar,

Thanks for the great updates! I just recently started using 2.24.2-test6 and hoping this might be user error but wanted to see if you were aware of this (I will update to R1 after getting next render done but assume it's very similar to test6).

Here is the issue:

I have been rendering all weekend and occasionally getting freezes where PV will render the first frame and then freeze rendering the next frame.

I have quite a few animations I am rendering and when it has frozen I may make some changes to file and restart it a few times and it will still hang and then all of a sudden it works fine ... I have not noticed anything consistent that I do to cause it to start rendering properly. For the current render, I turned on transparency (had turned it off to see sky in LV) and it started working but I don't think this has been the case every time.

I'm currently using 2.24.2-test6, R17.048, OSX Mavericks ....
I am attaching both Octane Log and C4D console output for this issue ... current C4D file is 68 mb ... I can try to generate a smaller test C4D file if this is not something you are already aware of but not sure if I can create one that "always" hangs.

I turned on "ALL" in Octane log and notice the following when it freezes on the second frame :

use active DirectLighting Kernel
Movable:8 Nodes:337 Tri:0/53k Mesh:130 Hair:0 Used/free/total vram:517Mb/3.157Gb/6Gb
image 1 doesn't match image 0 for render pass 'Beauty'
image 1 doesn't match image 0 for render pass 'Beauty'
image 1 doesn't match image 0 for render pass 'Beauty'
expected tonemap type 2 but got tonemap type 0
image 1 doesn't match image 0 for render pass 'Beauty'
**** RENDER FINISHED **** stat=6
expected tonemap type 0 but got tonemap type 2
Message type:14 data:0x00000001309867F0
Message type:1001071 data:0x0000000130986CD0

[aoktar]

I'm currently using 2.24.2-test6, R17.048, OSX Mavericks ....
I am attaching both Octane Log and C4D console output for this issue ... current C4D file is 68 mb ... I can try to generate a smaller test C4D file if this is not something you are already aware of but not sure if I can create one that "always" hangs.

Can i get a sample scene? It's not possible to know what happens without scenes.

[DigitalOven]

I can definitely send a sample scene ... since I got my current file rendering and I really want to let it finish but will make one once it is done (render is 12 hours).

Since the current file is working it may not be a good test case ... I will check the last versions and find one that hopefully always freezes but will take a little trial and error ... so it will likely be sometime tomorrow.

Looks like a similar issue to one pxlntwrk and Asym93 had ... though Asym93 mentioned renderpasses and I am not using those.

most telling thing I noticed was the lines in the log that only seemed to show up when freezing:

image 1 doesn't match image 0 for render pass 'Beauty'
expected tonemap type 2 but got tonemap type 0