Hiya all...

I feel kinda dumb askin this? But how can I get a terrain to move?

Im using ent_createterrrain to create it,
then setting the DYNAMIC flag (to no avail),
feeding its pointer to a function and trying
to manipulate its XYZ co-ords directly.

Ive been playing and reading for an hour now, but it remains
firmly fixed in place...

Any ideas anyone?

Terrain cannot be moved, you need to remove and recreate it.

No way ... at ALL ... EVER??

But If I gotta keep removing and re-creating, what that going to do
to my memory consumption?

Or do ent-remove'd terrains actually FREE their resources?

Why do you need to move terrains anyway? Are you working on an editor?

No, Im looking into an endless-terrain world concept where the
terrain is generated in the distance infront of you, and erased
in the distance behind you.

I was going to have a 'store' of terrain entities and just adjust their
heightmaps as they get activated on your horizon, as low-poly terrains.
And as the get closer, they get replaced by higher-poly terrains from
a different LOD 'store' and that gets a more detailled hightmap inserted.

See where Im going? Im trying to create a "potentially" edgeless world.

I may need to go back to an older concept of using entities instead of terrains.
Its just the new addition of ent_createterrain gave me new ideas...

Dude, I'm not sure, but may be this could help you?
The Sewer

Edit: I misunderstood you problem dude, sorry.

why not using vertex to move it?
you go throug every vertex of the terrain and move it forward
maybe this is a solution
WFG PRogger

3run: It may well help with the stitching later, if I can get the entity
vertices to follow the same numbering structure as terrains, but it contains
nothing to help me at THIS stage.

Progger: I see what you mean, but its just not feasable dude.
When Im potentially moving a terrain by up to 2,000,000 quants in both
the X and Y directions, the maths will get pretty ugly. And thats assuming
Also, having a terrain with vertices as much as 1,000,000 quants away form
its origin could possible cause some serious performance issues, or odd
collision-hull behaviour...

Already tried the infinite_terrain.c that uses the level.c library from sample folder, or you are looking for something special?

No rojart, the infinite terrain uses "special effects" to make a single
terrain look like many.

Whereas mine will be many UNIQUE terrains looking like a huge single terrain.

Im going back to using pseudo-terrain models for now anyways...