# Troubleshooting (/docs/orbit-studios-resources/orbit-dynamichud-stress/troubleshooting)



# Troubleshooting [#troubleshooting]

<Accordions>
  <Accordion title="Stress value does not show in DynamicHUD">
    Confirm `orbit-dynamichud` starts before the stress addon and that `Config.EnabledValues.stress` is enabled in the HUD config. Then check that `LocalPlayer.state.stress` becomes a number after joining the server. If it stays nil, the stress resource is not initializing the player state.
  </Accordion>

  <Accordion title="Speeding always adds stress too early">
    Match `Config.Stress.stressSpeedFormat` to the unit you used for thresholds, then check whether your seatbelt resource sets `LocalPlayer.state.seatbelt`. When that state is false or missing, the resource uses `Config.Stress.minForSpeedingUnbuckled`.
  </Accordion>

  <Accordion title="Police or other jobs still gain stress">
    Check that the job name in `Config.Stress.whitelistedJobs` exactly matches the job name returned by `orbit-lib`. The whitelist only affects `hud:server:GainStress`; custom scripts that set `Player(source).state.stress` directly bypass the whitelist.
  </Accordion>

  <Accordion title="Screen effects feel too strong">
    Increase `Config.Stress.effectInterval` timeouts or reduce `Config.Stress.blurIntensity` values for the affected stress ranges. Change one stress range at a time, restart the resource, and test with `/setstress` so you know which range feels wrong.
  </Accordion>
</Accordions>