support

What are per-animation height settings?

ARES has in-built support for adjustment of "hover height" settings that are applied when specific animations are played (such as the animation when your unit is powered off/shut down, the charging animation, etc.)

These values can be altered to adjust your height when in these specific animations to avoid your unit being sunk partway into the floor or hovering a meter above it. These values (at time of writing) fall under the chassis section of the database and will generally look something like this if you run the command @db show chassis.hover:

chassis.hover.enabled 1
chassis.hover.default 0.0
chassis.hover.s_charging 0.0
chassis.hover.s_dead 0.0
chassis.hover.s_fault 0.0
chassis.hover.s_frozen 0.0
chassis.hover.s_shutdown 0.0

The first line in this section, chassis.hover.enabled 1, determines whether this built-in height adjustment system is enabled or not. (0 is disabled, 1 is enabled).
Each of the following lines sets a hover height for a different state of operation.

• default is your general hover height when powered on and walking around the world.
  
• s_charging is the animation displayed when on a charger that indicates a charging state but does not force an animation itself.
  
• s_dead is the animation displayed when a unit has been reduced to 0 integrity via damage.
  
• s_fault is an animation displayed during a fault state.
  
• s_frozen is an animation displayed when a unit's motors are frozen/locked.
  
• s_shutdown is an animation displayed when the unit is powered off or has run out of battery power.
  

Changing an individual setting

To make a simple adjustment to one of these settings, you would utilize the @db set command combined with the setting you wish to adjust and a value to adjust it with.

(These values should be approximately the same amounts as you would see using your viewer's "Hover Height" adjustment tool, so you may find luck putting yourself into the state you wish to adjust, using your viewer's Hover Height tool to find the appropriate height adjustment value, and copying it from there)

An example: If you are somewhat lower than normal (partially in the ground) during the s_shutdown animation, you may attempt @db set chassis.hover.s_shutdown 0.34 to set the new value.

Once you set the value(s) you wish to set, run the command @service effector restart to have your system pull the new configuration data from your database to apply. (Note that you may need to recapture your chat after restarting effector.)

Saving a file for bulk adjustments

You can also place multiple settings into a notecard named something like hover.db and load this notecard if you ever need to unpack a new ARES HUD or change multiple of these settings at once.

An example hover.db notecard might look like:
chassis.hover.enabled 1
chassis.hover.default -0.125
chassis.hover.s_charging -0.11
chassis.hover.s_dead 0.20
chassis.hover.s_fault 0.0
chassis.hover.s_frozen 0.0
chassis.hover.s_shutdown 0.335

This file would then get CTRL-dragged into your ARES HUD (into the controller model badge prim near the status bars) and, once you receive a message saying it was detected and moved to user memory, loaded with @db load hover.db and then @service effector restart and all of these settings should be applied at once.