LOD's not working as expected on plane's or grid's?

#1

I finally prepared a terrain mesh by splitting it up - https://github.com/domlysz/BlenderGIS/issues/172

And I intended to start testing applying LOD’s, initial attempts did not work.

So I opened the example LOD blend file from - https://github.com/armory3d/armory_examples/tree/master/lod

And switched to tests on simple shapes to try and understand how the LOD’s function:

Objects like Monkey, Cube and Sphere work fine and switch through the various LOD’s & different materials applied as you move away. However the Plane and Grid does not change it’s material (colour)? It appears to only show in Krom the last LOD’s material?

Anybody have an idea why this might happen?

My intention is to apply LOD’s to all of these tiles:

0 Likes

#2

I’ve wondered how you would do landscape/terrain LODs. Maybe we can get a example blend , if it’s different than regular LODs.

1 Like

#3

I might just be doing something wrong? - as Planes/Grids act a little different, for example I noticed the back face shows empty, but I assume that is expected re something to do with backface culling etc.

I have raised it as an issue so hopefully Lubos will clarify -

Feels like it’s within reach to work on terrain LOD’s if I can get past this confusion…

0 Likes

#4

That is an option in the Armory Props in the Material panel for whatever material you are using. You can check “Double Sided” to have both sides rendered.

Also, does the LOD difference still occur on plains that are subdivided, i.e. more than a single quad?

0 Likes

#5

Good question - I had actually subdivided my 2 existing planes a few times. But just to check I added another plane with no subdivision and that behaves the same without LOD’s cycling - or at least the material is definitely not, as I would not be able to tell if LOD mesh’s are cycling through!

Ticking ‘Two sided’ does indeed make both sides render now - I only ticked on the last LOD as that is the only one showing when run.

0 Likes

#6

Hi, i opened an issue a year ago and made a feature request that wrap your issue here https://github.com/armory3d/armory/issues/385.

3 Likes

#7

Ah I recollect seeing your article a while back - that’s amazing work.

0 Likes