Skip to content
TECHNICALLYARTIST
FAB

Troubleshooting

Most issues come down to a session that was never opened, a missing widget class, or a layout that random positioning cannot move. Work down this list.

  • Did you call Begin Solving? Checks only run inside an open session.
  • Is Auto Trigger Skill Checks on? If it is off, nothing appears on its own; you have to call Show Gauge yourself.
  • Is Widget Class set? If it is empty, the component logs an error on Begin Play and shows nothing. Set it to WBP_GaugeSkillCheck (or your own widget).

That is Max Full Rotations set to -1 (infinite). Set it to 1 or more so an unanswered check times out into a miss.

  • Make sure the input calls Attempt Skill Check on the same component instance that is running the check.
  • It only scores while a gauge is visible; at any other time it is a safe no-op, so this will look like “nothing happened”.

The great zone is small by default (0.035) and sits at a random spot inside the good zone. Increase Great Zone Size, lower Gauge Speed, or both, to make perfect hits realistically reachable.

  • Assign the sound fields in Default Gauge Settings, or use the preconfigured BP_RadialSkillCheck, which ships with example sounds already set.
  • Remember the order: Skill Check Sound plays first, then the gauge appears after Skill Check Sound Delay seconds.

Random Position works by setting Canvas anchors on SizeBox_Container, so that box must be a direct child of a Canvas Panel. Also check that Random Position Margins are not so large that they collapse the valid area to nothing.

Tune Skill Check Interval and Skill Check Interval Variance. The gap between automatic checks is the interval plus or minus the variance, and never less than 0.5 seconds.