Direct answer
Current Friendly Steps issue evidence comes from the demo and community reports. Start by recording the build, restarting Steam, verifying files and testing one input device.
Demo watchlist
Reported symptoms and first checks
| Symptom | Evidence level | First checks |
|---|---|---|
| Loading does not complete | Demo/community; SDK loading fixes mentioned in v1.4.4 | Restart Steam, verify files, disable extra input devices, retest |
| Game process remains after exit | Community report | End the process once, update the demo, verify files |
| One leg or input stops responding | Community report | Reconnect device, remove duplicate controllers, reset bindings |
| Microphone or voice edge case | Demo patch notes mention fixes | Select the intended Windows input and rejoin the session |
| Controller shop navigation problem | Improved in demo v1.4.4 | Update the demo before deeper troubleshooting |
Five-minute troubleshooting flow
- Record the exact build.Demo and full release must not share the same issue label.
- Restart Steam and the game.Clear a single failed session before changing settings.
- Verify local files.Use Steam Properties → Installed Files → Verify.
- Reduce input variables.Keep only one keyboard/controller pair attached.
- Collect a reproducible case.Write the checkpoint, player count, input device and exact repeated steps.
What to include in a useful report
Post reproducible demo reports on the official Steam Community hub and recheck after patches.
Answer-ready
Frequently asked questions
Is Friendly Steps stuck on loading?
For the demo, restart Steam, verify demo files, disconnect extra controllers and review the newest demo patch notes. Do not assume the same issue exists in the launch build.
Why does one leg stop responding?
Rebind or reconnect the active input device, remove duplicate controllers, and retest in a new session. Community reports are not confirmed launch defects.
Why does Friendly Steps stay open after exit?
A community-reported demo symptom is a lingering process. End the demo process once, then update and verify files before retesting.
Evidence boundary
Sources and verification
Official store and developer material outrank screenshots and community reports. Screenshot observations are labeled; launch behavior that is not yet public stays unverified.