OctaneRender™ Standalone 2.12.1

[FoolooF]

Got an error when I tried to run 2.12:

The procedure entry point GetNamedPipeserverProcessId could not be located in the dynamic link library KERNEL32.dll.



I am running Win Xp sp3 (32bit)

[funk]

The new compact view looks great guys.

I see you decided to remove tonemapped EXR after our discussion (I would have preferred it was fixed), but you only removed it in the render pass dialog box, not in the single image saver.

[virtualzapp]

Hi,

On Mac, I can't open the standalone version 2.12 (back in 2.06).
Indeed it gives a file error at launch without possibilities to do anything than click ok and it closes… (cf attached screenshot)


Cheers
Regis

Which Mac OS are you using?

I'm running Mac OS X 10.8.5 with CUDA 6.5.18

[j7th]

"octane.render.getAllRenderOassesStatistics()"
typo in engine or only in post
Typo in post (fixed now).

[stratified]

The new compact view looks great guys.

I see you decided to remove tonemapped EXR after our discussion (I would have preferred it was fixed), but you only removed it in the render pass dialog box, not in the single image saver.

Hi funk,

I don't know yet if we'll remove it all together. I already saw a couple of post where people where trying to composite tone mapped results and scratched their heads. Applying an inverse gamma correction just to make it look correct in a viewer seems a hack to me. If everybody disagrees I'll reconsider ...

cheers,
Thomas

[funk]

Applying an inverse gamma correction just to make it look correct in a viewer seems a hack to me.

I'm not quite sure I'm following. The current tonemapped EXRs don't display correctly in any application I tested.

If I want to use these EXRs in Photoshop, After effects or Nuke (or even if I load the image into an octane scene to stick it on my 3d model's tv screen), I'll have to manually do the inverse gamma correction.

Imagine if we had to do this with every PNG exported from Octane. Wouldn't you consider this a problem?

[gabrielefx]

PMC speed increased from 9.43ms/s (2.11.1) to 21.80ms/s (2.12). Where is the trick?

2.11 was too slow. Compare with 2.06 and 2.10 and you see what I mean.

this issue was related to the speed or the diplayed number?

in this example I see more than 2X speed. Is it real or the calculated samples count has changed?

regards

[bepeg4d]

Hi,

On Mac, I can't open the standalone version 2.12 (back in 2.06).
Indeed it gives a file error at launch without possibilities to do anything than click ok and it closes… (cf attached screenshot)


Cheers
Regis

I have seen the same error message but only at the first start after installation.
at the next start the error message was not showed anymore.

i have an issue in working in the numerical fields of the color panel:

if i remember well, was present also in the 2.11 but i forgot to mention, sorry
anyway, very good update and i love too the new compact node inspector,
well done... as usual
ciao beppe

[enricocerica]

Oh, I forgot, I like the new compact interface!

Yep, much appreciated, very useful.

[virtualzapp]

Hi,

On Mac, I can't open the standalone version 2.12 (back in 2.06).
Indeed it gives a file error at launch without possibilities to do anything than click ok and it closes… (cf attached screenshot)


Cheers
Regis

I have seen the same error message but only at the first start after installation.
at the next start the error message was not showed anymore.

i have an issue in working in the numerical fields of the color panel:

Schermata 2014-10-25 alle 11.12.34.jpg

if i remember well, was present also in the 2.11 but i forgot to mention, sorry
anyway, very good update and i love too the new compact node inspector,
well done... as usual
ciao beppe

Hi Beppe,

Nope not working after trying 4 to 5 times, still the same issue ;o(

Cheers
Regis