Print at Feb 12, 2026, 10:28:40 PM

Posted by z56oo at Feb 3, 2026, 11:33:59 AM
Re: Generate terrain from a room in batch mode / Hijacking the “Generate 3D terrain from rooms…” plug-in
Keet,
Some food for thought (I’ve pushed a little my reflection on the subject)

The grid points are virtual: only their elevations are recorded as properties (If the room is moved, all properties are lost (become obsolete) , even those assigned to the room's native points ) .

The room’s native points follow the room move.
Therefore, if we want to store a given elevation for a point in the room , one solution is, for example, to modify the point tag by introducing a Z value, for example
<point x='3957.4912' y='32.531234' z='125.567'/>
This Z elevation is only used for "Generate 3d terrain" and is therefore an absolute elevation relative to the ground level (does not depend on the level where the room is located)

To say that this elevation is locked is equivalent to forcing a property for this point in the properties generated by "Generate 3d terrain", like (in the example above):
<property name='terrainElevationAt(3957.49,32.53)' value='125.567'/>

In the bottom-left box of "Generate 3d terrain", introduce a check if you are editing a native point of the room; in this case, a 'Lock' tick box will be displayed.
If this point has a Z value, display the Z value by setting Lock to true. The user can either leave the Lock enabled and not modify the value, or remove the Lock, in which case he can modify the value. He is free to re-enable the Lock or not afterwards (if he enables the Lock, the new Z value is recorded; if he removes the Lock, the Z value from the tag of this point is removed).
If this point does not have a Z value, Lock is false; the user can change the value and is free to then enable or disable Lock (if he enables Lock, the point is recorded with a Z value).

Regarding the method, it depends on the algorithm used. One solution could be (it's probably/certainly not the best): proceed as currently (without considering the Locks) and at the end check if a point elevation with a Z value has been modified , and if so, we simulate a complementary action on that point to return its elevation to its Z value (with the same parameters : radius of action, linearity, etc.). However, in this case, pay attention to infinite loops if two points with Z values are close together...

The cherry on the cake would be to update the "Edit room points" plugin to display this Z value. This would provide the functionality to review room points that have a Z value, without necessarily needing to introduce a "highlight Locked Points" function under "Generate 3D terrain" to visualize/find room points with a Z value.

Have a nice day
Cheers, Olivier