not tried yet, just for the 1st sight is your vector declaration correct? I use VECTOR within functions instead of VECTOR*, and use always vec_set or other vec_ command.

I got it to work by iterating directly over the vertices with ent_getvertex and then using a scale factor for the vertex positions into the bmap pixel positions .

it's fine like this ,lod works fine ,the heightmap is applied fine and the speed is fine jumping from vertex to vertex.

I dont know what's wrong with that code sivan ,maby its the ent_nextvertex or math section plugged into ent_nextvertex ..

a good feature would be if the height between one lod mesh to the next are morphed/interpolated or smoothly changed over time since height changes from one lod to the next is a sore thumb SOMETIMES ,if there is already such a feature I would like to make use of it ,just point me in the direction ,just a thought though.

jb

another one I am not sure of , when I set terrain lod above 0 , and create a terrain with ent_createterrain ,I try to read the pixel off the terrain with terrain_getpixel .

all it does is return a script crash in terrain_pixel_for_pos no matter what I use as input for the terrain_getpixel function. .

it only works with terrain lod at 0

maby the bug is linked somehow..

the exact same issue with terrain_setpixel with the exact same error message ,only works with terrain lod at 0

I got the problem ! terrain bounds aren't automatically set , the terrain. max_x .min_x .max_y .min_y min_z max_z all give a result of 0 , if I use c_setminmax directly after terrain creation the terrain lod and everything works because the bounds are part of those calculated values used in the code parts I needed to use..

jb