Shader prepare time

xdNevermore commented

2026-11-11 08:59:05 +00:00

(Migrated from github.com)

Builder version

v2.1.0

How you built

Hookshot Builder app (Windows)

Game files given to it

A .nup

The error

Prepare the shaders process took more than 73 minutes and keeps going.
CPU: AMD Ryzen 5 5600, GPU: AMD Radeon RX 9060 XT (Driver Adrenalin 26.3.1), Motherboard: Gigabyte A520M DS3H (BIOS F16), RAM: 32GB (2x16GB) 3600MT/s CL16

Visual Studio or Build Tools version, and Windows SDK version

No response

Operating system and free space on the output drive

Windows 11 26H2

Before you send it

I'm on the newest release, or it still fails on it.
I searched the open issues for this error.
I'm not attaching game files or anything built from them.

### Builder version v2.1.0 ### How you built Hookshot Builder app (Windows) ### Game files given to it A .nup ### The error ```text Prepare the shaders process took more than 73 minutes and keeps going. CPU: AMD Ryzen 5 5600, GPU: AMD Radeon RX 9060 XT (Driver Adrenalin 26.3.1), Motherboard: Gigabyte A520M DS3H (BIOS F16), RAM: 32GB (2x16GB) 3600MT/s CL16 ``` ### Visual Studio or Build Tools version, and Windows SDK version _No response_ ### Operating system and free space on the output drive Windows 11 26H2 ### Before you send it - [x] I'm on the newest release, or it still fails on it. - [x] I searched the open issues for this error. - [x] I'm not attaching game files or anything built from them.

xdNevermore commented

2026-11-11 09:16:14 +00:00

(Migrated from github.com)

Ekran görüntüsü 2026-11-11 121439 94th minute and still going, it does not stuck.

<img width="659" height="81" alt="Ekran görüntüsü 2026-11-11 121439" src="https://github.com/user-attachments/assets/ca29feaa-eb77-40f6-b4d9-d3227dc54e35" /> 94th minute and still going, it does not stuck.

Spidgeon1 commented

2026-11-11 09:19:01 +00:00

(Migrated from github.com)

Same on a Ryzen 5 5600x. Its using %100 of my CPU but not moving.

NeonDerg commented

2026-11-11 10:48:29 +00:00

(Migrated from github.com)

57 minutes into the prepping shaders stage on a 5800x, does it normally take this long? The builder says the entire process normally takes 45mins

<img width="417" height="73" alt="image" src="https://github.com/user-attachments/assets/0833f702-88e6-4078-b484-de993c00f579" /> 57 minutes into the prepping shaders stage on a 5800x, does it normally take this long? The builder says the entire process normally takes 45mins

kilanoff commented

2026-11-11 10:48:38 +00:00

(Migrated from github.com)

Close the builder, launch the game itself again, and the internal shader generation process will start with an adequate progress bar.

👍 1

chookhen60 commented

2026-11-11 11:00:46 +00:00

(Migrated from github.com)

Close the builder, launch the game itself again, and the internal shader generation process will start with an adequate progress bar.

Can confirm this workaround fixes the issue - but not ideal the shader compilation sits there chewing 100% CPU seemingly forever before realising it's just broken.

> Close the builder, launch the game itself again, and the internal shader generation process will start with an adequate progress bar. Can confirm this workaround fixes the issue - but not ideal the shader compilation sits there chewing 100% CPU seemingly forever before realising it's just broken.

👍 1

xdNevermore commented

2026-11-11 11:05:59 +00:00

(Migrated from github.com)

I deletd the app and reinstalled and this is how much it took, also it built pipeline for like 25minutes also. Now works well but there must be something wrong when updating the launcher not reinstalling.

<img width="974" height="602" alt="Ekran görüntüsü 2026-11-11 133758" src="https://github.com/user-attachments/assets/7c58af37-3f14-4a31-a69b-8dcfaf88440d" /> I deletd the app and reinstalled and this is how much it took, also it built pipeline for like 25minutes also. Now works well but there must be something wrong when updating the launcher not reinstalling.

NotRexed commented

2026-11-11 21:27:03 +00:00

(Migrated from github.com)

Thanks for the report. Reports of the same problem are now collected in #2505, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #2505 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened.