Terrain does not rendering from underneath view

[ybahadiry]

I want to see the terrains underneath. Yet, I think it is not possible to observe terrains correctly due to back-face culling. I come up with solution which is rotating the terrain. However, I wasn't able to rotate the terrains even though I was able to transform it. Is there a way to rotate the terrains or make them render underneath?

Thanks in advance.

[Zylann]

If you want to see it from both sides, backface culling has to be turned off...
...which requires to add the render_mode cull_disabled; line on top of the shader you are using:

godot_heightmap_plugin/addons/zylann.hterrain/shaders/simple4_lite.shader

Line 2 in 768c5bb

Or render_mode cull_front;.

As you can imagine, just having that option in the inspector requires me to copy/paste EVERY shader just to have that line hardcoded there... so unfortunately I can't add this to the plugin in any maintainable way for now. You'll need to do that change yourself.

What is this for though? I never heard of a use case requiring to see heightmaps from above and below at the same time, only from a single side. If you want this for the ceiling of a cave, rotating is another option. The gizmo doesn't work because of #41 so you need to set the rotation in the inspector.

[ybahadiry]

First of all, changing the rendering mode works perfectly. Thanks for the answer. I couldn't find how to change it or is it possible to change it even though I noticed the problem at first. Now, it works perfectly!

It is okay for me to see one side of the heightmap. As you mention, I am trying to implement the ceiling.

I've read the issue #41 regarding the gizmo. Considering that, I tried to rotate the terrain with both the transform/rotation degrees tab under the inspector and GDscript. Both the inspector (yet, transform/translation works nicely) and GDscript didn't work for me to rotate.

Not sure it is a bug or not for now.

[Zylann]

Hmm now that I think about it, I didnt handle rotation in several places of the plugin because I haven't thought of a use case for it. It's probably just not supported.