Ridgeline Hollow Runs at Sixty. It Does Not Feel Like Sixty, and We Can Show You Why.

The complaint we were testing

Ridgeline Hollow has been described in a dozen places as running well and feeling wrong, which is the sort of sentence that usually means somebody has noticed something real and lacks the tools to name it. The reported average frame rate is above target on almost any current configuration. The reported experience is of a game that hitches while riding.

Both of these are true, and the second one is measurable.

Method

We defined a fixed traversal route in each of nine areas, ranging from dense settlement to open moorland, and rode each route at a constant gait forty-one times. Captures were taken with an external frame-time logger, not the game's own overlay. Three runs were discarded for interference from an unrelated background process; the remaining thirty-eight are the dataset.

Thirty-eight of thirty-eight surviving captures show the same stall. Its magnitude varies between 28 and 39 milliseconds, and its position correlates with map coordinates rather than elapsed time, which rules out anything periodic in the engine's own scheduling.

What the traces show

The average is fine. The distribution is not. In our worst area, the mean frame time was 16.4 milliseconds against a 16.7 target, and the worst one per cent was 34.1 milliseconds — a stall of slightly over two frames, arriving roughly every eleven seconds of continuous movement.

Note the inversion. The busiest area, the settlement centre, has the highest mean frame time and the mildest stalls. The emptiest area, the ridge path, has the lowest mean and the worst stalls. This is the signature of a streaming problem rather than a rendering one: you cross cell boundaries fastest where there is least to draw.

What we ruled out

• Shader compilation. The stalls persist after twelve hours of play on a warmed cache, and their positions do not move.
• Storage throughput. Identical behaviour across three drives of very different speeds; the stall magnitude changed by under two milliseconds.
• Memory pressure. No correlation with allocated memory, and the pattern is unchanged with the texture budget halved.
• Our bench. A second machine of entirely different configuration reproduces the interval, at proportionally similar magnitude.

Why average frame rate hid it

Because a two-frame stall every eleven seconds costs you roughly a third of one per cent of your frames. It is statistically invisible and experientially unmistakable, and this gap is the single strongest argument for publishing distributions rather than means. A reviewer running the game and reading an overlay would see sixty and write down sixty.

The game underneath

Worth saying clearly: this is a good game. The writing in its settlement questlines is the best in its genre this year, its map rewards curiosity rather than checklists, and its riding animation is superb. Nothing in our data touches any of that.

What the data does establish is that a specific, reproducible engine problem is degrading the moment-to-moment experience of every player on every configuration, that it is not a hardware issue anybody can spend their way out of, and that it has gone unnamed for four months because the wrong number was being reported.

Score

7.1. A game we would recommend, with a technical caveat that we would want to know about before buying and that no storefront page will tell you. If a patch addresses the streaming boundaries we will re-capture the full route set and publish the comparison.