Read the feedback and finish the section
When SKI displays “CLOSE CALL,” note the feedback and keep your attention on the route out of the obstacle section. For practice, take a line you can already complete and make one deliberate adjustment. Check whether the label appears and whether you still leave the section cleanly.
Do not build a first-finish attempt around forcing a near miss. Begin with room to read the route. A displayed label can help you study an action, but it does not make an uncontrolled approach useful for reaching the bottom.
This page explains how to review close-call feedback and test a route choice. It does not prescribe an exact gap, distance from an obstacle, required speed, or guaranteed points value.
Understand what the video example shows
The recording below shows an obstacle corridor with “CLOSE CALL +79,” a speed readout, and “X1” on the screen around 35 seconds. You can see all of them at that moment in the player’s run.
Use the example to recognize the label and distinguish it from the surrounding displays. The value +79 belongs to that recorded event. It does not establish that every close call pays 79 points, nor does the displayed X1 explain a complete multiplier rule.
In your own session, read the action label and value after an attempt. If you also have an active objective, check its progress separately. A trick notification and an objective counter should not be treated as interchangeable.
Establish a route you can repeat
Choose a recognizable obstacle section with a visible exit. First complete it using an ordinary route you can control. Use that attempt as your comparison when testing a closer line afterward.
Check where you enter the section, which opening you use, and where you continue once you pass the obstacle. If the exit repeatedly requires a rescue turn, use course reading before experimenting with the approach.
Keep the same device and viewing setup. A new camera angle can change how you judge the space, so test it separately from the route. The camera guide helps you choose a view for nearby obstacles and the next section.
Compare one line adjustment
Once the baseline route is repeatable, change one part of the approach on the next attempt. Observe whether close-call feedback appears and whether you still reach the exit under control. Repeat the choice before making it part of a normal descent.
| Result | How to review it |
|---|---|
| Feedback appeared and the exit stayed clean | Repeat the same choice to test consistency |
| Feedback appeared but the next turn failed | Work on the exit before extending the attempt |
| No feedback appeared | Record that result without assuming a fixed detection distance |
| The adjustment caused a collision | Return to the controlled baseline and compare the approach |
Before trying a closer line, check the rest of the route. Aim to understand an attempt you can repeat. One lucky event cannot tell you a hidden distance rule.
Keep feedback, score, and time separate
Record the event label and value you actually saw. If you are comparing race attempts, record the finish result or time as another entry. The official description warns that mistakes cost time, so a larger event value does not settle whether the complete descent improved.
A simple note can contain the section, the approach choice, the displayed event, and the exit result. If the mountain or settings change, start a new comparison. A line learned beside one obstacle does not define all future courses.
For a broader explanation of the interface, read the score display guide. For a first finish, use reaching the bottom and leave optional close-call practice for another attempt.
Decide when to use the practiced line
After a few comparable attempts, ask whether you understand the entry and exit well enough to repeat them during a full run. Keep the ordinary route if the experimental choice still creates failures you cannot explain.
You can dedicate a session to reading close-call feedback and another to finishing or racing. That makes success easier to judge: one session tests an event, while the other tests the complete descent. Combine them after the event practice fits a route you already control.
FAQ
What does the close-call example show?
The embedded gameplay includes “CLOSE CALL +79” beside other run displays. It helps identify the event label; it does not set a universal payout.
Is every close call worth 79 points?
Read the value shown in your own attempt. The recorded +79 is one event, so do not use it as a fixed scoring formula.
How close should I pass an obstacle?
Begin with a route you can complete and compare one adjustment. Judge the feedback and exit without assuming an exact detection distance.
Should I chase close calls during my first finish?
Work on reaching the bottom first. Use a separate practice attempt to study optional event feedback after you can control the route.
Does close-call feedback prove objective progress?
Check the active objective’s counter separately. The event label, its score value, and task progress each need their own reading.