Skip to content
Find The NeedleSteam Demo · factory notes

Demo settings

Buy upgrades when double-clicking does nothing

Demo · Arch Linux / Hyprland report, October 6–8, 2026 · build unspecified

The short answer

Select the upgrade, then use the Buy button in the right-hand pane near the bottom of the screen. Do this even if the on-screen instruction tells you to double-click. Medive, who reported the problem on Arch Linux with Hyprland, later confirmed that the right-pane button worked.

This fixes the missed purchase control in that report. It does not establish that every Linux purchase bug has the same cause, or that Linux is an officially supported platform.

On this page

Use the purchase control, not repeated double-clicks

  1. Open the upgrade screen and select the upgrade you want. Check the selected upgrade's name in the detail pane so you buy the intended one.
  2. Read its requirements. Confirm that your current technology and available money meet the requirements shown in your build. SeaChicken's first reply asks whether the technology was unlocked; the thread does not provide a universal unlock order.
  3. Find Buy in the right-hand detail pane. SeaChicken describes it at the bottom-right, and Medive's final reply identifies the right-pane button. The small double-click instruction was misleading in that player's session.
  4. Use Buy once and inspect the result. Confirm the upgrade's purchased state or changed value and the corresponding cost before buying anything else. These are purchase checks, not a promise that every upgrade has the same visual indicator.

What the Linux thread actually resolved

Medive originally could buy items but could not buy upgrades; double-clicking did nothing with or without Proton. SeaChicken recommended the bottom-right button, another reply repeated the distinction, and Medive then confirmed it worked.

Pryl reports that clicking elsewhere also failed in their session, without a later successful result. That unresolved report prevents treating the button method as a universal Linux fix. No Proton version, launch flag or save reset was needed for Medive's confirmed UI workaround.

If the Buy button still does nothing

Stop and separate a missing control from a purchase failure. If you cannot see Buy, record the selected upgrade and a screenshot of the full detail pane. If it is visible but disabled, read the requirement or cost displayed by your current build. Do not assume a disabled button is the double-click problem.

If an eligible purchase still fails, record the Demo build, distribution, desktop/compositor, whether you use Proton and its version, and whether normal item purchases work. Add those details to the original upgrade discussion. Repeatedly changing compatibility versions or deleting a save is not a verified next step from this thread.

A game that never reaches the upgrade screen has a different blocker: use the exact SSE4.2 error diagnosis or the graphics launch test as appropriate.

Sources & version

Community instructions, not our own gameplay test. Version-specific advice may change after a Demo update.

Keep going

Your next useful guide

Connect multiple pumps and pulpers to one water network →A Demo V42 connection diagram, machine-port splitter steps, and checks that separate a connected water network from enough supply.Place scanners before hay is sold or burned →Route loose hay through scanners, check every branch, and distinguish needle-loss warnings from unproven recovery claims.Change the Demo back to English on Windows →Use the reported settings.cfg locale value when an unreadable game menu blocks you, while keeping the original file and saves intact.Does the Dispatch timer limit a Demo run? →The October 5–6 player explanation of the Dispatch clock, its reported reset behavior and what it does not establish about the full game.Stop an unwanted belt exit or splitter output →Two reported Demo methods: reverse a short end section or close a Smart Splitter output, with checks for bypasses and backed-up input.Diagnose the SSE4.2 CPU error at Demo startup →Check whether Windows exposes SSE4.2 to the Demo and distinguish a CPU instruction requirement from graphics, language or save problems.Try a reversible OpenGL launch test for graphics crashes →Apply the community-proposed Godot compatibility flags in Steam, test the result and restore your original launch options if they do not help.