Game: the start sometimes sits at 100% on Loading pipelines before going on to the game #714

New issue

Closed

opened 2026-11-15 05:50:46 +00:00 by HumanBean · 1 comment

HumanBean commented

2026-11-15 05:50:46 +00:00

Owner

A player reports that the start sometimes sits on Loading pipelines at 100% (32,623 / 32,623 pipelines, "a few seconds left") for a while before it goes on to the game. It does reach the game in the end: it isn't a hang, but it looks like one.

Reported on Discord: https://discord.com/channels/1569849200047427645/1569849200617726065/1571398809983127662

How to reproduce

Seen on: v3.0.0-rc.4. GPU, driver and OS not yet known.
Steps: start the game with a pipeline cache already built (the "Loading pipelines" step, not "Building pipelines").
Expected: the screen moves on to "Starting the game" soon after the bar reaches 100%.
Actual: sometimes the bar stays at 100% with all pipelines counted and "a few seconds left", then the game loads eventually. How long it stays isn't known yet.

Notes

In gpu/vk/vk_progress.h the bar only reads 100% once every counted part is over (fraction() holds it under 0.999 until then). After that the screen keeps the pipeline view until the start is finished, when it shows "Starting the game". So the wait is in work that isn't counted, between the last pipeline and the end of the start. Candidates: writing the pipeline cache back, waiting for worker threads, or the first work for the game.
The time estimate also stays at "a few seconds left" through that wait. Once everything is counted it could say what it is waiting on instead.
Needed from the player: how long the wait lasts, whether it happens on every start or only some, the GPU, driver and OS, and the log from a start where it happened (the times around the last pipeline and "Starting the game" show where the time goes).

A player reports that the start sometimes sits on **Loading pipelines** at 100% (32,623 / 32,623 pipelines, "a few seconds left") for a while before it goes on to the game. It does reach the game in the end: it isn't a hang, but it looks like one. Reported on Discord: https://discord.com/channels/1569849200047427645/1569849200617726065/1571398809983127662 ## How to reproduce - **Seen on:** v3.0.0-rc.4. GPU, driver and OS not yet known. - **Steps:** start the game with a pipeline cache already built (the "Loading pipelines" step, not "Building pipelines"). - **Expected:** the screen moves on to "Starting the game" soon after the bar reaches 100%. - **Actual:** sometimes the bar stays at 100% with all pipelines counted and "a few seconds left", then the game loads eventually. How long it stays isn't known yet. ![Loading pipelines stuck at 100%](https://git.magicbean.dev/attachments/b047cd5b-94b3-49f7-b44c-c97a7f37fb8a) ## Notes - In `gpu/vk/vk_progress.h` the bar only reads 100% once every counted part is over (`fraction()` holds it under 0.999 until then). After that the screen keeps the pipeline view until the start is `finished`, when it shows "Starting the game". So the wait is in work that isn't counted, between the last pipeline and the end of the start. Candidates: writing the pipeline cache back, waiting for worker threads, or the first work for the game. - The time estimate also stays at "a few seconds left" through that wait. Once everything is counted it could say what it is waiting on instead. - Needed from the player: how long the wait lasts, whether it happens on every start or only some, the GPU, driver and OS, and the log from a start where it happened (the times around the last pipeline and "Starting the game" show where the time goes).

Rows
Columns