OctaneRender® 1.0 beta2.52 >>> download here <<< [OBSOLETE]

[mlru]

i had some strange black areas on objects with opacity set to 0 and the nvidia driver version 280.26 (in all modes: direct lighting, rt and pms).
that behavior went away using the 275.33 driver
so i think this:

on Windows the latest NVIDIA GeForce driver 280.26 causes problems with the first initialization of the alpha buffer, which we couldn't work around yet. for the time being please switch back to the previous stable driver release 275.33.

might still apply for this version, if not for the alpha buffer, then at least for opacity.
interestingly this wasn't the case in the OctaneRender® 1.025 beta 2.51 pre-release, where everything worked fine for me with the 280.26 driver version.

also the responsiveness seems a tad worse with the 275.33 driver than it was with the pre-release and version 280.26.

[amathews9518]

Beta 2.52 loads file.
It does not render however.
These files rendered in 2.46B.

Tried this in 2.46B and it just crashes after a while without rendering.
This worked before.
Any suggestions?

[radiance]

and flash when to add?

are examples of more octane 1 .23 (2010) ( sss and flash )

Hi,

That's not SSS but roughness on specular/glass.
The camera flash is modeled in blender, it's an area light above the camera.

You can easily set up a lighting rig like this in your 3d app for now, until we decide to add it in the next versions...

Radiance

[radiance]

hi there,

I'd like to know when will be the manual updated to beta2.52.

We are currently working on the manual, it should be done soon, and we will repackage it and communicate the addition here.

Radiance

[dkalna]

hi there,

I'd like to know when will be the manual updated to beta2.52.

We are currently working on the manual, it should be done soon, and we will repackage it and communicate the addition here.

Radiance

great, thank you radiance

[abstrax]

i had some strange black areas on objects with opacity set to 0 and the nvidia driver version 280.26 (in all modes: direct lighting, rt and pms).
that behavior went away using the 275.33 driver
so i think this:

on Windows the latest NVIDIA GeForce driver 280.26 causes problems with the first initialization of the alpha buffer, which we couldn't work around yet. for the time being please switch back to the previous stable driver release 275.33.

might still apply for this version, if not for the alpha buffer, then at least for opacity.
interestingly this wasn't the case in the OctaneRender® 1.025 beta 2.51 pre-release, where everything worked fine for me with the 280.26 driver version.

also the responsiveness seems a tad worse with the 275.33 driver than it was with the pre-release and version 280.26.

This is definitely a different problem than the one we fixed with beta 2.52. Could you post screen shots with and without the artifacts?

Thanks a lot,
Marcus

[grenzfrequence]

Again i get the same problems with octan 2.52 on ubuntu 11.04: cube is rendered wrong. I got no help until now and it is frustrating.

Greatings, Stephan.

[mlru]

This is definitely a different problem than the one we fixed with beta 2.52. Could you post screen shots with and without the artifacts?

Thanks a lot,
Marcus

Grr - after updating to 280.26 again everything looks fine, can't reproduce it.
Obviously something went wrong in my first update from the 266 to the 280 drivers.

I hate when that happens...

[adiarc]

I just recently rendered many images with Octane 2.49b, imported from Blender using Octane exporter without any problems (except the fact that most materials import as glossy when they should be diffuse). Now that I installed Octane 2.52, the exporter says "Something wrong happened, please check console logs". Does this mean the Python console? It doesn't say much anything.

The only reason I need to use the Blender exporter anyway, is to get the exact camera angle I want, because it's a pain in the ass to do it in Octane. Now I had to do it because the exporter doesn't work and it took me 30 minutes to do just that. Not very practical for professional work.

This is why I wish you guys made the camera controls more user friendly. Then I wouldn't depend on somebody somewhere maybe updating the exporter if they happen to have time. I am using this software for professional stuff cos it's a great quality software, so I would like to see the basics like proper camera controls be available.

If you want to know what I mean by proper camera controls is for example a slider for turning the camera around its z-axis 360 degrees by sliding the slider from one end to the other. Simple as that.

Thanks.

adiarc

[GeoPappas]

...I wish you guys made the camera controls more user friendly.

+1