Approximately Up Guide
Community fixGuide checked 2026-08-20Game version checked 2026-08-20

Player-reported guidance: not reproduced here in the current build.

My warning light needs to turn on below the limit

First actionSet the Simple Threshold to the limit you want to monitor and connect it to a disposable light or indicator first.

Check nextThe test indicator changes across both sides of your selected limit in the direction you intended.

A warning that needs to appear below an altitude or distance limit can look backwards when the threshold outputs 1 on the other side of the line.

Quick answer

Try this first

First confirm which side of the limit makes your Simple Threshold output 1. If it is the above-limit side, put a NOT gate between that output and the light, then test one value above and one value below your chosen limit.

  1. 1

    Set the Simple Threshold to the limit you want to monitor and connect it to a disposable light or indicator first.

  2. 2

    Check which side of the limit produces output 1; the current community report describes 1 at or above its 500 example.

  3. 3

    If that is the opposite of the warning you need, put a NOT gate between the Simple Threshold output and the warning light.

  4. 4

    Test just above and just below the limit before using the circuit during a flight. Record the component names and the exact behavior if the result differs.

Visual orientation

Invert the signal only after you test its direction

Show the conceptual order of input, threshold, inversion, and warning light without depicting current-game ports or interface states.

Original logic-flow diagram showing a threshold signal passing through a NOT gate before a warning lamp.
Original orientation diagramOriginal logic-flow diagram, not a current-game wiring capture. Test the current components and both sides of the limit before relying on the circuit.Open full-size diagram

What is happening

The signal has to be true on the warning side

A threshold can be useful while still producing its active signal on the wrong side of a warning boundary. The reported NOT-gate path flips that 1/0 signal before it reaches the lamp; it does not establish every current Threshold or lamp behavior.

Troubleshooting

If that does not solve it

  • Keep the light on a small test circuit until you see the expected state on both sides of the limit.
  • Do not assume the alternate Redirector, subtraction, or Remapper suggestions use the same current component behavior; they need their own test.
  • If the result is inverted twice or never changes, note the exact component names, limit, input source, and game version before switching paths.
  • Use the current in-game Manual for the actual component ports and labels; this page has no first-party current-build wiring capture.

Before you switch paths

Carry three signals forward.

A changed guide is easier to test when it starts from the exact point where this one stopped.

  1. 01
    Current game version and active mission

    Old values can describe a different build or objective.

  2. 02
    The part, input, or control path that failed

    Use the current in-game name and note the ports or axis involved.

  3. 03
    What happened after the first action

    Record one observed result before changing several things at once.

These notes describe your own run; they do not turn a community report into current-game proof.

Confidence

What is confirmed

This is a current player-reported fix: the original poster said the NOT gate worked, and other replies gave distinct alternatives. This site has not reproduced it in full-release 1.0.012.

  • On 2026-08-17, a player described needing a warning below 500 altitude or distance while their Simple Threshold output 1 at or above that value.
  • The first reply named a NOT gate, and the original poster later reported that adding it between the light and threshold worked.
  • Other participants proposed Redirector, subtraction, and Remapper patterns, so this page keeps only the short NOT-gate path as the first test.
  • Official update 1.0.005 previously fixed an unrelated Logic Gate OR behavior, so historical logic advice is not first-party proof of the current threshold behavior.
Sources and version notes

Game-version context checked 2026-08-20: Full release 1.0.012; logic path not yet reproduced first-party

  • Approximately Up - official Steam News feedConfirms the most recently named patch, 1.0.012, and a later official roadmap announcement. Roadmap items are not current features or first-party reproduction of guide steps.
  • Warning below 500 alt/distanceA current 2026-08-17 logic-wiring thread: the original poster reports that placing a NOT gate between a Simple Threshold and a warning light worked for a below-500 warning. Other replies offer separate Redirector, subtraction, and Remapper paths. Community evidence only; no current-build reproduction was performed by this site.