OctaneRender® for ArchiCAD 3.03.3 [OBSOLETE]

[marek]

OK, thanks Paul,

Will try it tomorrow, 11.12 PM here.

Marek

[marek]

Paul,

Looks to me that my nvidia card is... weather sensitive, since today all is fine with that grass material.
So, this Grass with flowers material looks not bad, needs of course some geometry adjustments for the grass not to be gone through the pavement.
It might be more efficient method, though than adding it in Photoshop and makes no significant difference in rendering time.

One thing, though - all the materials coming from LiveDB need to be scaled up, say about ten times, what is a little troublesome. There are at least two parameters to be changed (scaled: Diffuse and Bump) and I'm not sure that's all.
My guess is that it might be something with Imperial units not translated to Decimal.

Also, that's quite different thing - for the notebook shadow around the flat part to be seen I had to reduce the Ray epsilon parameter to 0,01. Is it the only way for that kind of shadows to be seen?
That Ray epsilon shadow is pretty black and solid so is it the way to change it somehow?

Anyway, Octane is AWESOME!

Marek

[face_off]

One thing, though - all the materials coming from LiveDB need to be scaled up, say about ten times, what is a little troublesome. There are at least two parameters to be changed (scaled: Diffuse and Bump) and I'm not sure that's all.

Adjust the "LiveDB Texture Scaling" amount in the Configuration.

Also, that's quite different thing - for the notebook shadow around the flat part to be seen I had to reduce the Ray epsilon parameter to 0,01. Is it the only way for that kind of shadows to be seen?

Yes, close-ups on small items need a small ray epsilon. ArchiCAD might be throwing individual polygons 1mm in area through to 1km in area at Octane, so you need to adjust the ray epsilon to it knows where to limit self-shadowing.

That Ray epsilon shadow is pretty black and solid so is it the way to change it somehow?

Increase the sun size.

Paul

[marek]

Thank you Paul!

Marek

[marek]

Adjust the "LiveDB Texture Scaling" amount in the Configuration.

Paul,

It's not working.

LiveDB Texture scaling adjusted to the max e.g. 10 (no more allowed):
(BTW, why you can't see Archicad textures in OR rendering window?)

After attaching LiveDB texture to the surface:

Texture not scaled, obviously. Diffuse and Bump parameters need that (0,05 - first value).

After manually changing above:

Brick looks OK now, first parameters changed to 1,0 - 20 times.
There some textures for instance 'Concrete polished' requiring change of SEVEN parameters (30 times, from 0,1 to 3,0)!
Hopefully it's easy to fix, because OR textures and materials are so real!

Marek

[face_off]

Hi Marek

I am unclear what process you are following to get the images you posted. Are the second and third images from the LiveDb - they seem to have the material name from the ArchiCAD material - indicating not.

The LiveDb Scaling factor does not apply to textures converted from ArchiCAD materials. It's only when you import a material from the LiveDb.

Would it be possible to send me the scene from the first image? I suspect none of the textures are working because they are in the AC library - you need to extract them as per http://render.otoy.com/manuals/ArchiCAD/?page_id=169.

Paul

[marek]

Paul,

I'm using Material Pipette to pick any Archicad texture.

Archicad texture name stays but after importing LiveDB material has a LiveDB texture parameters.

I think the problem might involve decimal divider, in the parameters window it is dot (US, UK, NZ and Australia, I think), in EU and Poland and my system it's comma.

There is no texture conversion just exchange of them.
Second and third image show imported LiveDB material, second imported as it is, third with the increased values of Diffuse and Bump parameters (20 times).

Here you go, pla file:
https://www.dropbox.com/s/evmsgj233e74l ... k.pla?dl=0

Marek

[marek]

And AC scene after importing DB material:
https://www.dropbox.com/sh/9l2gxv6x0m16 ... 7ibqa?dl=0

Marek

[marek]

Yes, it might be confusing, but it's the way it is.

Octane render window displays Octane (LiveDB) materials but Archicad 3d window still shows the original Archicad's texture.

Marek

[face_off]

Archicad texture name stays but after importing LiveDB material has a LiveDB texture parameters.

I think the problem might involve decimal divider, in the parameters window it is dot (US, UK, NZ and Australia, I think), in EU and Poland and my system it's comma.

There is no texture conversion just exchange of them.
Second and third image show imported LiveDB material, second imported as it is, third with the increased values of Diffuse and Bump parameters (20 times).

Here you go, pla file:
https://www.dropbox.com/s/evmsgj233e74l ... k.pla?dl=0

Hi Marek - I downloaded that pla, and it seems to render fine for me (pls see below). It is definitely converting the AC materials to Octane materials for me. I have Scene Scaling set to 1, and LiveDb Texture Scaling at 3. That scene appears to not use any LiveDb texturemaps. If I import "Bricks running" I needed to set the LiveDb Texture Scaling to 0.5 to get the right brick size.

If you think the plugin is having a problem with the 'comma', change your Windows settings to 'decimal point' and see if that fixes the issue. The plugin uses the AC API to do all the number conversion - so I doubt this is an issue - but worth checking.

One final point - there are a lot of AC materials in your library - are they all needed? It is cause the Cache Stage 1 to take quite a long time.

Paul