Well, functions and pointers are really the same.
An ACTION (and also an EVENT) are really just VOID function, and by passing its address
as a parameter is as easy as passing any other VOID*. Then assign that address
to an unused function pointer... easy.


I see your shadowing problem, and I EXPECT to hit the same, but Im not that far yet...
Im still trying to get the entities to arrange themselves properly around the focus point.
Not so easy because I have a circle of LOD_0 at the focus, surrounded by a thick
ring of LOD_1 entities, etc. out to LOD_3. Getting them to arrange based on a
single formula is the tricky bit, as I need a single formula to to this .
Because the game (at boot up) calculates the clip_far to use, and how "big" each lod circle is.
This result gets fed to the terrain-management, and the entities are created/arranged.
So... for low-power PC's, the total terrain "circle" is small (115 entities),
and for higher-powerd PC's it is bigger (465 entities).
[/i]See spoiler at the bottom for some preliminary calculations.[/i]

Ive not gotten to changing heights yet. Once the entities are arranging correctly,
then I'll implement the height mapping. So I expect your problem, even though
I havent had to deal with it "yet".

What I expect to need to do is integrate a "normal recalculation" into the stitcher code
that looks at BOTH entities, and adjusts BOTH their normals for the edge pixels/polys,
based on the value one entity normal plus the other entity normal divided by two.



My entity LOD rings. (still in preliminary testing ATM)
This is only showing THREE of the seven steps possible.