Hi to all, some backgroundinformations:

At the end of 2016 I already experimented with such drives, at that time ingame with the programmable block. The reaction was possible, but it was too slow.
First hover vehicle: https://youtu.be/1mw1Qc1D7rM

Now with new possibilities in modding, I experimented with the distance detection and achieved better results. After many hours fighting with Blender, I had a model I was satisfied with.

The mod is based on an atmospheric thruster. The basic function of the dampers continues to function via the game mechanism and thus does some of the work (but it works to the center of mass!). In addition to normal behavior, the mod checks the distance to other objects.

1. starting from the center of the engine downwards (downwards is not the direction of gravity). In the test phase, it has been shown that it causes problems as soon as one engine recognizes the ground, another does not, which led to uncontrolled rotary movements. To prevent this, the sensor paths merge in one point (please note this when you put blocks around the engine). If the distance is less than the target distance, a force acts to increase the distance. If the distance is too large, a force acts to reduce the distance.

2. Since the regulation from 1. is not fast enough to have lots of fun with high speeds, the engine also checks the area in the direction of flight. The sensor path starts at half-altitude under the engine and moves forward to the current ground level. The distance depends on the current speed. An internal logic checks the distances at the current flight direction. When a collision is imminent, a force acts regardsless of the current altitude to increase the distance to the ground.

To see the sensor path, activate "debug" in the controls. If the path hit the ground or a object, the path will be displayed in game (blue normal, red if hit the own grid, on DS more transparent than on SP/MP).
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=1225922798 (old Pic)

The acting forces are acting to the center of the engine (not center of mass!), thats important for your design.

The creation of the controls is very cumbersome and has cost me a lot of time and nerves. In order to be able to transport these settings via blueprints, I have decided to save them in the "Custom Data" of the block.

________________________________________________________________________
Technical Details of the Blocks:
(on Earth planet, other Planets have other Force values but same result. Its a Keen secret why the menue shows other values)

Civilian Version:
Small Grid Small HoverEngine:
Force magnitude (N): 88000
Active power consumption (MW): 0.21

Small Grid Large HoverEngine:
Force magnitude (N): 449000
Active power consumption (MW): 0.72

Large Grid Small HoverEngine:
Force magnitude (N): 462000
Active power consumption (MW): 0.708

Large Grid Large Hover Engine:
Force magnitude (N): 5940000
Active power consumption (MW): 4.908

Military Version:
Small Grid Small HoverEngine:
Force magnitude (N): 140000
Active power consumption (MW): 0.315

Small Grid Large HoverEngine:
Force magnitude (N): 714000
Active power consumption (MW): 1.08

Large Grid Small HoverEngine:
Force magnitude (N): 735000
Active power consumption (MW): 1.06

Large Grid Large Hover Engine:
Force magnitude (N): 9450000
Active power consumption (MW): 7.36

________________________________________________________________________
Control names for scripting (not tested, maybe you have access):
(reason for different controls for Large and small is the differnece between the limits)
Large Blocks:
L_altitudemin
L_altituderange
L_altituderegdist

Small Blocks:
S_altitudemin
S_altituderange
S_altituderegdist

All Blocks:
aligntogravity_btn
force_to_centerofmass_btn
color1
debug_btn

I hope you have fun and this has explained some of the background, if you have questions, please feel free to ask.

Regards,
Takeshi