Submit your pipelines: help remove first-load stutter for everyone #14

New issue

Open

opened 2026-11-12 22:43:23 +00:00 by HumanBean · 0 comments

HumanBean commented

2026-11-12 22:43:23 +00:00

Owner

Is it safe? Yes. The file holds no game code, game data or personal info: only shader hashes, formats and draw state. See assets/pipeline_states.md.

How to submit

Play on a recent build (a build from main).
Zip longshot_pipeline_states.bin from next to the Longshot executable, and drag the zip into a comment here. The in-game menu's pipeline share makes the zip for you and opens this issue.
Fill in:

- Longshot version:
- OS, GPU and driver:
- Output resolution:
- Upscaler + render resolution (game's / DLSS / FSR 3.1 / FSR 4; Quality / Balanced / ...):
- Frame generation / HDR: on / off
- Mods or texture packs:
- Where you played (areas, dungeons, age, night/rain, ...):

Settings matter, so lists from different GPUs, upscalers and resolutions are especially welcome, as are areas few people reach (late dungeons, bosses, night, rain, underwater).

Only send that one file: no longshot_shaders.bin, saves or anything else from the game folder.

Using an AI agent?

You can paste this to a coding agent running on your PC:

Find longshot_pipeline_states.bin next to the Longshot executable in my Longshot game folder and zip it. Then fill in the template from this issue using my Longshot version, OS, GPU and driver, and the graphics settings from Longshot's settings file. Show me the zip's path and the filled template. Don't include or upload any other file from the game folder, and don't post anything yourself.

Then attach the zip and post the comment yourself.

What happens next

We merge each list with nx2/pipeline_states.py (each pipeline kept once) and note its source in assets/pipeline_states.md. Lists that only repeat known pipelines add nothing, and that's fine.

This continues Hookshot's issue 2034, where the lists sent before the fork are.

Thanks!

When Longshot meets a pipeline it hasn't built on your PC yet, it builds it on the spot, which causes a stutter, or a short white wash on the first field load. Releases ship a list of known pipelines that the first start builds ahead of time. The list only covers what someone has played, so **send us the list your game wrote while you played** and we'll merge it into the next release. **Is it safe?** Yes. The file holds no game code, game data or personal info: only shader hashes, formats and draw state. See [`assets/pipeline_states.md`](https://git.magicbean.dev/MagicBeanDev/Longshot/src/branch/main/assets/pipeline_states.md). ## How to submit 1. Play on a recent build (a build from **main**). 2. Zip `longshot_pipeline_states.bin` from next to the Longshot executable, and drag the zip into a comment here. The in-game menu's pipeline share makes the zip for you and opens this issue. 3. Fill in: ``` - Longshot version: - OS, GPU and driver: - Output resolution: - Upscaler + render resolution (game's / DLSS / FSR 3.1 / FSR 4; Quality / Balanced / ...): - Frame generation / HDR: on / off - Mods or texture packs: - Where you played (areas, dungeons, age, night/rain, ...): ``` Settings matter, so lists from different GPUs, upscalers and resolutions are especially welcome, as are areas few people reach (late dungeons, bosses, night, rain, underwater). Only send that one file: no `longshot_shaders.bin`, saves or anything else from the game folder. ## Using an AI agent? You can paste this to a coding agent running on your PC: > Find `longshot_pipeline_states.bin` next to the Longshot executable in my Longshot game folder and zip it. Then fill in the template from this issue using my Longshot version, OS, GPU and driver, and the graphics settings from Longshot's settings file. Show me the zip's path and the filled template. Don't include or upload any other file from the game folder, and don't post anything yourself. Then attach the zip and post the comment yourself. ## What happens next We merge each list with `nx2/pipeline_states.py` (each pipeline kept once) and note its source in `assets/pipeline_states.md`. Lists that only repeat known pipelines add nothing, and that's fine. This continues [Hookshot's issue 2034](https://github.com/NotRexed/Hookshot/issues/2034), where the lists sent before the fork are. Thanks!

HumanBean referenced this issue

2026-11-12 23:30:05 +00:00

fix: issue forms and a pull request template for Forgejo, and a bug report link that fills the form #18

HumanBean referenced this issue from a commit

2026-11-12 23:32:49 +00:00

fix: issue forms and a pull request template for Forgejo, and a bug report link that fills the form (#18)