Terradome - 3

[Hydra]

Folks,

Is anyone using Terradome 3?
http://www.daz3d.com/terradome-3-iray

The surfaces are very complex shaders, and the HDR skies don't seem to work either.

[Sorel]

I find it strange that the HDRIs would not be working.

[Hydra]

My bad on the HDR... its fine.

I was able to render but I needed to manually construct a shader... Frankly its not as good as their iRay shaders.

[DrHemulen]

Yeah, that's going to be something we have to get used to. Often you'd be able to render better images of scenery in Iray because you (not you personally) lack the skill and/or time to build proper Octane shaders for all items
I hope there's going to be a secondary market like normal material add-ons for these complex scenes.

[Hubby72]

I am really suprised, that the terrain shaders in iray works and look good and in octane - no chance. You need to create somethin on your own.

I always had the experience until now if it works in Iray at least it works also in octane with some "love". But here i am really surprised.

Do you think there will be any chance to get this running in octane better ?

[face_off]

I don't have the Terradome scene - so I'm unsure what the problem is - sorry.

Paul

[Hubby72]

Hi Paul,

i think it is difficult, because with terraDome i can not give you a scenefile. It is not like something that can be reproduced with some primitives.
I try to explain by using an included promoscene callen Mountain View.

In the picture you can see viewport and both renders octane and iray in seperate windows.
The octane picture looks almost like the viewport. So i would say OCDS is not doing something wrong.
But in Iray it looks so totally different.

What i found out meanwhile is that the scaling of the textures are wrong. When i change it in OCDS to x=1 and Y=1 then almost fit more. but i need to try out more there also.
Perhaps you have an idea to help.

I think also the Translation and Rotation does not fit, but it is late here today so i can test around more tomorrow.

My bloody non technical understanding is, that , because in the scene you can change or morhp around the Terrain zones that TD3 will add these transformation information directly before Iray wants them.
Because it also looks this broken in DAZ Viewport.
And as OCDS is importing these data while adding the objects to the scene and not later before rendering again. Something like that. Could be something special of Iray.
But i thought until now that Iray and Octane are technically not so far away from each other - why should NVidia build two totally different Renderengine. I think at least they are based on the same architectural software basis.

[face_off]

Thanks Hubby. Perhaps the info at https://docs.otoy.com/manuals/products/ ... may%20help?

Paul

[sikotik13]

The issue with Terradome 3 isn't the render engine itself, it's that the creators actually took time to write up an incredibly specific and complex shader node for Iray. It changes the texture dynamically with height, etc. (like a lot of multilayer textures for landscapes in terrain morphing programs and the Unreal landscape editor, for example). Iray itself isn't doing anything special or out of the ordinary, the shader was just written from the ground up to do things a specific way with that particular render engine.

[Hubby72]

That what i understood so far also.

But anyhow as long the Terradome Team did not change anything to the renderengine at some point it will handover the created shaders to the renderengine.

But anyhow. For me its not a total waste . As i do mostly fantasy settings i can still use it for landscape backgrounds and assign my own textures. Or to put render Iray Background layers.
The morphs are still fine for me.

But in that case i do not recommend to any DAZ octane users