OctaneRender™ Standalone 3.06 TEST 2

[coilbook]

Is it possible to convert procedural octane noise to bitmap and then use it for displacement. We just don't want to deal with manual texturing of objects since proderual does it right away thank you.

[bepeg4d]

Hi coilbook,
if the mesh has proper unfolded not overlapping uvs, then you can use the Octane Baking feature to bake any kind of procedural textures applied, like noise, dirt and so on, and reuse them, also as displacement.
ciao beppe

[coilbook]

Hi coilbook,
if the mesh has proper unfolded not overlapping uvs, then you can use the Octane Baking feature to bake any kind of procedural textures applied, like noise, dirt and so on, and reuse them, also as displacement.
ciao beppe

Thank you!

[coilbook]

Hi coilbook,
if the mesh has proper unfolded not overlapping uvs, then you can use the Octane Baking feature to bake any kind of procedural textures applied, like noise, dirt and so on, and reuse them, also as displacement.
ciao beppe

what is a proper resolution for baking. Seems like changing aspect ratio changes texture look. Like aspect ratio? In this example I am baking a rectangular plane with noise


Why did not cylinder create a proper texture with proper textures on cylinder caps? Same happens with the box.




Thank you

[mojave]

Why did not cylinder create a proper texture with proper textures on cylinder caps? Same happens with the box.

I think the problem is that you don't have UV geometry mapping the cylinder caps, or at least that what it looks like to me from the baked texture.

You also need to make sure both geometries, the one you are baking from and the one you are mapping the texture into have the same UV set, otherwise the mapping won't match.

If you are not sure, could you share the wireframe view of your geometry using the baking camera?

[coilbook]

Why did not cylinder create a proper texture with proper textures on cylinder caps? Same happens with the box.

I think the problem is that you don't have UV geometry mapping the cylinder caps, or at least that what it looks like to me from the baked texture.

You also need to make sure both geometries, the one you are baking from and the one you are mapping the texture into have the same UV set, otherwise the mapping won't match.

If you are not sure, could you share the wireframe view of your geometry using the baking camera?

Thank you. We really thought Octane can automatically map for us since procedural textures on cylinder looks fine and it will create a matching bitmap with mapped caps. That's was the whole point for us is not to deal with mapping and let octane do all the work.
Thanks for explaining.

[Zay]

We really thought Octane can automatically map for us...

I can see this would be nice to have if you're using Standalone and don't have a modeling program. Create an UV and use atlas as projection.
But since you use 3D Max, why do you need Octane to do it? Just curious.

[mojave]

We really thought Octane can automatically map for us

We try to keep Octane agnostic to any modifications or additions to the input geometry and limit to render what is provided, specially when the majority of our users use it as a plugin within software packages that already provide very good UV and advanced unwrapping methods.

Also think that doing this in an automatic way may not give you the best results as you may want more detail in certain areas or a very specific type of projection, which can only be achieved with some degree of user intervention.

[Notiusweb]

Hi Marcus,
Could you put an option to apply a filter map to an RGB image being used as a back-plate for the Visible environment?
Essentially, to let you Blur the background image (which itself is the image and has no 3D map...)
Thanks!

[Goldorak]

We really thought Octane can automatically map for us...

I can see this would be nice to have if you're using Standalone and don't have a modeling program. Create an UV and use atlas as projection.
But since you use 3D Max, why do you need Octane to do it? Just curious.

To this end, we are testing if the free version of Unity 2017 (w/ Octane Standalone features fully integrated) will automatically unwrap imported ORBX scene meshes and then feed them back into Octane for baking using Unity's unwrapped UV2 coords (so far it looks possible for <10 million poly scenes) . You could then export this result in a new ORBX for baking outside of Unity+Octane.

There is a similar (but different) built in unwrapping system in UE4 which would be used for that specific OR plug-in to allow in-engine baking without leaving the UDK tool.