they Changed terminal actions... /bangs head on keyboard.

Hot fix done.

seems to cause ship to rock back and forth on servers.

Not sure if this is a bug report or a new feature idea.

Observed behavior.
OFC disables override on all ship connected gyros when it boots.

In some of my ship designs I have an auxiliary gyro, or group of gyros, that have an override set to 0 rpm on all axes at 100% power. These are used for emergency ship stabilization, in normal situations, they are all turned off.

Is there a way to tell OFC to use a specific gyro or gyro group; or inversely to tell it not to touch a specific gyro or gyro group.

Flipping on the "emergency stabilization system" could make a bad situation worse or lead to a total loss of ship if OFC has disabled override on all emergency stabilization gyros.

Ran into some issue with OFC and grav drive systems.

1. The OFC running on a ship without a grav drive system will completely mess up the grav drive system on a mother ship when it docks via connector.

2. Even with gravdriveoff being the first command in the custom data of the OFC PB, OFC still messes with settings of grav gens.

3. Even after running gravdrive on the OFC to toggle gravdrive state OFC still insists on zeroing out grav gens.

It may be far less disruptive if OFC simply turned off the mass block and left the grav gens alone.

For example, in my mother ship, grav gens which are part of a GES (gravel ejection system) also double as an input to the grav drive system. If the ejection connector gets turned on, the mass block gets turned off via event controller, otherwise we would be pulled into the gravel stream which we are launching away from the ship at 2g.

When we turn on the mother ships's OFC, ship-wide gravity fails and the GES when engaged dumps a pile of gravel directly behind the ship.

Currently the engineering crew is referring to the OFC as the Orbital Fail Computer, or worse; and wondering if O.I.S. was a spin-off of K.S.H. ?

Personally, I feel O.I.S. has picked up were K.S.H. failed. O.I.S. software adds a lot of needed functionality to a ship.

We would appreciate solutions. Currently we have to shut the OFC down and run the grav drive manually via event controllers tied to directional thrusters.

Regarding issue we have been recently having with the OFC, our engineering crew has come up with some ideas that could be potential upgrades to the OFC.
Here they are for the consideration of O.I.S.

Regarding Issue 1.
Potential solution:
Commands be added to the OFC to allow it to ignore anything beyond the connectors of the grid it is running on.
Example suggested commands.
ModuleSupportoff
Instructs OFC to ignore anything beyond convectors of current grid.
ModuleSupporton
Instructs OFC to consider hardware beyond the connectors of current grid as safe to control.
This would allow dockable Atmo thrust modules, etc to be controlled by OFC when docked .
ModuleSupport
Toggle of module support state.

If may also be a good idea to have a setting stored in the custom data of a connector to override OFC behavior for that specific connector regardless of global state. Examples, connectors used exclusively for docking, or exclusively for module attachment.
Example
[OIS-OFC]
ModuleSupport=True
ModuleSupport=False

Regarding Issues 2 & 3.
Potential solution:
Before changing a Grav Gen's state, OFC stores it's on/off state, field dimensions, and acceleration values in the Grav gen's custom data. When OFC receives a command that turns the gravdrive system off, it restores the Grav gen configuration from the custom data.

This would allow OFC to control the gravdrive when it is flying the ship. This would also allow for the existence of a manually controlled gravdrive system that uses pre configured grav gens tied to conventional thruster systems via event controllers.

An example using one of our ship's GES GravGens
[OIS-OFC]
GravGenState=Off
GravGenH=2.5
GravGenW=5
GravGenD=150
GravGenA=-9.8

Thank You for your consideration.