This Forum should be used to post Feature requests or maybe useful Ideas vor new features and not for workarounds for that.

There's no need to say what this forum should be for!

Read the other threads and you know what is common in this forum.

Any news of this feature?

Yes, it would be useful, but the workaround with a shader is also easy - so it will come one day, probably together with an MDL extension for LOD meshes, but has low priority at the moment.

Yes, the workoarund with the SHADER is very good, but if you use Fixed Functions Pipeline, then there isn't a workaround.

well, why not just change materials depending on distance? You have to have a while loop for the objects, but as long as you dont use a million of them this can be done reasonably fast.

I think you can do this with a material event function.

Code:

---

function mtl_Event()
{
my.material=mat_norm;
  if(vec_dist(my.x,render_view.x)>lodfactor[0]*render_view.clip_far)
{
   my.material=mat_lod1;
}
if(vec_dist(my.x,render_view.x)>lodfactor[1]*render_view.clip_far)
{
   my.material=mat_lod2;
}
if(vec_dist(my.x,render_view.x)>lodfactor[2]*render_view.clip_far)
{
   my.material=mat_lod3;
}
}

material mat_norm
{
   event=mtl_Event;
   enable_render=on;
}
....
  

---

You convinced me... this solution sounds good. I'll try it.

Actually this is not a good idea to do it this way, becasue then you are calling vec_dist for every render of every entity. This is going to be sloooww

Better to use a loop in an action like this

while(1)
{
if vec_dist(my.x,camera.x)>dist && my.material!=newmat
{
chnage material to newmat
}

wait (1+random(5)*random(2)); //or whatever
}

this way you only call vec_dist once in a while for each entity...

Yes your are right about the vec_dist (altough vec_dist is fast), but its not a good idea to do this in the entity action list. My method is independent from the entity and works with more then one view.